On 8/22/2010 11:26 AM, Ralf Wildenhues wrote:
> Hello Paolo, Charles,
>
> I think these are the leftover items, right?
>
> * Paolo Bonzini wrote on Fri, Aug 13, 2010 at 03:23:02AM CEST:
>> 4) patch for old libtool, to not barf on '='
>> 6) support in libltdl for '=' in .la files
> 7) doc updates.
Yes, that is the entire remaining list IIRC.
> I think the sysroot branch is in pretty good shape and all remaining
> items can be argued to not be regressions. Thus, it might be a good
> idea to merge the branch to master now so that we can easily test it all
> together. So, barring disagreement from any of the other maintainers
> within the next 72 hours, let's merge the current sysroot branch.
I agree.
> Of course, we should still aim to complete as much as possible before
> the release.
Of course (especially docs).
>> I would like some help for 6 mostly due to lack of time on my part.
>> The main design point here is how to pass the sysroot to libltdl.
>
> For me, that will definitely have to wait 'till next weekend, sorry.
Ack.
Given the tentative plan to roll out a libtool-2.2.next by "the end of
this month" (august) with "some msvc support" -- and Peter's statement
that some of his remaining msvc patches require my cross-path support
patch, I'm going to roll that out (against master, not sysroot) later
today, in preference to working on the libltdl patches.
I've tested the cross-path patch (in the past) in the following
configurations:
cygwin (native)
mingw (native; e.g. msys in its normal "pretend I
am mingw32" personality)
linux (native)
linux->mingw cross (*)
I plan to repeat ALL of those tests, plus
cygwin->mingw cross
linux->cygwin cross (*) (**)
msys->msys (native; e.g. msys in its "okay, I'm actually
a cygwin-like unix environment" personality)
(*) as with all cross configurations, the -exec tests are skipped as
part of the "official" test run. However, I'll spot check by manually
checking the contents of the c wrapper source code, and manually running
the executable from the builddir.
(**) I need to actually compile and install these tools on my linux box;
so far there are no public "linux->cygwin" cross tool chains available
"out there" for immediate use.
Anyway, this test series will take DAYS to complete...so I'd appreciate
it if the review (or, the reviewER's refresh/reread of the OLD reviews,
whose links I will post) could commence concurrent with my generation of
the test results. I don't expect any surprise in those test results, tho...
--
Chuck
