On 12/6/06, Bob Rossi <[EMAIL PROTECTED]> wrote:
On Wed, Dec 06, 2006 at 08:30:55AM +1100, John Vandenberg wrote:
> The problem appears to be that libtool is now emitting a blank line
> before the line that contains the version string; try
>
> $ libtool --version 2>/dev/null | sed -e
> '/^$/d;s/([^)]*)//g;s/^[^0-9]*//;s/[- ].*//g;q'
Works like a charm.
$ libtool --version 2>/dev/null | sed -e
'/^$/d;s/([^)]*)//g;s/^[^0-9]*//;s/[- ].*//g;q'
1.5.23a
I have grabbed a copy of libtool-1.5.22 and 1.5.23a. I can confirm
that 1.5.23a is emitting a blank line first, while 1.5.22 does not.
Sounds like a bug in their development builds.
> >> >So, after patching autoconf, and making these two patches to apr, I was
> >> >able to cross compile on cygwin with this command,
> >> >
> >> > ./configure apr_cv_tcp_nodelay_with_cork=no
> >ac_cv_func_setpgrp_void=yes
> >> > ac_cv_file__dev_zero=no --build=i686-pc-cygwin --host=i686-pc-mingw32
> >> > CC='gcc -mno-cygwin' CXX='g++ -mno-cygwin'
> >> >
> >> >I was able to take a sample program, and run it on a machine that did
> >> >not have cygwin installed, and it ran fine. It was simply a hello world
> >> >type program with apr stuff in it.
> >>
> >> Have you tried the test suite?
> >
> >Nope, great idea. Attached is the results. I'm going to try a native
> >build of mingw to make sure the results are the same. How do these
> >results look?
>
> They look comparable to the last msys/MinGW test results I have seen.
>
> http://marc2.theaimsgroup.com/?l=apr-dev&m=114506483217503&w=2
Intereseting. So everything appears to be correct? For some reason,
testsock works now, and it didn't before.
Great! Hopefully in another few months testdso will also start
working correctly :-)
I'd love to see the sed command go into apr.
We should first check whether the libtool developers intentionally
added that blank line; if they can fix the regression on their side,
it means that the next stable version of libtool will work with older
source tarballs of apr.
--
John
