4 commits

Author	SHA1	Message	Date
jlam	13760a9c4a	GCC generates and uses its own libtool to build shared libraries, and ... the resulting shared library names don't necessarily match the NetBSD names. Instead of hardcoding the shared library names in the PLISTs, only list the libtool archives in the PLISTs and dynamically determine the shared library names at post-install time and insert them into the PLIST. This fixes PLIST errors on non-NetBSD platforms. All of the magic is done in pkgsrc/lang/gcc3/language.mk. This should probably be generalized into something that could be used by all packages that use libtool.	2004-09-08 10:22:01 +00:00
drochner	26acfcb094	oops, I was assuming the .info files are put into the packlist ... automatically. Not true appearently.	2003-07-08 16:07:03 +00:00
drochner	7497ad9c29	some cleanup: ... -USE_NEW_TEXINFO, saves some patches -symlink libiberty.a into build tree instead of buildlink/lib, saves some patches -put common make rules into Makefile.common (for all) and buildaddon.mk (for all but the base "c" pkg)	2003-07-08 15:04:53 +00:00
drochner	bf1c6cfe93	Split the gcc3 pkg into per-language pieces. ... Needs some cleanup and integration; eventually lang/gcc3 can turn into a meta-pkg.	2003-07-06 12:15:03 +00:00