GNOME Bugzilla – Bug 141113
xvidcore in custom dir not detected by configure
Last modified: 2004-12-22 21:47:04 UTC
Install xvidcore to a custom directory, configure gst-plugins, watch xvidcore detection fail. Since xvidcore does not come with a .pc file, installing xvidcore to a different prefix (not /usr, not /usr/local) causes configure to fail. Moving the xvidcore related files to a standard location temporarily fixes this. The configure script does not have any option to specify a custom prefix should xvidcore be installed to a different directory.
So, shouldn't the xvid team provide a .pc file? :). You can set environment variables such as LD_LIBRARY_PATH, CFLAGS and LDFLAGS to their corresponding dirs (colon-separated if you need multiple) to fix this. The correct fix is to install standard xvidcore packages in standard system locations, or for the xvid team to provide a .pc file.
Hrm... if I remember correctly, I did try the CFLAGS and LDFLAGS variables... it saw one thing (the header file detection I believe) but flunked the rest. Not sure as to why even tho I've set the vars correctly. As far as I know, I only set one dir each for CFLAGS and LDFLAGS. LD_LIBRARY_PATH wasn't much of an issue as I've gotten those custom dirs listed in the ld.so.conf file and have ran ldconfig many times prior to encountering this. I'd let the xvid team know... but other than a mailing list, is there any way to actually submit something to let the developers know of a "feature request"?
They have a forum where the developers occassionaly hang out. You could try there. Maybe LDFLAGS is not right and you need to set LIBS or something else. I must admit that I'm not much of a configure guru. I'll check out acgeneral.m4 tonight, maybe it has some hints on this.
I checked, it's $LIBS, not $LDFLAGS. Please retry with that.
well, went back to the tarball to do a quick configure of this... here's the command used: CFLAGS="-I/opt/apps/include" LIBS="-L/opt/apps/lib" ./configure --prefix=/opt/gnome --with-gnu-ld [... plus various disable options ...] I mean, this is supposedly correct, right? xvidcore custom-installed into /opt/apps prefix Here's the xvid portion of the configure script: checking xvid.h usability... yes checking xvid.h presence... no configure: WARNING: xvid.h: accepted by the compiler, rejected by the preprocessor! configure: WARNING: xvid.h: proceeding with the preprocessor's result configure: WARNING: ## ------------------------------------ ## configure: WARNING: ## Report this to bug-autoconf@gnu.org. ## configure: WARNING: ## ------------------------------------ ## checking for xvid.h... no configure: *** These plugins will not be built: xvid ----- Perhaps I've missed something?
What does config.log say? Maybe the pre-processor wants you to set $CPPFLAGS instead of $CLFAGS. And yes, I know this is sort of annoying... ./configure isn't always your best friend in such cases.
Used CPPFLAGS and LDFLAGS with configure. It now detects the header file and libraries repsectively. Going to post on xvid forum requesting a pc file addition.
I'll close this here then, it's not really a GStreamer bug... :).