Re: cross-compiling question: static libraries and binaries to different places?

[Guido Draheim]

Es schrieb Dan Kegel:
 
 Guido Draheim wrote:
  ... See - the libtool crossgcc support (to which I did
  contribute some of the time) can simply ask the cross-gcc
  for the local searchpath via `gcc -print-search-dirs` -
  this is needed for win32 compiles atleast, and I have a
  patch on my disk which generalizes the idea for all
  cross-gcc targets (since there have been problems with
  crosscompiling linux-to-linux).
 
 You mean this?

YES!! I just didn't know how to make an argument about it on
the mailinglist, may be the sheer number of our voices can
avoid that ;-) - oh btw your patch needs an enhancement for
the last s/;/ /g since on unix a : is used. There was a
discussion a while back about the use of path_separator here,
but the final solution was to cut the line into three, and
examine the raw print-search-dirs string for occurrences of
;. If yes, use that one as the path_separator, if no
then use : and assume that unix path parts do never 
contain ; either but have : as the pathseparator. (and
IIRC, there was some rumour about differences as with a gcc 
on win32 hosted in a unix pesonality, so you can't be that 
sure about the ; even on win32.). Anyway, you actually got
the idea, and I didn't say anything explicit, so it makes
me confident that this is an obvious flaw (a bug?) in the
libtool crosscompiling support. It needs to be fixed.

go ahead, I'm all with you, guido

 
 --- libtool.m4.orig Thu Mar  7 16:58:42 2002
 +++ libtool.m4  Thu Mar  7 17:04:23 2002
 @@ -2312,6 +2312,13 @@
dynamic_linker=no
;;
  esac
 +
 +# When cross-compiling, get the list of system library directories
 +# from gcc if possible, since hardcoded paths above are surely wrong.
 +if test $GCC = yes  test $cross_compiling = yes; then
 +  sys_lib_search_path_spec=`$CC -print-search-dirs | grep ^libraries: | sed -e 
s/^libraries:// -e s/;/ /g`
 +fi
 +
  AC_MSG_RESULT([$dynamic_linker])
  test $dynamic_linker = no  can_build_shared=no
  ##
 
 I just spent two hours realizing why libtool could not link with shared
 libraries when cross-compiling; it ended up being exactly the thing
 you're talking about.  I created a patch according to your suggestion
 on the libtool mailing list, and it makes life much nicer.
 
 Is this in CVS yet?  By golly, it sure needs to be.
 
 - Dan

___
Libtool mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/libtool

Autoconf 2.53 is released

[Akim Demaille]

The Autoconf team is extremely pleased to announce Autoconf 2.53.  We
hope it will address your problems, and make your life easier.

Enjoy!

Akim, Alexandre, Jim, Paul, Tom.

  ftp://ftp.gnu.org/gnu/autoconf/autoconf-2.53.tar.gz   (973 kB)
  ftp://ftp.gnu.org/gnu/autoconf/autoconf-2.53.tar.bz2  (743 kB)

And here are xdelta-style diffs

  ftp://ftp.gnu.org/gnu/autoconf/autoconf-2.52-2.53.xdelta   (215 kB)

Here are the MD5 and SHA1 signatures for the compressed tar files:

42948310deb847982004a3b0d936f7bb  autoconf-2.53.tar.gz
c121b003f51e293c2bf5a6105c721388  autoconf-2.53.tar.bz2
a9fe8460b4ed6f279f3d3f8a73eb39b19e93dc98  autoconf-2.53.tar.gz
c99aa737c0fe24c1cfcf0701e614e69f3ff07209  autoconf-2.53.tar.bz2

NEWS:

** Requirements

  Perl 5.005_03 or later is required: autom4te is written in Perl and is
  needed by autoconf.  autoheader, autoreconf, ifnames, and autoscan are
  rewritten in Perl.

** Documentation

- AC_INIT
  Argument requirements, output variables, defined macros.
- M4sugar, M4sh, Autotest
  First sketch.
- Double quoting macros
  AC_TRY_CPP, AC_TRY_COMPILE, AC_TRY_LINK and AC_TRY_RUN.
