GNOME Bugzilla – Bug 88234
glib-2.0.4 breaks on hp-ux 11.00
Last modified: 2004-12-22 21:47:04 UTC
gmake ... rm -fr .libs/libglib-2.0.lax mkdir .libs/libglib-2.0.lax rm -fr .libs/libglib-2.0.lax/libcharset.al mkdir .libs/libglib-2.0.lax/libcharset.al (cd .libs/libglib-2.0.lax/libcharset.al && ar x /users/mgansser/GNU/glib- 2.0.4/glib/libcharset/.libs /libcharset.al) /usr/ccs/bin/ld -b +h libglib-2.0.sl.0 +b /usr/local/lib -o .libs/libglib- 2.0.sl.0.4 garray.lo gasy ncqueue.lo gbacktrace.lo gbsearcharray.lo gcache.lo gcompletion.lo gconvert.lo gdataset.lo gdate.lo gdir.lo gerror.lo gfileutils.lo ghash.lo ghook.lo giochannel.lo glist.lo gmain.lo gmarkup.lo gmem.lo gmessages.lo gnode.lo gpattern.lo gprimes.lo gqsort.lo gqueue.lo grel.lo grand.lo gscanner.lo gshel l.lo gslist.lo gstrfuncs.lo gstring.lo gthread.lo gthreadpool.lo gtimer.lo gtree.lo guniprop.lo gutf 8.lo gunibreak.lo gunicollate.lo gunidecomp.lo gutils.lo giounix.lo gspawn.lo .libs/libglib-2.0.lax/ libcharset.al/localcharset.lo -L/usr/local/lib libcharset/.libs/libcharset.al -R/usr/local/lib -lc /usr/local/lib/libintl.sl /usr/local/lib/libiconv.sl -lc /usr/ccs/bin/ld: Invalid numeric argument for -R/usr/local/lib gmake[3]: *** [libglib-2.0.la] Error 1 gmake[3]: Leaving directory `/users/mgansser/GNU/glib-2.0.4/glib' gmake[2]: *** [all-recursive] Error 1 this is my built script: setenv CPPFLAGS "-I/usr/local/include" setenv LDFLAGS "-L/usr/local/lib" setenv RANLIB "/bin/true" # gmake distclean rm config.cache ./configure --prefix=/usr/local --x-includes=/usr/include/X11R6 \ --x-libraries=/usr/lib/X11R6 --with-libiconv=gnu \ --enable-threads=no --enable-static=yes gmake Compiler: gcc-3.1 thanks Martin
*** This bug has been marked as a duplicate of 78302 ***
I know his bug is a duplicate of 78302. I brought this to the attention of the libtool developers and they think it is a gettext problem. I`ve test it by remove '-R/usr/local/lib' from "/usr/local/lib/libintl.la". It seems to solve the problem on hpux with glib-2.0.x
Not sure why this was repoened :-) *** This bug has been marked as a duplicate of 78302 ***