* We can't use the funky SETENV construct because it breaks some of the
code related to computing package sizes. Use a different way to remove
unwanted environment variables from the shell environment before calling
BSD make.
and rely on the gcc and g++ called internally to use the buildlink
wrappers. This correctly forces all references to headers and libraries
outside of /usr/include and /usr/lib to be within ${BUILDLINK_DIR}.
handle everything for us. Invoking "pgcc" is equivalent to invoking
"cc -pthread" on other platforms. Change the buildlink.mk file to
appropriately define CC and CXX to pgcc and pg++, respectively.
pkgsrc. Instead, a new variable PKGREVISION is invented that can get
bumped independent of DISTNAME and PKGNAME.
Example #1:
DISTNAME= foo-X.Y
PKGREVISION= Z
=> PKGNAME= foo-X.YnbZ
Example #2:
DISTNAME= barthing-X.Y
PKGNAME= bar-X.Y
PKGREVISION= Z
=> PKGNAME= bar=X.YnbZ (!)
On subsequent changes, only PKGREVISION needs to be bumped, no more risk
of getting DISTNAME changed accidentally.
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.
There is no need to worry about if its called vfork or __vfork14. The
right one will get built. As vfork is not used internally don't worry
about creating a syscall wrapper.
While I'm here remove a completely unnecessary unistd.h that's looks as
though it was for a early version linux.
"The changes to unproven-pthreads fix a problem with fstat not using
the pthreads filedescriptors, but the native ones (the code for this
was already there (slightly buggy), but it wasn't used for some
unknown reason). In addition, the handling of select is improved, as
the original code may wake up not all threads waiting for some event."
Bump version number to unproven-pthreads-0.17nb2
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.
