From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 381] New: libtheora not using sdl-prefix
Date: Tue, 9 Jun 2009 06:07:44 +0000 (UTC) [thread overview]
Message-ID: <bug-381-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=381
Host: linux
Target: mipsel-linux
Summary: libtheora not using sdl-prefix
Product: buildroot
Version: unspecified
Platform: Other
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: evan.zelkowitz at gmail.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
It seems that the libtheora build ends up linking against the local libc and/or
using the local SDL install when building along side SDL in buildroot. I
noticed during the configure it was linking against my local SDL libraries and
using my local sdl-config. I had to add --with-sdl-prefix=$(STAGING_DIR)/usr
to the libtheora.mk and then it appeared to use the correct sdl directory.
This had caused issues for me since the rest of sdl would then attempt to use
libc.so.6 when being linked by other apps and those apps would not run on the
uclibc system since libc.so.6 did not exist.
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2009-06-09 6:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 6:07 bugzilla at busybox.net [this message]
2009-07-19 20:42 ` [Buildroot] [Bug 381] libtheora not using sdl-prefix bugzilla at busybox.net
2009-07-19 21:17 ` bugzilla at busybox.net
2009-07-20 5:57 ` bugzilla at busybox.net
2009-08-31 8:00 ` bugzilla at busybox.net
2009-09-02 1:24 ` bugzilla at busybox.net
2009-09-02 5:59 ` bugzilla at busybox.net
2009-09-02 6:02 ` bugzilla at busybox.net
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=bug-381-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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