Hi, experts, Our RE got the following build error when I built pango(1.24.1) on snv_116 sparc(/usr/ccs/bin/ld version is 5.11-1.1673), I didn't see this problem on snv_114(ld version is 5.11-1.1666) and snv_116 x86.
snip from log file, ************************************* pkgbuild: source='viewer-pangox.c' object='viewer-pangox.o' libtool=no \ pkgbuild: DEPDIR=.deps depmode=none /bin/bash ../depcomp \ pkgbuild: /sgnome/onnv-tools/sparc/SS12/bin/cc -DHAVE_CONFIG_H -I. -I.. -I.. -DG_DISABLE_CAST_CHECKS -D_REENTRANT -D_PTHREADS -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -I/usr/X11/include -I/usr/include/freetype2 -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/X11/include -I/usr/include/freetype2 -i -xO4 -xspace -xstrconst -xarch=v9 -xcode=pic32 -mr -c viewer-pangox.c ... pkgbuild: /sgnome/onnv-tools/sparc/SS12/bin/cc -i -xO4 -xspace -xstrconst -xarch=v9 -xcode=pic32 -mr -Wl,-zignore -Wl,-zcombreloc -Wl,-Bdirect -o .libs/pango-view viewer-render.o viewer-main.o pango-view.o viewer-x.o viewer-pangox.o viewer-pangoft2.o viewer-pangoxft.o viewer-cairo.o viewer-pangocairo.o -L/usr/lib/sparcv9 ../pango/.libs/libpango-1.0.so ../pango/.libs/libpangox-1.0.so -lsocket -lnsl -L/lib ../pango/.libs/libpangoft2-1.0.so ../pango/.libs/libpangoxft-1.0.so -L/usr/X11/lib -lXft -lXrender -lX11 ../pango/.libs/libpangocairo-1.0.so /jds/packages/BUILD/SUNWpango-1.24.1/sparcv9/pango-1.24.1/pango/.libs/libpangoft2-1.0.so /jds/packages/BUILD/SUNWpango-1.24.1/sparcv9/pango-1.24.1/pango/.libs/libpango-1.0.so -lgobject-2.0 -lgmodule-2.0 -lglib-2.0 -lm -lfreetype -lfontconfig -lcairo -R/usr/lib/sparcv9 -R/lib -R/usr/X11/lib pkgbuild: cc: Warning: -xarch=v9 is deprecated, use -m64 to create 64-bit programs *pkgbuild: ld: elf error: file viewer-pangox.o: elf_strptr: Request error: no string table* It looks like that ld has changed in snv 115. Does anyone know the root cause? Please cc to dave.lin at sun.com who saw this problem. Thanks Brian
