Date: Tue, 30 Nov 2004 07:30:25 GMT From: Pascal Hofstee <caelian@gmail.com> To: freebsd-amd64@FreeBSD.org Subject: Re: amd64/71674: static libraries cannot be linked when building shared libraries Message-ID: <200411300730.iAU7UPFC013891@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR amd64/71674; it has been noted by GNATS. From: Pascal Hofstee <caelian@gmail.com> To: freebsd-gnats-submit@FreeBSD.org, pete@twisted.org.uk Cc: Subject: Re: amd64/71674: static libraries cannot be linked when building shared libraries Date: Mon, 29 Nov 2004 21:37:40 -0800 As i am occasionally toying around with GNUstep as well ... and noticed that originally the FreeBSD ports-version of GNUstep essentially required an actual libobjc.so (and hence required to build a gcc-3.3.5 iirc and get its libobjc.so from there) .... i have since noticed that it is indeed possible to build GNUstep on FreeBSD/i386 using just our static libobjc.a I am wondering though if there is any specific reason for Not reverting this "bogus" disabling of libobjc.so for i386 as well ? i recall reading somewhere that certain elements of the Objective-C runtime would require a dynamic libobjc ... though i don't recall where i read this at the moment ... and it seems not to really impact GNUstep's functioning. But if there is no real reason (besides apprently so called performance impact .. which i hope may have been improved on since 1998) ... i would definately appreciate this change reverted on i386 as well ... (if only for consistency's sake concerning the libraries provided by the base system between different FreeBSD architectures) With kind regards, Pascal Hofstee
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200411300730.iAU7UPFC013891>