Adam D. Barratt wrote: > [Please Cc me on replies; I'm not subscribed to the list] > > Hi,
Hi > I'm looking at the failure of the mailutils package to build on mips and > mipsel, as it's stalling the transition of krb5 to testing. > > The build fails with the error below, which I believe is probably due to > a lack of -fPIC somewhere in the build process. The question is, where, > as our current attempts to add -fPIC to relevant places don't seem to > have fixed the problem. > > Is there any easy (or even logical) way of working out exactly where > -fPIC is missing? Unfortunately it's not enough to use -fPIC everywhere. It seems binutils on mips is more picky and does not want to link when it finds multiple different symbols with the same name where one is a weak symbol and the other not... > /bin/sh ../libtool --tag=CC --mode=link cc -g -O2 -g -Wall -O2 -o muauth > muauth.o ../libargp/libmuargp.a ../libcfg/libmucfg.la ../lib/libmuaux.la > ../auth/libmuauth.la -lgsasl -lgnutls -lgcrypt -lldap -lpam -ldl > ../mailbox/libmailutils.la -lcrypt -lresolv -lpthread -lgdbm > libtool: link: cc -g -O2 -g -Wall -O2 -o .libs/muauth muauth.o > ../libargp/libmuargp.a ../libcfg/.libs/libmucfg.so ../lib/.libs/libmuaux.a > ../auth/.libs/libmuauth.so -L/usr/lib -L/usr/local/lib/mysql > /build/buildd/mailutils-2.0+dfsg1/mailbox/.libs/libmailutils.so > /usr/lib/libmysqlclient.so -lnsl -lm /usr/lib/libgsasl.so /usr/lib/libidn.so > /usr/lib/libntlm.so -lgssapi_krb5 -lkrb5 -lk5crypto -lcom_err > /usr/lib/libgnutls.so /usr/lib/libtasn1.so -lz /usr/lib/libgcrypt.so > /usr/lib/libgpg-error.so -lldap -lpam -ldl ../mailbox/.libs/libmailutils.so > -lcrypt -lresolv -lpthread /usr/lib/libgdbm.so > /usr/bin/ld: non-dynamic relocations refer to dynamic symbol > mu_gsasl_module_data > /usr/bin/ld: failed to set dynamic section sizes: Bad value > collect2: ld returned 1 exit status so this probably means there are 2 different mu_gsasl_module_data symbols in the code... Cheers Luk -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
