[Buildroot] Libtool problem building mesa3d-demos

[Arnout Vandecappelle <arnout@mind.be>]

On 02/05/15 23:16, Carlos Soto wrote:
> 
> 
> 2015-05-02 22:45 GMT+02:00 Arnout Vandecappelle <arnout@mind.be
> <mailto:arnout@mind.be>>:
> 
>     On 02/05/15 22:42, Carlos Soto wrote:
>     >
>     >      Since this xtools thing is not passed on the command line, it must be in your
>     >     environment. Can you do 'env | grep xtools'?
>     >
>     >      Regards,
>     >      Arnout
>     >
>     > No, it's not in my environment. As far as I can tell, libtool seems to be
>     > joining together my toolchain path
>     > (usr/local/xtools//arm-cortexa9_neon-linux-gnueabihf) and the buildroot staging
>     > sysroot path (
>     > /home/starsl/iMX6/buildroot/output/host/usr/lib)
> 
>      OK, so then there must be some .la file which has something funny. Can you grep
>     for xtools in all the .la files in output/ ?
> 
>      Regards,
>      Arnout
> 
> 
> Done. Yes, there is something funny in some .la files.
> I've found this line
> libdir='/usr/local/xtools/arm-cortexa9_neon-linux-gnueabihf/arm-cortexa9_neon-linux-gnueabihf/lib'
> in some .la files in /host/usr/arm-buildroot-linux-gnueabihf/sysroot/lib, but
> that's expected because these are copied from my external toolchain.
> 
> The awful one is libGLU.la, which contains the strange search path for
> libstdc++.la in 'dependency_libs'
> There are 4 libGLU.la in my output directory, and 3 of them have a valid path
> ./build/libglu-9.0.0/libGLU.la
> ./build/libglu-9.0.0/.libs/libGLU.la
> ./target/usr/lib/libGLU.la
> 
> But this one
> ./host/usr/arm-buildroot-linux-gnueabihf/sysroot/usr/lib/libGLU.la
> has the wrong path:

 Right, I had a feeling that that was going to be the issue...

 In pkg-autotools, there is a fixup of the .la files which is done in
_INSTALL_STAGING_CMDS. There's a big explanation above it why it is needed. It
basically assumes that any occurrence of /usr means it's something that points
to the host environment while it shouldn't, so $(STAGING_DIR) is prepended to
it. The logic takes into account that $(STAGING_DIR) and $(BASE_DIR) could be
under /usr as well, so these are handled. But it doesn't take into account that
$(TOOLCHAIN_EXTERNAL_INSTALL_DIR) could be in /usr (most people put it in /opt).

 I'll see if I can come up with a patch...

 Regards,
 Arnout

[snip]


-- 
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