Re: cwrapper generates long strings.

2010-10-04 Thread Peter Rosin
Den 2010-10-04 19:58 skrev Ralf Wildenhues: > The updated patch is fine. Pushed, and again thanks for reviewing! Cheers, Peter

Re: cwrapper generates long strings.

2010-10-04 Thread Ralf Wildenhues
* Peter Rosin wrote on Mon, Oct 04, 2010 at 10:02:15AM CEST: > > I wrote a loop appending the first PATH component until the length > exceeds the limit. The longest possible PATH should be 499 characters > this way, which seems OK to me, and it should have no "wild" components. Cool. > Den 2010

Re: cwrapper generates long strings.

2010-10-04 Thread Peter Rosin
Den 2010-10-04 07:00 skrev Ralf Wildenhues: > * Peter Rosin wrote on Sun, Oct 03, 2010 at 08:28:47PM CEST: >> Den 2010-10-03 09:01 skrev Ralf Wildenhues: +for i in 25 50 75 100 125 150 175 200 225 250 +do + PATH="$PATH$PATH_SEPARATOR/somewhere-that-eksists-not" > >>> Does $LIBTOOL

Re: cwrapper generates long strings.

2010-10-04 Thread Ralf Wildenhues
* Peter Rosin wrote on Sun, Oct 03, 2010 at 08:28:47PM CEST: > Den 2010-10-03 09:01 skrev Ralf Wildenhues: > >> +for i in 25 50 75 100 125 150 175 200 225 250 > >> +do > >> + PATH="$PATH$PATH_SEPARATOR/somewhere-that-eksists-not" > > Does $LIBTOOL or the autotest machinery ever intentionally try

Re: cwrapper generates long strings.

2010-10-03 Thread Peter Rosin
Den 2010-10-03 09:01 skrev Ralf Wildenhues: >> I used 250 at the limit in the test as the 79 characters from the string >> splitter in ltmain might be doubled due to C string escapes and then I >> added some extra margin for quotes and the ", f);" trailer. Still below >> 255 which might be an arbi

Re: cwrapper generates long strings.

2010-10-03 Thread Ralf Wildenhues
Hi Peter, * Peter Rosin wrote on Sat, Oct 02, 2010 at 11:33:02PM CEST: > Den 2010-10-02 13:53 skrev Ralf Wildenhues: > > Yes. Well, we might get the odd report about the Cygwin non-binmode > > mount where the CR NL messes up things, but otherwise, it should work. > > If you are on a text mount,

Re: cwrapper generates long strings.

2010-10-02 Thread Peter Rosin
Den 2010-10-02 13:53 skrev Ralf Wildenhues: > * Peter Rosin wrote on Sat, Oct 02, 2010 at 01:42:02PM CEST: >> Den 2010-10-02 08:32 skrev Ralf Wildenhues: +$SED -n -e ' +s/^\(.\{79\}\)\(..*\)/\1\n\2/ >>> >>> \n is portable only in the regex part, but not in the replacement part. >>

Re: cwrapper generates long strings.

2010-10-02 Thread Ralf Wildenhues
[ dropped bug-libtool ] * Peter Rosin wrote on Sat, Oct 02, 2010 at 01:42:02PM CEST: > Den 2010-10-02 08:32 skrev Ralf Wildenhues: > >> +$SED -n -e ' > >> +s/^\(.\{79\}\)\(..*\)/\1\n\2/ > > > > \n is portable only in the regex part, but not in the replacement part. > > For that you need b

Re: cwrapper generates long strings.

2010-10-02 Thread Peter Rosin
Den 2010-10-02 08:32 skrev Ralf Wildenhues: > Hi Peter, > > * Peter Rosin wrote on Fri, Oct 01, 2010 at 11:22:54PM CEST: >> Subject: [PATCH] cwrapper: split long lines when dumping the wrapper script. >> >> * libltdl/config/ltmain.m4sh (func_emit_cwrapperexe_src): If >> the wrapper script contains

Re: cwrapper generates long strings.

2010-10-01 Thread Ralf Wildenhues
Hi Peter, * Peter Rosin wrote on Fri, Oct 01, 2010 at 11:22:54PM CEST: > Subject: [PATCH] cwrapper: split long lines when dumping the wrapper script. > > * libltdl/config/ltmain.m4sh (func_emit_cwrapperexe_src): If > the wrapper script contains long lines, split them for > readability and to conf

Re: cwrapper generates long strings.

2010-10-01 Thread Peter Rosin
Hi Chuck, Den 2010-10-01 16:03 skrev Charles Wilson: > On 10/1/2010 7:28 AM, Peter Rosin wrote: >> I.e. I have this on line 865 in lt-main.c: >> >> fputs ("relink_command=\"(cd >> /c/cygwin/home/peda/libtool/git/msvc/tests/testsuite.dir/112; >> PATH=\\\"/LOADS:/OF:/ENTRIES\\\"; export PATH; >