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.
linked from a particular package, and add a pre-configure target to
the buildlink.mk file to more painlessly use buildlink.mk files. A
${BUILDLINK_TARGETS} variable still exists in case a package _must_
define NO_CONFIGURE.
${BUILDLINK_INCDIR} and ${BUILDLINK_LIBDIR}, to be used by other packages.
* Remove unnecessary include of bsd.prefs.mk.
* Change how we disable pthreaded version of lwp by passing values to the
configure script via the environment, instead of requiring an extra file.
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.
coda/lwp may be built and run. "lwp" needs custom pmap handling in assy
language. Only "lwp" is needed to build and run a coda server; client's
also need to have the MI CODA filesystem enabled. In fact, it seems
that sparc64 has the CODA file system even the assembler in "lwp" is
only for sparc, and mac68k is the only m68k port with the CODA filesystem,
but such would be cumbersome to express with the present framework.
full support.
-add partial mips support, but still get:
process.s:177: Warning: MIPS PIC call to register other than $25
process.s:177: Warning: No .cprestore pseudo-op used in PIC code
Add a new USE_LIBTOOL definition that uses the libtool package instead of
pkglibtool which is now considered outdated.
USE_PKGLIBTOOL is available for backwards compatibility with old packages
but is deprecated for new packages.
* Fixed a bad stackbase on NetBSD/FreeBSD platforms.
* Fixed a locking bug in lock_pt.c.
* Using pthread_attr_setdetachstate in lwp_pt.c instead of modifying the
attr struct directly.
* Improved cross-compiling with cygwin32 and djgpp.
* Added a script that might produce a useable ports/packages descriptions.
* Wrote a bit in the INSTALL document.
NOTE: The script pkgs/pkg-bsd.sh was not used to make this package.
