[Buildroot] Issue with toolchain wrapper changes

[Arnout Vandecappelle <arnout@mind.be>]

On 17-02-16 18:23, Thomas De Schampheleire wrote:
> 
> On Feb 17, 2016 13:00, "Thomas Petazzoni" <thomas.petazzoni@free-electrons.com
> <mailto:thomas.petazzoni@free-electrons.com>> wrote:
>>
>> Hello,
>>
>> On Wed, 17 Feb 2016 12:04:30 +0100, Peter Korsgaard wrote:
>> > >>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com
> <mailto:thomas.petazzoni@free-electrons.com>> writes:
>> >
>> >  > Hello Arnout,
>> >  > I am facing some issues with the toolchain wrapper, which I believe
>> >  > were introduced by the changes done to use the toolchain wrapper also
>> >  > for the internal toolchain backend.
>> >
>> >  > As you know, Buildroot installs all its host stuff in $(HOST_DIR)/usr,
>> >  > and not directly under $(HOST_DIR). For the autobuilders, I build a
>> >  > number of toolchains with Buildroot, which are then used as pre-built
>> >  > external toolchains by the autobuilders. In order for those toolchains
>> >  > to look like conventional toolchains, at the end of their build, I do:
>> >
>> >  >    mv /path/to/host/usr/* /path/to/host/
>> >  >    rmdir /path/to/host/usr/
>> >
>> >  > Which moves everything outside of the usr/ subdirectory, and removes
>> >  > the usr/ subdirectory itself. This used to work perfectly fine, but
>> >  > now, it fails to find the .br_real equivalent of the command being
>> >  > executed. Example:
>> >
>> > Is the extra /usr really such a problem? I've built a bunch of
>> > toolchains, and just refer to them as /opt/br/<whatever>/usr.
>>
>> Yes, for my purpose it's annoying. I want to produce pre-built
>> toolchains that everyone can use, in Buildroot or something else, so I
>> want them to look like normal toolchains. And normal toolchains don't
>> have this useless usr/ top-level directory.
> 
> I may be misunderstanding something, but what is the problem with creating the
> archive from the usr directory? This is what I did at the time I was using a
> buildroot toolchain.

 It works fine when you use it as an external toolchain in buildroot, but it
doesn't work when you try to call cross-gcc directly. The wrapper will look for
the real executable in ../../usr/bin.

 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:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF