[tlbuild] 2014 builds for FreeBSD

[Marc Baudoin]

Alan BRASLAU <alan.braslau at cea.fr> écrit :
> On Wed, 2 Apr 2014 08:55:01 +0200
> Peter Breitenlohner <peb at mppmu.mpg.de> wrote:
> 
> > On Tue, 1 Apr 2014, Alan BRASLAU wrote:
> > 
> > > On (some) BSD systems, the TL build fails as sed is hardwired and
> > > appears that gsed extensions are used. A solution would be to put
> > > ${SED-sed} at appropriate places so that one can define SED=gsed in
> > > the environment.
> > 
> > Hi Alan,
> > 
> > (1) it would help to know the exact failure(s), i.e., during 'make'
> > or 'make check', in which directory, which GNU extensions.
> > 
> > (2) the configure scripts should use AC_PROG_SED (see the Autoconf
> > manual) but perhaps some do not and probably some shell scripts for
> > tests do not use $SED.
> > 
> > (3) with AC_PROG_SED configure should automatically select sed or
> > gsed, but having SED=gsed on the command line for configure or in the
> > environment certainly does no harm.
> 
> In fact, the problem is not sed that is hardwired and relies on GNU
> extensions, but rather make that is (still) hardwired in a few places
> and relies on GNU extensions. Setting
> 	export MAKE=/usr/local/bin/gmake
> is not sufficient and here and there /usr/bin/make is used.
> The first manifestations of this (g)make error are calling sed with
> incorrect syntax, thus leading me to hastily believe that gsed was the
> culprit.
> 
> My (temporary) solution is to put a symbolic link
> 	ln -s /usr/local/bin/gmake ~/bin/make
> with
> 	PATH=~/bin:$PATH; ./Build

The right way to do this is to set the TL_MAKE environment
variable (which is used by the Build script).  I do this on a
NetBSD system (whose problems are quite similar regarding GNU
extensions than on FreeBSD):

TL_MAKE=gmake ./Build

In fact, I also do:

TL_MAKE=gmake LDFLAGS='-L/usr/X11R7/lib -Wl,-rpath,/usr/X11R7/lib' ./Build

to get things right with X11 shared libraries (might be similar
on FreeBSD).