Fixes endless loop problems. Report and suggestion by Greg Troxel
gdt at ir bbn com in private mail; some comments by Alistair Crooks;
patch reviewed and okayed by Jaromir Dolecek.
Bump PKGREVISION to 3.
so don't depend on devel/gindent on these two platforms.
* USE_BUILDLINK2 implies AUTOMAKE_OVERRIDE=NO.
* Don't use the hackish test for libwrap supplied in the configure script.
Instead, just specify the necessary variables to link against libwrap
in the package Makefile.
This closes PR 18712 by Greg A. Woods.
compiled using orbit-idl, which uses the C preprocessor to do its work, and
the C preprocessor has it's arguments transformed (correctly) by
buildlink2.
headers in ${BUILDLINK_DIR}, simply create BUILDLINK_CPPFLAGS.<pkg>
variables whose values are appended to CPPFLAGS, which are automatically
passed to the configure and build processes.
BUILDLINK_TRANSFORM.<pkg> has little use in buildlink2 since packages are
now told that the software may be found where it really is installed, not
in ${BUILDLINK_DIR} as was the case with buildlink1. Eventually, these
variables will be declared unsupported by buildlink2.
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.
provided by Thomas Klausner.
Diffs from previous version:
2002-03-20 Michael Meeks <michael@ximian.com>
* configure.in: copy the autoconf macro into here so we
can rely on it not changing across autoconf versions.
2002-03-11 Michael Meeks <michael@ximian.com>
* src/IIOP/giop-msg-buffer.c
kill #define writev mess.
(giop_send_buffer_write): handle EINTR, handle EAGAIN
correctly, handle short writev's correctly, test
thorougly.
* src/ORBitutil/compat.c (g_writev): kill this
abomination.
2002-02-11 Sebastian Wilhelmi <wilhelmi@ira.uka.de>
* src/orb/allocators.h, src/orb/allocators.c (ORBit_alloc_2,
ORBit_free): Make the free marker really always sit directly in
front of the memory block, not at some random lower position.
2002-02-09 Elliot Lee <sopwith@redhat.com>
* src/ORBitutil/os-feature-alloca.h: Don't redefine alloca if it is already defined.
2002-01-27 Darin Adler <darin@bentspoon.com>
* test/everything/Makefile.am: Added -lm -- can't build without it.
2002-01-25 Mark McLoughlin <mark@skynet.ie>
* configure.in: (AC_CHECK_ALIGNOF): error out if an alignment
is found to be zero.
Thomas thought that the modification to src/IIOP/giop-msg-buffer.c to
"kill #define writev mess" might mean that we could drop the
NetBSD-specific wrapper for writev(2), but sadly this isn't so -
configure undefines HAVE_LIMITED_WRITEV on NetBSD, and rightly so,
since IOV_MAX (1024) iovecs can be written, not 50. However, we still
have the basic "attempt to send more than IOV_MAX iovecs and you get
EINVAL" problem with our writev(2) implementation.
calls writev(2). Some of the applications which use ORBit, such as
oaf, can send 1214 iovecs, which is slightly more than IOV_MAX. Add a
wrapper for writev(2), to check the number of iovecs passed to writev,
and loop, sending MIN(IOV_MAX, count) until the iovecs have all been
written.
Summary of changes:
- removal of USE_GTEXINFO
- addition of mk/texinfo.mk
- inclusion of this file in package Makefiles requiring it
- `install-info' substituted by `${INSTALL_INFO}' in PLISTs
- tuning of mk/bsd.pkg.mk:
removal of USE_GTEXINFO
INSTALL_INFO added to PLIST_SUBST
`${INSTALL_INFO}' replace `install-info' in target rules
print-PLIST target now generate `${INSTALL_INFO}' instead of `install-info'
- a couple of new patch files added for a handful of packages
- setting of the TEXINFO_OVERRIDE "switch" in packages Makefiles requiring it
- devel/cssc marked requiring texinfo 4.0
- a couple of packages Makefiles were tuned with respect of INFO_FILES and
makeinfo command usage
See -newly added by this commit- section 10.24 of Packages.txt for
further information.
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.
Include a bugfix for lisp_LISP independently discovered by me that has
been pulled up to the automake-1-4 branch of automake cvs.
Changes are:
New in 1.4-p5:
* Allow AM_PROG_LIBTOOL again.
* Diagnose AC_CONFIG_HEADERS the same as AC_CONFIG_HEADER.
* Display distributed file list correctly in usage message.
* Allow numbers in macro names.
* Bugfixes.
New in 1.4-p4:
* Deal with configure.ac as well as configure.in -- this time for real!
* The version numbering system now allows three point version numbers,
such as 1.4.4, without thinking they are alpha release numbers.
New in 1.4-p3:
* Deal with configure.ac as well as configure.in.
* Don't complain if `version.texi' is included in multiple places.
New in 1.4-p2:
* Deal with AC_CONFIG_FILES from autoconf-2.50.
* Improvements to f77 support.
* DESTDIR now works for script targets.
* distcheck-hook works correctly.
New in 1.4-p1:
* The version numbering system now allows fork identifiers (such as
the p1 in this version of automake).
* Cope gracefully with various versions of libtool which may or may not
require ltconfig, ltcf-c.sh, ltcf-cxx.sh or ltcf-gcj.sh.
* Bugfixes.
set FOO_CONFIG=${BUILDLINK_CONFIG_WRAPPER.foo} in both CONFIGURE_ENV and
MAKE_ENV. We remove the check for GNU_CONFIGURE because if a package
Makefile includes the buildlink.mk file, then it most likely wants to use
the config script wrappers as well. Change suggested by Hubert Feyrer
(hubertf) and Tomasz Luchowski (zuntum).
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>.
so remove it from package Makefiles. Also move the inclusion of the
buildlink.mk files to the end of the Makefile to just before bsd.pkg.mk
to ensure that any Makefile settings occur before the buildlink.mk files.
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.
first component is now a package name+version/pattern, no more
executable/patchname/whatnot.
While there, introduce BUILD_USES_MSGFMT as shorthand to pull in
devel/gettext unless /usr/bin/msgfmt exists (i.e. on post-1.5 -current).
Patch by Alistair Crooks <agc@netbsd.org>
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.
0.5.3 -- only that 0.5.4 is the latest stable version of ORBit.
The pkgsrc-related changes are:
* Compile and link libpopt statically into ORBit. This is really a
small library, and there are more recent versions available if we
with to add it to pkgsrc. Also don't install this library.
* Compile the tcpd-specific code in libIIOP.
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.