- Licensing
  The Autoconf manual is now distributed under the terms of the GNU FDL.
- Section `Hosts and Cross-Compilation'
  Explains the rationale for the 2.5x changes in the cross-compilation
  chain, and in the relationships between build, host, and target
  types.
  Emphasizes that `cross-compilation' == `--host is given'.
  If you are working on compilers etc., be sure to read this section.
- Section `AC_LIBOBJ vs. LIBOBJS'
  Explains why assigning LIBOBJS directly is now an error.
  Details how to update the code.

** configure

- $LINENO
  Now used instead of hard coded line numbers.
  This eases the comparison of `configure's, and diminishes the
  pressure over control version archives.
  Automatic replacement for shells that don't support this feature.
- New output variables
  @builddir@, @top_builddir@, @abs_srcdir@, @abs_top_srcdir@, @abs_builddir@,
  @abs_top_builddir@.

** Emacs

  Autoconf and Autotest modes are provided.

** Executables

- autom4te
  New, used by the Autoconf suite to cache and speed up most processing.
- --force, -f
  Supported by autom4te, autoconf and autoheader.
- --include, -I
  Replaces --autoconf-dir and --localdir in autoconf, autoheader,
  autoupdate, and autoreconf.
- autoreconf
  No longer passes --cygnus, --foreign, --gnits, --gnu, --include-deps:
  automake options are to be given via AUTOMAKE_OPTIONS.
- autoreconf
  Runs gettextize and libtoolize when appropriate.
- autoreconf
  --m4dir is no longer supported.
- autoreconf
  Now runs only in the specified directories, defaulting to `.',
  but understands AC_CONFIG_SUBDIRS for dependent directories.
  Before, it used to run on all the `configure.ac' found in the
  current tree.
  Independent packages are properly updated.

** Bug fixes

- The top level $prefix is propagated to the AC_CONFIG_SUBDIRS configures.
- AC_TRY_RUN
  Under the user pressure, $? is finally available.  Probably a mistake.
- AC_F77_LIBRARY_LDFLAGS now supports the HP/UX f90 compiler.
- Precious variables accumulation
  config.status could stack several copies of the precious variables
  assignments.
- AC_PATH_PROG and family.
  Works properly when given a literal path.
- AC_FUNC_SETPGRP
  Somewhere since 2.13, the result had been reversed.

** C Macros

- AC_C_BIGENDIAN supports the cross-compiling case.
- AC_C_BIGENDIAN accepts ACTION-IF-TRUE, ACTION-IF-FALSE, and
  ACTION-IF-UNKNOWN arguments.  All are facultative, and the default
  for ACTION-IF-TRUE is to define WORDS_BIGENDIAN like AC_C_BIGENDIAN
  always did.
- AC_C_LONG_DOUBLE now succeeds only if `long double' has more range or
  precision than `double'.

** Generic macros

- AC_INIT
  It now defines the preprocessor symbols PACKAGE_NAME,
  PACKAGE_TARNAME, PACKAGE_VERSION, PACKAGE_STRING, and
  PACKAGE_BUGREPORT.

- AC_INIT
  Admits a fourth optional parameter: the tar name.

- AC_CONFIG_COMMANDS, HEADERS, FILES, LINKS.
  Provide the user with srcdir, ac_srcdir, ac_top_srcdir, ac_builddir,
  ac_top_builddir, ac_abs_srcdir, ac_abs_top_srcdir, ac_abs_builddir,
  ac_abs_top_builddir.

- AC_CONFIG_COMMANDS, HEADERS, FILES, LINKS and AC_OUTPUT.
  Are much less expensive when using long lists of files.

- AC_PREFIX_PROGRAM
  Works with shell variables, and non alphanumeric names.

** Library macros

- AC_FUNC_STRERROR_R now sets STRERROR_R_CHAR_P, not HAVE_WORKING_STRERROR_R,
  because POSIX 1003.1-200x draft 7 says strerror_r returns int, not char *.

- AC_FUNC_STRTOD substitutes POW_LIB.

- AC_FUNC_STRNLEN
  New.

___
Libtool mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/libtool