[yocto] libtool problem?

[Hans Beckérus]

On Fri, Sep 6, 2013 at 10:25 AM, Richard Purdie
<richard.purdie at linuxfoundation.org> wrote:
> On Thu, 2013-09-05 at 17:44 +0200, Hans Beckérus wrote:
>> I have now prepared a patch that will fix this problem i Yocto. Since
>> no one (so far) commented on this issue I interpreted the silence as
>> that nothing has been done about this bug.
>
> I think that coming up to release, we've all be focusing on that. Once
> you'd identified a specific issue like this, filing a bug report in the
> bugzilla can be a good way of getting people's attention, particularly
> when you have a patch.
>
> The key question is the help message:
>
>  --with-libtool-sysroot=DIR Search for dependent libraries within DIR
>                        (or the compiler's sysroot if not specified).
>
> so yes, this sounds like a genuine bug in libtool. Would you like to
> send a patch to the OE-Core mailing list which adds your patch, along
> with a description of the problem in the commit messages, a proper patch
> header (description and Upstream-Status:) and signed-off-by line?
>
> If you do, I think we'll likely include it. If not, it will need to wait
> for someone to turn this into a full commit which might take a little
> longer but it does look like a good change.
>
Hi Richard, I am fully aware that people are currently on their toes
for the upcoming release.
I did not mean to sound harsh, if that was how it came out, I am truly
sorry. It is just that I am used to quick feedback :) and since I
heard nothing I though maybe this problem is to specific for anyone to
actually comment on it. As I said, this is really a bug in libtool so
the best solution would of course be an upstream fix. But I needed a
solution to this much quicker than that. I am not really expecting
Yocto to fix a libtool problem. I only wished to flag for the problem
and provide the patch if more people stumble into the same issue. And
sure, I can try to post this patch in a proper way. I will probably
mess it up, but there is a first time for everything ;) Is there some
document that describes the exact procedure for sending a patch for
review in Yocto? I guess you also wish to have some ticket id or
something to connect it to?
As it stands right now we have a .bbappend to workaround this so there
is really no panic.

Thanks.
Hans








> Cheers,
>
> Richard
>
>
>
>> But I am very surprised, to
>> say the least, that this problem has passed unnoticed!
>> The patch goes into meta/recipes-development/libtool/libtool. This
>> patch *must* be applied after Khems patch that renames --with-sysroot
>> to --with-libtool-sysroot (rename-with-sysroot.patch).
>> After applying the patch (and added it to libtool-2.4.2.inc) the
>> populated SDK toolchain works as expected also when
>> --with-libtool-sysroot is not provided, instead it is picked up from
>> $CC --print-sysroot. I have filed a bug report to bug-libtool since
>> the real problem is in libtool itself, not Yocto.
>
>
>