Re: [PATCH] Path conversion documentation

On 8/30/2010 12:32 AM, Gary V. Vaughan wrote: >> Documentation updates for path conversion. Plus a missed >> path<->file-name terminology correction. > > Awesome! Thanks for that. An interesting read. > >> OK to push? > > Please do. Two patches though - otherwise we have two independent > cha

Re: [PATCH] Path conversion documentation

Hi Chuck, On 30 Aug 2010, at 06:50, Charles Wilson wrote: > * doc/libtool.texi (Platform quirks): Add new subsections > 'Cross compiling' and 'File name/path conversion'. > * libltdl/config/ltmain.m4sh (func_convert_file_check): Update > comments and warning message. > func_convert_path_check): Up

Re: [PATCH] [cygwin|mingw]: Add cross-compile support to cwrapper (take 6)

On 8/26/2010 2:26 AM, Peter Rosin wrote: > This is my current queue of libtool patches. They need more work. > In particular, I don't know if 0008-Slashify-instead-of-backslashify > is even remotely acceptable. The subject has been up before and I > think Chuck had some issue with it, but don't rem

Re: [PATCH] [cygwin|mingw]: Add cross-compile support to cwrapper (take 6)

On 8/29/2010 12:21 PM, Peter Rosin wrote: > Den 2010-08-28 08:57 skrev Charles Wilson: >> Rename file/path conversion functions > > You missed one instance here. Pushed the attached as obvious... Thanks. -- Chuck

[PATCH] Path conversion documentation

* doc/libtool.texi (Platform quirks): Add new subsections 'Cross compiling' and 'File name/path conversion'. * libltdl/config/ltmain.m4sh (func_convert_file_check): Update comments and warning message. func_convert_path_check): Update warning message. --- Documentation updates for path conversion.

Re: [PATCH] [cygwin|mingw]: Add cross-compile support to cwrapper (take 6)

Peter Rosin wrote: Den 2010-08-27 00:27 skrev Roumen Petrov: Ralf Wildenhues wrote: Hi Charles, [SNIP] + func_wine_to_win32_path_result="$1" + if test -n "$1"; then +# Unfortunately, winepath does not exit with a non-zero +# error code, so we are forced to check the contents of +

Re: [PATCH 0/3]: Another go at LTO support

Test results for this patch series more or less look the way they did with the old proposed patch, and more reflect the state of binutils and GCC than that of Libtool I would say; there might be ways to work around them though, dunno yet. 1) With -flto in CC, CXX, F77, FC and LDFLAGS, I get failur

[PATCH 0/3]: Another go at LTO support

OK, so the issues I had with was both changing output_verbose_link_cmd to something that might work worse in a number of setups, and on the other hand having a reliable way to get at postdeps in presence of -flto or -fwhopr or so. Here'

[PATCH 3/3] Support GCC LTO on GNU/Linux.

* libltdl/config/ltmain.m4sh (func_mode_link): Allow through flags matching -O*, -flto*, -fwhopr, -fuse-linker-plugin. * libltdl/m4/libtool.m4 (_LT_CMD_GLOBAL_SYMBOLS): Drop symbols starting with __gnu_lto. (_LT_LINKER_SHLIBS) [linux] : Add $pic_flag for GCC. (_LT_LANG_CXX_CONFIG) [linux] : Likewis

[PATCH 2/3] Disable GCC LTO for verbose library extraction.

* libltdl/m4/libtool.m4 (_LT_SYS_HIDDEN_LIBDEPS): Temporarily append -fno-lto or -fno-whopr to CFLAGS if CC or CFLAGS (which are substituted with the per-language variables here) contain -flto or match -fwhopr*, respectively. Signed-off-by: Ralf Wildenhues --- ChangeLog |6 ++

Re: proposed autobuild_mode naming scheme

Hello Simon, * Ralf Wildenhues wrote on Sun, Aug 22, 2010 at 08:44:57PM CEST: > > configure: autobuild mode... default > [...] > > Autobuild uses a few strings to categorize log results: package version, > $build, $host, hostname, time and date, and a so-called "mode" which my > patch sets with t

[PATCH 1/3] Save and restore CFLAGS properly inside libtool.m4 macros.

* libltdl/m4/libtool.m4 (_LT_CMD_GLOBAL_SYMBOLS): Use different temporary variables for saved and restored values of $LIBS, $CFLAGS, to avoid overlap with the *_CONFIG macros. (_LT_LANG_CXX_CONFIG, _LT_LANG_F77_CONFIG, _LT_LANG_FC_CONFIG) (_LT_LANG_GCJ_CONFIG, _LT_LANG_RC_CONFIG): Also save and res

Re: [PATCH] [cygwin|mingw]: Add cross-compile support to cwrapper (take 6)

Den 2010-08-28 08:57 skrev Charles Wilson: > Rename file/path conversion functions > > * TODO: Document QoI issue with file name conversion functions. > * Makefile.am (TESTS_ENVIRONMENT): Renamed cache variable > lt_cv_to_host_path_cmd to lt_cv_to_host_file_cmd; Renamed > envir

Re: ${var:+"quo ted"} and similar, inside unquoted here-docs

* Ralf Wildenhues wrote on Sun, Aug 29, 2010 at 04:48:34PM CEST: > With Solaris 10 sh (and others): > > cat < ${var-"quo ted"} > EOF > > "quo ted" I'm working around the issue in Libtool like this. Cheers, Ralf Work around yet another shell quoting portability issue. * configure

${var:+"quo ted"} and similar, inside unquoted here-docs

With Solaris 10 sh (and others): cat