Brad Smith <b...@comstyle.com> writes:

> The native ABI is placed in /usr/lib, the 32-bit ABI on a multi-lib
> 64-bit host is placed in /usr/lib32.
>
> Signed-off-by: Brad Smith <b...@comstyle.com>
>
> ---
>  configure.ac | 12 ++++++++----
>  1 file changed, 8 insertions(+), 4 deletions(-)
>
> diff --git a/configure.ac b/configure.ac
> index 39b5b148..b9f48769 100644
> --- a/configure.ac
> +++ b/configure.ac
> @@ -428,11 +428,15 @@ if test "x$ABI" != xstandard ; then
>           && libdir='${exec_prefix}/'"lib${ABI}"
>       fi
>       ;;
> -      # On freebsd, it seems 32-bit libraries are in lib32,
> -      # and 64-bit in lib. Don't know about "kfreebsd", does
> -      # it follow the Linux fhs conventions?
> +      # On FreeBSD, 32-bit libraries in a multi-lib environment on a
> +      # 64-bit host are placed in lib32. Don't know about "kfreebsd",
> +      # does it follow the Linux FHS conventions?
>        *:freebsd*:32)
> -     libdir='${exec_prefix}/lib32'
> +     if test "$cross_compiling" = yes ; then
> +       libdir='${exec_prefix}/lib32'
> +     else
> +       libdir='${exec_prefix}/lib'
> +     fi

Hi, can you explain the check of cross_compiling? I would expect that a
typical 32-bit build on a 64-bit host would be something like

  ./configure CC='gcc -m32'

Then libraries should be installed in ../lib32, if I understand your
comment correctly, but cross_compiling = no, so with the above change,
they'll end up in .../lib.

Note that in a 32-bit build on a 32-bit host, the configure script
should leave ABI = standard, and then all of these libdir tweaks are
skipped. 

The only reason that cross_compiling is checked in the linux case is
that, unfortunately, conventions differ between linux distributions. The
configure script tries to guess based on existence of directories on the
build system, but that way of guessing makes no sense for a cross
compile.

Regards,
/Niels

-- 
Niels Möller. PGP key CB4962D070D77D7FCB8BA36271D8F1FF368C6677.
Internet email is subject to wholesale government surveillance.
_______________________________________________
nettle-bugs mailing list -- nettle-bugs@lists.lysator.liu.se
To unsubscribe send an email to nettle-bugs-le...@lists.lysator.liu.se

Reply via email to