tech-pkg archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

dependency of glib2 on libelf harmful


I am currently building pkgsrc on Solaris 10/Sparc with a stand-alone GCC 4.7.0, i.e. not the one from lang/gcc47, bootstrapped without any dependency on pkgsrc.

While building www/curl, the configure script choked on

checking for OpenSSL headers version... 0.9.8 - 0x0090817fL
checking for OpenSSL library version... unknown
checking for OpenSSL headers and library versions matching... fail

and the error in config.log was

configure:20915: gcc -o conftest -g0 -O2 -Wno-system-headers -isystem /usr/pkgsrc/20120411/include -I/usr/pkgsrc/20120411/include -L/usr/p kgsrc/20120411/lib -R/usr/pkgsrc/20120411/lib -L/usr/pkgsrc/20120411/lib conftest.c -lssl -lcrypto -llber -lldap -lrt -lsocket -lnsl -lssl -lcrypto -lsocket -lnsl -ldl >&5
ld: fatal: file /var/tmp//ccIujcJ4.o: unknown file type

Thousands of other object files could be compiled succesfully, and I didn't encounter the problem on Solaris 10/i86.

It turned out, that after removal of devel/libelf the problem was gone. Although GCC was built without this libelf, it was included by the linker and caused the problem.

The only reason for having devel/libelf is the dependency in devel/glib2, which is AFAIK supposed to fix a problem relating to large file support on Solaris. I think pkg/41601 tells part of the story. But if this breaks the ability to use compilers not prepared to use this libelf, it's a bad fix.

Any ideas???

 Jörn Clausen                    
 Universität Bielefeld

Home | Main Index | Thread Index | Old Index