lang/gcc41 - linking issues

[[LoN]Kamikaze]

I have further reports to make about the gcc41 port. It seems that the
latest build links binaries to libraries in
/usr/local/lib/gcc/i386-portbld-freebsd6.1/4.1.1/ , because of this I
have to run

# ldconfig -m /usr/local/lib/gcc/i386-portbld-freebsd6.1/4.1.1/

after every boot to make all applications built by gcc41 run again. I
know I could fix this with a couple of symlinks or entries in
/etc/libmap.conf, but the real trouble is that all ports built with
gcc41 will be broken if I deinstall gcc41. I don't think this is the way
it is supposed to be. I did not have such troubles with previous builds.

This behaviour is independent from weather I build gcc41 with libjava or
without.

[Gerald Pfeifer]

On Mon, 20 Mar 2006, Dirk Meyer wrote:
> This happens even with gcc3x when you build "SHARED"
>
> I will update gcc32 after some more testing.

IMnsHO opionion this indicates a major deficiency of the FreeBSD
ports infrastructure.

Hacking each and every port like this, when we already *have* the
needed information in the individual ports doesn't seem a good approach.

That said, I do not disagree with your patch. In fact since I'm on the
road with somewhat limited access to my FreeBSD machine I would appreciate
if you could make similar changes to lang/gcc{33,34,40,41,42} -- the first
two I have updates pending and tested which I'll commit shortly.)

I just think the FreeBSD Ports Collection should solve this in a better
way.

Gerald
_______________________________________________
freebs...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-port...@freebsd.org"

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-...@muc.de

[[LoN]Kamikaze]

I noticed that the mysql port solves this in a nice and elegant way. A
simple

# echo "/usr/local/lib/gcc/i386-portbld-freebsd6.1/4.1.1/" >
/usr/local/libdata/ldconfig/gcc41

solves the problem easily.

Does anyone agree? Should I make a patch and file a PR?

[[LoN]Kamikaze]

Dirk Meyer wrote:
> [LoN]Kamikaze schrieb:,

>
>> # echo "/usr/local/lib/gcc/i386-portbld-freebsd6.1/4.1.1/" >
>> /usr/local/libdata/ldconfig/gcc41
>> solves the problem easily.
>

> Where is this documented?
>
> kind regards Dirk
>

Since this issue is rather troubling in my opinion I wanted to get a
hold of how library finding works in FreeBSD. I started with reading
"/etc/rc.d/ldconfig". The command

# /etc/rc.d/ldconfig start

brought the following output:
ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/X11R6/lib
/usr/local/lib /usr/local/lib/compat/pkg /usr/local/libdata/ldconfig/mysql
a.out ldconfig path: /usr/lib/aout /usr/lib/compat/aout /usr/X11R6/lib/aout

Since mysql certainly isn't part of the base system I had a look what's
there. "/usr/local/libdata/ldconfig/mysql" is a file that simply
contains the string "/usr/local/lib/mysql".

I didn't find it documented anywhere, though. Also it seems that all
"lang/gccXX" ports have recently received the proper "INSTALLS_SHLIB"
and "LDCONFIG_DIRS", as described in the porters handbook. Thus my
solution is obsolete.

[[LoN]Kamikaze]

>From 6.0 on ldconfig_compat is part of the base rc.d system.

Dirk Meyer wrote:
> Hallo [LoN]Kamikaze,

>
>> I didn't find it documented anywhere, though. Also it seems that all
>> "lang/gccXX" ports have recently received the proper "INSTALLS_SHLIB"
>> and "LDCONFIG_DIRS", as described in the porters handbook. Thus my
>> solution is obsolete.
>

> This seemms to be a feature of a port.
> /usr/ports/misc/ldconfig_compat
>
> kind regards Dirk