On Sat, Apr 05, 2003, Ralf S. Engelschall wrote:
> On Sat, Apr 05, 2003, Michael Schloh wrote:
>> Force use of binutils ld command, removing the incompatible mapfile
>> flag if it exists. Also, manually build the static library if only a
>> shared one was built.
>
> 1. You're using %{l_prefix}/bin/make. Either you then need also a
> dependency to "make" or you have to use %{l_make} instead.
> Additionally, MAKE should be implicitly set by at least GNU make, so
> if you depend on GNU make you do not need MAKE=%{l_make} at all.
>
No, it looks like a native make will work here. The implicit setting
would have been a good idea, though.> 2. Why to the hell should libXaw3d.a not be built? Instead of > doing it manually (and hopefully the right way) I would > expect that one fixes the real problem instead. > No, as there are more than one way to fix this problem. The one I chose is activated only if the vendor sources fail to build a static library. This might be due to the particular X11 configuration of the host, but we can't depend on that because the X11 configuration (X11/lib/config) is not within OpenPKG scope. If you or anybody has a preferred fix, then they it is welcome of course. > 3. Why is GNU binutils required? Just because you want to reference > "ar" and "ld" directly? Then LD=ld and AR=ar would be sufficient > because they _HAVE_ to be in $PATH. Or is GNU binutils really > requires for functionality reasons? > The chosen fix solved the build problem with symbol references. There might be a different fix not involving binutils. However, debugging native tools on a platform by platform basis is not as efficient as using one common toolset (like binutils). I believe this was proven when diagnosing php with its sed problems, for example. -- [EMAIL PROTECTED] Development Team, Application Services Cable & Wireless Deutschland GmbH
pgp00000.pgp
Description: PGP signature
