package. shlibtool will not build static libraries. Add handling in
bsd.pkg.mk for a variable named "SHLIBTOOL_OVERRIDE" that is analogous to
LIBTOOL_OVERRIDE and causes any listed libtool scripts to be replaced with
a symlink to shlibtool, and teach buildlink2 about shlibtool. Bump
PKGREVISION of devel/libtool* packages to 11.
buildlink2.mk files back into the main trunk. This provides sufficient
buildlink2 infrastructure to start merging other packages from the
buildlink2 branch that have already been converted to use the buildlink2
framework.
Jeff Putsch <jdputsch@attbi.com>. Also repair a typo that had prevented
'-fno-common' from being passed along (found and fixed by skrll).
Bump PKGREVISION.
Approved by skrll.
libraries the following could occur
- a.out platforms: c++rt0.o would be missing and therefore
global contstructors would not work.
- ELF platforms libstdc++ and libm would not be explicitly
linked in.
This affected notably libqt and explains the build failure of kdelibs2 on
arm32.
Bump PKGREVISION and require it.
in the library name. This fixes pkg/15981 from Dan McMahill
<dmcmahill@netbsd.org>
Patch up the test configure scripts while we're here.
Bump the PKGREV, but don't require it just yet.
recording strategy and a flag (--preserve-dup-deps) to provide the old
stratey if needed. The new strategy reduces the length of the
dependency_libs information stored in .la files and therefore the length
of link lines. This has a positive effect on performance.
Pull across the documentation updates for the change.
Bump the PKGREVISION.
This was tested by building and running both KDE and Gnome.
The side effect of touching configure.in is to recreate ltmain.sh from
ltmain.in. We patch ltmain.sh and so the changes get lost.
This should fix pkg/15481 from Tom Haapanen <tomh@metrics.com>
well as the normal shared objects. This means that the new toolchain, that
links in libgcc_pic.a, will build proper shared objects again.
Bump to nb5 and make this the required version.
Fixes pkg/15120 from Matthias Scheler <tron@colwyn.zhadum.de>
toolchains actually works.
I had reports that the problem that the definition of
"output_verbose_link_cmd" was supposed to fix had indeed been fixed.
(Never believe everything you read)
/usr/lib/crtbeginS.o and /usr/lib/crtendS.o make it into
{pre,post}dep_objects.
Fixes pkg/14353 from Witold J. Wnuk <witek@pd37.warszawa.sdi.tpnet.pl>
Tested as "still" working on 1.5.2.
Bump minor number of pkg and make pkgsrc depend on this version.
The automatic truncation in gensolpkg doesn't work for packages which
have the same package name for the first 5-6 chars.
e.g. amanda-server and amanda-client would be named amanda and amanda.
Now, we add a SVR4_PKGNAME and use amacl for amanda-client and amase for
amanda-server.
All svr4 packages also have a vendor tag, so we have to reserve some chars
for this tag, which is normaly 3 or 4 chars. Thats why we can only use 6
or 5 chars for SVR4_PKGNAME. I used 5 for all the packages, to give the
vendor tag enough room.
All p5-* packages and a few other packages have now a SVR4_PKGNAME.
/usr/local/lib.
Discussed with Johnny Lam <jlam@netbsd.org> and Bernd Ernesti
<veego@netbsd.org>
Problem reported by Jeremy C. Reed <reed@reedmedia.net> on tech-pkg
foo-* to foo-[0-9]*. This is to cause the dependencies to match only the
packages whose base package name is "foo", and not those named "foo-bar".
A concrete example is p5-Net-* matching p5-Net-DNS as well as p5-Net. Also
change dependency examples in Packages.txt to reflect this.
BUILDLINK_PREFIX.<pkgname>. This allows buildlink to find X11BASE packages
regardless of whether they were installed before or after xpkgwedge was
installed. Idea by Alistair Crooks <agc@pkgsrc.org>.
FOO_REQD=1.0 being converted to foo>=1.0, one can now directly specify
the dependency pattern as FOO_DEPENDS=foo>=1.0. This allows things like
JPEG_DEPENDS=jpeg-6b, or fancier expressions like for postgresql-lib.
Change existing FOO_REQD definitions in Makefiles to FOO_DEPENDS.
Notable changes are:
* Fix memory leak in libltdl
* Handle large dependency_libs entries in .la files better
* Integration of a lot of the NetBSD changes
of the ones with which libtool was built, attempt to infer the compiler
from the first word of the command line passed to libtool.
We only reach this test if libtool is about to die with a message about
lacking a specific tag, so this change is the least intrusive that can
be made.
This means that different CC options can now be recognised when compiling.
Bump version number to nb6
Actually simply the workaround in the process.
Fixes problems noted by SUNAGAWA Keiki <kei_sun@ba2.so-net.ne.jp> on
tech-pkg and David W. Talmage <talmage@ricochet.net> in private email.
Tested by SUNAGAWA Keiki.
support to follow. Note this in documentation.
Bump revision of libtool to nb3 and update dependencies.
Update (sort) known affected PLISTs.
Fixes pkg/12368 by Kimmo Suominen <kim@tac.nyc.ny.us>
Fixes problems with cross/* noted on tech-pkg and packages by
Chuck Cranor <chuck@research.att.com>, and
Thomas Klausner <wiz@danbala.ifoer.tuwien.ac.at>
This meta-package pulls in the other two parts.
XXX any modifications should be made to this pkg's Makefile.common, patches,
XXX files dir etc. *only* !
actually are CTORS/DTORS in the objects that go into the library.
This makes pkgsrc under 1.3.x not blow up on C libraries that were built
with libtool. E.g. everything that linked against -lintl would dump core.
out of date - it was based on a.out OBJECT_FMT, and added entries in the
generated PLISTs to reflect the symlinks that ELF packages uses. It also
tried to be clever, and removed and recreated any symbolic links that were
created, which has resulted in some fun, especially with packages which
use dlopen(3) to load modules. Some recent changes to our ld.so to bring
it more into line with other Operating Systems also exposed some cracks.
+ Modify bsd.pkg.mk and its shared object handling, so that PLISTs now contain
the ELF symlinks.
+ Don't mess about with file system entries when handling shared objects in
bsd.pkg.mk, since it's likely that libtool and the BSD *.mk processing will
have got it right, and have a much better idea than we do.
+ Modify PLISTs to contain "ELF symlinks"
+ On a.out platforms, delete any "ELF symlinks" from the generated PLISTs
+ On ELF platforms, no extra processing needs to be done in bsd.pkg.mk
+ Modify print-PLIST target in bsd.pkg.mk to add dummy symlink entries on
a.out platforms
+ Update the documentation in Packages.txt
With many thanks to Thomas Klausner for keeping me honest with this.
The previous patch could cause problems in a couple of oddball cases.
So, set need_version=yes for a.out, and hack avoid-version so it works on
a.out platforms.
loads shlib components at run-time on a.out systems (such as imlib, gtk themes,
gdk-pixbuf, and gnumeric). So, disable it for all NetBSD platforms.
(Note: This requires updating some PLISTs.)
To test, type "info libtool|" and hold down space. See it stop with a
``Cannot find the node "(/usr/pkg/info/libtool.info)Linking executables"''
error. Simply making sure the info-files get re-done works here.
--cplusplus option is should just work. Thanks to Todd Verling for
help with this.
I've been sitting on this update while I played with
deplibs_check_method for a.out. There seems to be a problem related
to dlopen stuff if file_magic is used. Still investigating.
Version bumped to nb4.
- New, optional Makefile variable HOMEPAGE, specifies a URL for
the home page of the software if it has one.
- The value of HOMEPAGE is used to add a link from the
README.html files.
- pkglint updated to know about it. The "correct" location for
HOMEPAGE in the Makefile is after MAINTAINER, in that same
section.
