Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Open bug analysis
Date: Mon, 17 Feb 2014 18:46:48 +0100	[thread overview]
Message-ID: <53024B08.1040709@mind.be> (raw)
In-Reply-To: <CAAXf6LVJwg4Xcjg1rMZvfgC8xi-9TJrV7faUknff630duLG_AQ@mail.gmail.com>

On 14/02/14 21:39, Thomas De Schampheleire wrote:
> Hi Thomas,
> 
> Thanks for your feedback...
> 
> On Thu, Feb 13, 2014 at 7:52 PM, Thomas Petazzoni
> <thomas.petazzoni@free-electrons.com> wrote:
>> > Dear Thomas De Schampheleire,
>> >
>> > On Thu, 13 Feb 2014 16:30:37 +0100, Thomas De Schampheleire wrote:
>> >
>>> >> Doing a Buildroot build from /usr doesn't work
>>> >> https://bugs.busybox.net/show_bug.cgi?id=5750
>>> >> ThomasP, you are assigned to this bug. Have you done an analysis about
>>> >> this in the past? What are the reasons for these problems?
>> >
>> > The main problem I had identified was our logic to fixup the .la files.
>> > To fix it, I had written:
>> >
>> > -               $$(SED) "s:\(['= ]\)/usr:\\1$(STAGING_DIR)/usr:g" $$$$i; \
>> > +               $$(SED) "\:['= ]$(STAGING_DIR)/usr:!s:\(['= ]\)/usr:\\1$(STAGING_DIR)/usr:g" $$$$i; \
>> >
>> > but I believe it still wasn't working properly, because the staging
>> > directory was being re-prefixed everytime this was executed on all .la
>> > files. But I may not necessarily remember all the details.
> I am trying to reproduce and fix this.
> As mentioned on IRC, I'm currently using a slightly modified version
> of the above .la fixing:
> 
> -               $$(SED) "s:\(['= ]\)/usr:\\1$(STAGING_DIR)/usr:g" $$$$i; \
> +               $$(SED) "s:\(['=
> ]\)/usr/lib:\\1$(STAGING_DIR)/usr/lib:g" $$$$i; \
> +               $$(SED) "s:\(['=
> ]\)/usr/local/lib:\\1$(STAGING_DIR)/usr/local/lib:g" $$$$i; \
> 
> I.e. instead of searching for /usr/something, only search for /usr/lib
> as this is where all .la files are put.
> I actually don't think we need the /usr/local/lib line.

 Just brainstorming here, but I think a more complete solution could be
something like:

$$(SED) -e "s:\(['= ]\)$(STAGING_DIR):\\1 at STAGING_DIR@:g" \
        -e "s:\(['= ]\)/usr:\\1$(STAGING_DIR)/usr:g" \
        -e "s:@STAGING_DIR@:$(STAGING_DIR):g" \
        $$$$i;



 Regards,
 Arnout

-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2014-02-17 17:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-13 15:30 [Buildroot] Open bug analysis Thomas De Schampheleire
2014-02-13 18:52 ` Thomas Petazzoni
2014-02-14 20:39   ` Thomas De Schampheleire
2014-02-17 17:46     ` Arnout Vandecappelle [this message]
2014-02-19 16:02       ` Thomas De Schampheleire
2014-02-19 21:16         ` Arnout Vandecappelle
2014-02-17 17:36   ` Arnout Vandecappelle

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53024B08.1040709@mind.be \
    --to=arnout@mind.be \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox