Bug 381

Summary:	libtheora not using sdl-prefix
Product:	buildroot	Reporter:	Evan Zelkowitz <evan.zelkowitz>
Component:	Other	Assignee:	unassigned
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	buildroot
Priority:	P5
Version:	unspecified
Target Milestone:	---
Hardware:	Other
OS:	Linux
Host:	linux	Target:	mipsel-linux
Build:

Description Evan Zelkowitz 2009-06-09 06:07:42 UTC

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.

Comment 1 Peter Korsgaard 2009-07-19 20:42:01 UTC

Hmm, I cannot reproduce this. Can you provide some more details please? I take it that you are building for the same target as your build host, and that the libtheora build picks up your /usr/bin/sdl-config and ends up using your host libraries.

I've tried doing a x86-64 build (as that's what my build host is) with and without SDL enabled. The libtheora configure script does pick up my host sdl-config, but as it is only used for examples and we build with --disable-examples it has no effect. I also tried with a i686 build with the same affect.

Now, adding a --with-sdl-prefix doesn't hurt, but I would like to understand the problem first.

Comment 2 Evan Zelkowitz 2009-07-19 21:17:19 UTC

I will try to reproduce again.  I was building for mipsel on an x86 box and it ended up linking against the sdl in the box's local /usr/lib instead of the one in the buildroot directory, thats why I added the sdl-prefix so it would look at the buildroot one.  Since I was building for mipsel it was pretty apparent when things werent built correctly since they would fail on linking.  Since you were doing an x86 toolchain on an x86 box that may be why you couldnt see it.

Comment 3 Peter Korsgaard 2009-07-20 05:57:07 UTC

I also cannot reproduce it in mipsel either. The reason why I tries x86 was that this is normally the situation where packages gets confused and link with system libs.

Comment 4 Peter Korsgaard 2009-08-31 08:00:10 UTC

(In reply to comment #3)
> I also cannot reproduce it in mipsel either. The reason why I tries x86 was
> that this is normally the situation where packages gets confused and link with
> system libs.

Have you been able to reproduce this?

Comment 5 Evan Zelkowitz 2009-09-02 01:24:21 UTC

I have not been able to reproduce since either

Comment 6 Peter Korsgaard 2009-09-02 05:59:44 UTC

Ok, then I suggest we close the issue then. Feel free to reopen if you experience it again.

Comment 7 Evan Zelkowitz 2009-09-02 06:02:54 UTC

sounds good