All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens <irimi@gmx.de>
To: buildroot@busybox.net
Subject: [Buildroot] toolchain problem:wrong path in libSDL.la
Date: Tue, 19 Jan 2010 17:32:47 +0100	[thread overview]
Message-ID: <4B55DEAF.40808@gmx.de> (raw)

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

             reply	other threads:[~2010-01-19 16:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-19 16:32 Jens [this message]
2010-01-19 18:53 ` [Buildroot] toolchain problem:wrong path in libSDL.la Julien Boibessot
2010-01-19 22:35   ` Jens
2010-01-27 14:43     ` Julien Boibessot

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=4B55DEAF.40808@gmx.de \
    --to=irimi@gmx.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.