[Buildroot] toolchain problem:wrong path in libSDL.la

[Buildroot] toolchain problem:wrong path in libSDL.la

[Jens]

Hi,

I'm using recent version 2009.11 and I've added SDL package to my 
configuration.

My br installation is at /mnt/ext3data/buildroot/

but br creates a wrong path of libdir in libSDL.la
(/mnt/ext3data/buildroot/output/build/SDL-1.2.14/build/libSDL.la
resp. /mnt/ext3data/buildroot/output/build/staging_dir/usr/lib/libSDL.la):
--- cut ---
# Libraries that this one depends upon.
dependency_libs=' 
-L/mnt/ext3data/buildroot/output/build/staging_dir/usr/lib 
/mnt/ext3data/buildroot/output/build/staging_dir/usr/lib/libiconv.la 
-L/mnt/ext3data/buildroot/output/build/staging_dir/lib -lm 
/mnt/ext3data/buildroot/output/build/staging_dir/usr/lib/libts.la -ldl 
-lpthread'
# Directory that this library needs to be installed in:
libdir='/mnt/ext3data/buildroot/output/build/staging_dir/usr/mnt/ext3data/buildroot/output/build/staging_dir/usr/lib'
--- cut ---

Of course the correct path at my machine is 
'/mnt/ext3data/buildroot/output/build/staging_dir/usr/lib'
That makes it impossible to link applications that require the SDL lib, 
it leads to an linker error:  i.e. 'could not find SDL lib'

I checked older br versions , but same problem. Also an update (I 
switched to newer versions in br scripts) of SDL lib didn't help it nor 
update of libtool (as far as I understood that creates the *.la files !?).

BR,
Jens

[Buildroot] toolchain problem:wrong path in libSDL.la

[Julien Boibessot]

Hi Jens,

Jens a ?crit :
> I'm using recent version 2009.11 and I've added SDL package to my
> configuration.
>
> My br installation is at /mnt/ext3data/buildroot/
>
> but br creates a wrong path of libdir in libSDL.la
please find attached here a patch that can probably solve your problem.
Sorry but I didn't take time yet to submit it to BR team.
http://armadeus.git.sourceforge.net/git/gitweb.cgi?p=armadeus/armadeus;a=blob;f=patches/buildroot/078-sdl-correct_libdir_path_in_libSDL.la.patch;h=c455834241d222b72865032c333c83630bd571b0;hb=HEAD

Hope it will help you...

Regards,
Julien

[Buildroot] toolchain problem:wrong path in libSDL.la

[Jens]

Hi Julien,

Thank you very much! Yes in staging_dir libdir of libSDL.a has fixed now.
But your patch is just a workaround because in build dir of SDL the path 
will be still wrong.

Could not find it as known bug in recent buglist, hence I supposed to 
write a new bug report, but I still don't have an account.

BR,
Jens

Julien Boibessot wrote:
> Hi Jens,
>
> Jens a ?crit :
>   
>> I'm using recent version 2009.11 and I've added SDL package to my
>> configuration.
>>
>> My br installation is at /mnt/ext3data/buildroot/
>>
>> but br creates a wrong path of libdir in libSDL.la
>>     
> please find attached here a patch that can probably solve your problem.
> Sorry but I didn't take time yet to submit it to BR team.
> http://armadeus.git.sourceforge.net/git/gitweb.cgi?p=armadeus/armadeus;a=blob;f=patches/buildroot/078-sdl-correct_libdir_path_in_libSDL.la.patch;h=c455834241d222b72865032c333c83630bd571b0;hb=HEAD
>
> Hope it will help you...
>
> Regards,
> Julien
>
>   

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20100119/d14a3ecf/attachment-0001.htm>

[Buildroot] toolchain problem:wrong path in libSDL.la

[Julien Boibessot]

Hi Jens,

Jens a ?crit :
> Hi Julien,
>
> Thank you very much! Yes in staging_dir libdir of libSDL.a has fixed now.
> But your patch is just a workaround because in build dir of SDL the
> path will be still wrong.
and why do you need libSDL.la from SDL build dir ?
Shouldn't you use staging_dir content to link your application against
SDL (or other .so) ?
>
> Could not find it as known bug in recent buglist, hence I supposed to
> write a new bug report, but I still don't have an account.
If think it's an SDL cross-compiling problem (libtool?). When
configuring SDL with --prefix="/usr" I think you will have a correct
libdir in libSDL.la, but in that case SDL would try to install itself in
/usr/ of your host.

So I will propose my workaround unless someone has a better idea...

Regards,
Julien