Lionel,<br> On the first three items, won't we always have to keep these until all of the packages either support autoreconfiguring or start using libtool 2.4? Like I said before, I ran into three packages that wouldn't autoreconfigure, so they would still need the traditional approach. Also, I haven't had a chance to really investigate this, but isn't TARGET_LDFLAGS+=-L$(STAGING_DIR)/lib -L$(STAGING_DIR)/usr/lib also needed by gentargets to link to the correct libraries?<br>
As for my setup, the only difference is, I compiled libtool with --with-sysroot (no directory given), and I don't configure the package with it. libtool gets the sysroot directory from gcc's sysroot, if none is specified. Everything else is the same. What kind of problems did you encounter? Was it just the problem with autoreconfiguring packages?<br>
<br>Martin<br><br><div class="gmail_quote">On Sun, Oct 3, 2010 at 4:47 PM, Lionel Landwerlin <span dir="ltr"><<a href="mailto:llandwerlin@gmail.com">llandwerlin@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
As long as we keep the following things, we can bump to 2.2 or 2.4 :<br>
* sed pass on .la files<br>
* Add -L$(STAGING_DIR)/lib -L$(STAGING_DIR)/usr/lib to LDFLAGS<br>
* patches for encountered libtool versions<br>
<br>
I always took the hypothesis that we wanted to get rid of the first 2,<br>
and wanted to keep the third only for special cases.<br>
<br>
I encountered problem with libtool 2.4 for several packages under the<br>
following conditions :<br>
* run autoreconf on the package<br>
* do not apply the libtool patch<br>
* configure the package with --with-sysroot=$(STAGING_DIR) option<br>
<br>
Martin, did you have the same setup ?<br>
<br>
I guess we're back to the current situation if we don't pass the<br>
--with-sysroot option and we apply a libtool patch for the correct<br>
libtool version.<br>
<br>
Regards,<br>
<font color="#888888"><br>
--<br>
Lionel Landwerlin<br>
<br>
Le dimanche 03 octobre 2010 à 15:36 -0700, Martin Banky a écrit :<br>
</font><div><div></div><div class="h5">> If you want to integrate my patches, I would like to submit a new set<br>
> of patches with some changes in preparation for libtool 2.4, mainly<br>
> with <a href="http://Makefile.autotools.in" target="_blank">Makefile.autotools.in</a>. I have it setup now to distinguish between<br>
> 1.5.x, 2.2.x, and 2.4. Also, in working on converting the packages to<br>
> either gentargets or autotargets, I've been noticing a lot of packages<br>
> have their own libtool patch. I would like to go through, and clean<br>
> them up. I have a question, why can't we upgrade to libtool 2.4? I've<br>
> been running it now since I first posted the heads up patch, and have<br>
> used it with the sysroot option turned on without any obvious issues.<br>
> If the sysroot option is an issue, we could turn it off for now and<br>
> use the libtool patches until we integrate the sysroot option<br>
> properly, right? The imagemagick patch set that I posted, was first<br>
> done with libtool 2.4 and autoreconfigure turned on. I wanted to make<br>
> sure that it would work properly in this configuration, in preparation<br>
> of the coming changes. It was then actually posted with<br>
> autoreconfigure turned off and using the libtool patch. As a side<br>
> note, I just realized that imagemagick is using libtool 2.2.x, which<br>
> means that it's incorporation is blocked until either I add it's own<br>
> libtool patch or we commit my libtool patch set. Sorry about that. If<br>
> anyone would like me to add the libtool patch to imagemagick, and<br>
> repost, let me know.<br>
><br>
> Martin<br>
><br>
> On Sun, Oct 3, 2010 at 7:22 AM, Thomas Petazzoni<br>
> <<a href="mailto:thomas.petazzoni@free-electrons.com">thomas.petazzoni@free-electrons.com</a>> wrote:<br>
> Hello,<br>
><br>
> On Sun, 03 Oct 2010 15:22:26 +0200<br>
> Lionel Landwerlin <<a href="mailto:llandwerlin@gmail.com">llandwerlin@gmail.com</a>> wrote:<br>
><br>
> > Here is what I would like to us to do for the next<br>
> releases :<br>
> ><br>
> > 1) Bump libtool package to 2.2, more and more packages<br>
> require libtool<br>
> > 2.2, and we're stuck to not autoreconfigure them without<br>
> 2.2. This is<br>
> > already creating problems to Thomas when trying to bump host<br>
> > libglib/libgtk packages.<br>
><br>
><br>
> 1a) Integrate Martin Banky's proposal so that packages using<br>
> libtool<br>
> 2.2 can work without the need to autoreconfigure them.<br>
><br>
> > 2) Eventually integrate some patches to libtool 2.2 to be<br>
> able to<br>
> > cross compile autoreconfigured packages.<br>
> ><br>
> > 3) When the libtool 2.4 sysroot issue is sorted out, bump to<br>
> libtool<br>
> > 2.4 and get rid of the patches integrated in 2).<br>
> ><br>
> > I think 1) is mandatory for 2010.11.<br>
><br>
><br>
> And 1a).<br>
><br>
> So, I would suggest :<br>
><br>
> *) Peter merges Martin Banky's set of patches on libtool<br>
><br>
> <a href="http://lists.busybox.net/pipermail/buildroot/2010-September/037505.html" target="_blank">http://lists.busybox.net/pipermail/buildroot/2010-September/037505.html</a><br>
><br>
><br>
> *) Lionel, could you propose a patch that just bumps libtool<br>
> to 2.2 ?<br>
><br>
> Lionel, Martin, Peter, what do you think ?<br>
><br>
> Thanks,<br>
><br>
> Thomas<br>
> --<br>
> Thomas Petazzoni, Free Electrons<br>
> Kernel, drivers, real-time and embedded Linux<br>
> development, consulting, training and support.<br>
> <a href="http://free-electrons.com" target="_blank">http://free-electrons.com</a><br>
> _______________________________________________<br>
><br>
><br>
> buildroot mailing list<br>
> <a href="mailto:buildroot@busybox.net">buildroot@busybox.net</a><br>
> <a href="http://lists.busybox.net/mailman/listinfo/buildroot" target="_blank">http://lists.busybox.net/mailman/listinfo/buildroot</a><br>
><br>
><br>
> _______________________________________________<br>
> buildroot mailing list<br>
> <a href="mailto:buildroot@busybox.net">buildroot@busybox.net</a><br>
> <a href="http://lists.busybox.net/mailman/listinfo/buildroot" target="_blank">http://lists.busybox.net/mailman/listinfo/buildroot</a><br>
<br>
<br>
</div></div></blockquote></div><br>