relocatable.texi: improve reference to packaging systems?

Rather than Red Hat, Debian, and similar package systems > would it make more sense to refer to "RPM, APT, and similar package systems" ? (i.e. refer to the package systems, not the GNU/Linux distros). -- https://rrt.sc3d.org

relocatable.texi: remove mention of OpenBSD?

doc/relocatable.texi contains the following text: > Also, installation with > @option{--enable-relocatable} might not work on OpenBSD, when the > package contains shared libraries and libtool versions 1.5.xx are used. > I checked, and the last version of OpenBSD to ship with libtool 1.5 was

Re: relocatable.texi: remove mention of OpenBSD?

Hi Reuben, > doc/relocatable.texi contains the following text: > > > > Also, installation with > > @option{--enable-relocatable} might not work on OpenBSD, when the > > package contains shared libraries and libtool versions 1.5.xx are used. > > > > I checked, and the last version of OpenBSD

Re: relocatable.texi: improve reference to packaging systems?

Hi Reuben, > Rather than > > Red Hat, Debian, and similar package systems > > > > would it make more sense to refer to > > "RPM, APT, and similar package systems" > > ? (i.e. refer to the package systems, not the GNU/Linux distros). Well, the tool on Red Hat systems is not called 'rpm' any

Re: relocatable.texi: improve reference to packaging systems?

On Tue, 26 Jan 2021 at 09:43, Bruno Haible wrote: > Hi Reuben, > > > Rather than > > > > Red Hat, Debian, and similar package systems > > > > > > > would it make more sense to refer to > > > > "RPM, APT, and similar package systems" > > > > ? (i.e. refer to the package systems, not the GNU/Linux

Re: relocatable.texi: remove mention of OpenBSD?

On Tue, 26 Jan 2021 at 09:36, Bruno Haible wrote: > Hi Reuben, > > > doc/relocatable.texi contains the following text: > > > > > > > Also, installation with > > > @option{--enable-relocatable} might not work on OpenBSD, when the > > > package contains shared libraries and libtool versions

Re: Possible bug in configure script

On Tue, Jan 26, 2021 at 12:32 PM Bruno Haible wrote: > > Jeffrey Walton wrote: > > > Jeffrey Walton wrote: > > > > Placing flags in CC breaks other scripts. For example, this no longer > > > > works: > > > > > > > > if [[ ! $(command -v "${CC}") ]]; then > > > > echo "The compiler is

[PATCH] maintainer-makefile: Mimic bootstrap's gnulib-srcdir guessing.

Hi! I've noticed in a couple of projects that use bootstrap, without a gnulib git submodule, and where $GNULIB_SRCDIR is set during bootstrap, that syntax-check will print some spurious errors like this: prohibit_intprops_without_use Can't open ./gnulib/lib/intprops.h: Filen eller katalogen

Re: relocatable.texi: improve reference to packaging systems?

Reuben Thomas wrote: > If you still don't agree, then I suggest: "The package systems of most > GNU/Linux distributions." The same problem exists for distros on macOS (MacPorts, Fink, ...), Solaris (OpenCSW), and so on. Also, Wikipedia [1][2] uses the term "package management systems", so let's

Re: relocatable.texi: improve reference to packaging systems?

On Tue, 26 Jan 2021 at 16:40, Bruno Haible wrote: > Reuben Thomas wrote: > > If you still don't agree, then I suggest: "The package systems of most > > GNU/Linux distributions." > > The same problem exists for distros on macOS (MacPorts, Fink, ...), Solaris > (OpenCSW), and so on. > > Also,

libunistring version detection w/ "configure -C"

At , there is a patch to libunistring version detection w/ "configure -C". Does that look right? It seems strange to me. -- Thien-Thi Nguyen --- (defun responsep (query) ; (2021) Software

Re: Possible bug in configure script

Jeffrey Walton wrote: > > Jeffrey Walton wrote: > > > Placing flags in CC breaks other scripts. For example, this no longer > > > works: > > > > > > if [[ ! $(command -v "${CC}") ]]; then > > > echo "The compiler is not valid. Please install a compiler." > > > exit 1 > > >

Re: gnulib commit 0aa8ef42465 - free: Fix warning breaks parted

Hi, Brian C. Lane wrote: > I encountered this while trying to prepare a new release of parted 3.4, > after updating gnulib to commits past b07286e464 (free-posix: port to > GNU/Linux) builds exit with this puzzling error: > > make[4]: Entering directory

gnulib commit 0aa8ef42465 - free: Fix warning breaks parted

I encountered this while trying to prepare a new release of parted 3.4, after updating gnulib to commits past b07286e464 (free-posix: port to GNU/Linux) builds exit with this puzzling error: make[4]: Entering directory '/home/bcl/Red_Hat/projs/parted/libparted/labels' CC aix.lo In file

Re: relocatable.texi: remove mention of OpenBSD?

Reuben Thomas wrote: > I believe the prediction has come true; from libtool's NEWS for version > 2.1b: > > - On (AIX?,) HP-UX, and OpenBSD, hardcoding has been changed to prefer > rpath over absolute dependent library names. This fixes DESTDIR > installs, among others, on the

Re: [PATCH] maintainer-makefile: Mimic bootstrap's gnulib-srcdir guessing.

Simon Josefsson wrote: > See the beginning of my e-mail: > > Hi! I've noticed in a couple of projects that use bootstrap, without a >^ > gnulib git submodule, and where $GNULIB_SRCDIR is set during bootstrap, >

Re: [PATCH] maintainer-makefile: Mimic bootstrap's gnulib-srcdir guessing.

Bruno Haible writes: > Hi Simon, > >> The reason is top/maint.mk has >> >> # You can override this variable in cfg.mk if your gnulib submodule lives >> # in a different location. >> gnulib_dir ?= $(srcdir)/gnulib >> >> and that directory doesn't exist if bootstrap used $GNULIB_SRCDIR. > >

Re: Possible bug in configure script

Paul Eggert writes: > On 1/25/21 7:55 PM, Jeffrey Walton wrote: > >>> Jeffrey Walton wrote: Placing flags in CC breaks other scripts. For example, this no longer works: if [[ ! $(command -v "${CC}") ]]; then echo "The compiler is not valid. Please install

Re: [PATCH] maintainer-makefile: Mimic bootstrap's gnulib-srcdir guessing.

Hi Simon, > The reason is top/maint.mk has > > # You can override this variable in cfg.mk if your gnulib submodule lives > # in a different location. > gnulib_dir ?= $(srcdir)/gnulib > > and that directory doesn't exist if bootstrap used $GNULIB_SRCDIR. Instead of relying on an environment