On Fri, Sep 6, 2013 at 11:53 AM, Richard Purdie <richard.pur...@linuxfoundation.org> wrote: > On Fri, 2013-09-06 at 10:59 +0200, Hans Beckérus wrote: >> On Fri, Sep 6, 2013 at 10:25 AM, Richard Purdie >> <richard.pur...@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. > > It wasn't harsh, I just want to make sure you know you're not being > ignored, fixes for issues like this are much appreciated and key to > improving the project. Equally, there aren't enough hours in the day for > us to do everything, we try our best! :) > >> As I said, this is really a bug in libtool so >> the best solution would of course be an upstream fix. > > Agreed, however I know first hand how hard it is to get fixes into > libtool. So we're prepared to put this one with the other libtool fixes > we have. > >> 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 ;) > > Indeed, the first time you do this its quite daunting but equally, we'll > do our best to help you through it and its not actually so bad. I'm > suggesting you do go through the process since if you then later have > other changes, you'll be more likely to submit them too and I would > encourage people to do that. > >> Is there some >> document that describes the exact procedure for sending a patch for >> review in Yocto? > > http://www.yoctoproject.org/docs/1.5/dev-manual/dev-manual.html#how-to-submit-a-change > > Don't worry about maintainers and so on for this one, just send it to > the OE-Core list. > >> I guess you also wish to have some ticket id or >> something to connect it to? > > Its not essential in a case like this where the issue is now well > understood. > >> As it stands right now we have a .bbappend to workaround this so there >> is really no panic. > > If its going to be in the release which I'd like it to be, I could do > with it sooner than later though. If you don't have the time, fair > enough but it does seem like a good fix. >
Ok, I will see what I can do. I guess ch3.9+ch3.9.2 is what I need to walk through. > Cheers, > > Richard > > > _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto