Subject: bl3 and LDFLAGS
To: None <tech-pkg@netbsd.org>
From: Jonathan Perkin <jonathan@perkin.org.uk>
List: tech-pkg
Date: 06/08/2004 12:39:02
--5H/fb45LiqycLnjq
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

I've recently attempted a 64bit SunPRO bulk build, and the
results don't look good so far.  Most packages are failing at
the link stage because the 64bit flags are not being passed
through to ld, e.g. for databases/freetds:

  /bin/ksh ../../libtool --mode=3Dlink cc  -O -xO2 -xtarget=3Dultra -xarch=
=3Dv9 -D_LARGE FILE_SOURCE -D_FILE_OFFSET_BITS=3D64 ...
  ld -G -h libtds.so.2 [ no -xarch=3Dv9 etc] ...

  ld: warning: file ./.libs/libtds_objects.a(mem.o): wrong ELF class: ELFCL=
ASS64

I suspect this is caused in bl3 somewhere; anyone able to give
me some hints before delving into it?  I'd love if there was a
way to override LDFLAGS for all packages, inserting my custom
CFLAGS at every link stage, so even packages with hardcoded

  LDFLAGS =3D ...

will be compiled correctly.  This would be a huge benefit.

Thanks,

--=20
Jonathan Perkin                         <jonathan@perkin.org.uk>
BBC Internet Services         http://www.perkin.org.uk/jonathan/

--5H/fb45LiqycLnjq
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (NetBSD)

iQEVAwUBQMWlViFee6/VMqV4AQLkdggAlk/IY+Hxe865cSxJcTcaUYBJVlc2sTnS
LeKpkI39lCHwaOanKXTRDW244s3e1DtRbp5QibE+FZeQFeLZxJ1T5TWcDkCj/RtF
udyAxwM2B2DgpmuNO8imQPhHw4CVzv1cBwTxNqWOKD7LxSrAw34Xn6vW8ck7RMt4
zhT/uHt7SjXU7gBfCYyoJlSS66fMfqyuvY0XdWhRmR5pIez8kpXHcNoZYAsL88cn
3KjetdmllpUlLF6rfSyey53ohhEuC/UN/LicGboqb21XpU65brDe3gwMPjo7bsgA
N+/TWPqe0VETKA99io9Tdpc/pWr9C2XwoPyAN/s1jKhv/NaUDhs8CQ==
=nLsB
-----END PGP SIGNATURE-----

--5H/fb45LiqycLnjq--