After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 141113 - xvidcore in custom dir not detected by configure
xvidcore in custom dir not detected by configure
Status: RESOLVED NOTGNOME
Product: GStreamer
Classification: Platform
Component: gst-plugins
0.8.1
Other Linux
: Normal normal
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-04-26 04:10 UTC by DJ
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description DJ 2004-04-26 04:10:33 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.
Comment 1 Ronald Bultje 2004-04-26 14:48:38 UTC
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.
Comment 2 DJ 2004-04-27 05:18:46 UTC
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"?
Comment 3 Ronald Bultje 2004-04-27 16:44:59 UTC
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.
Comment 4 Ronald Bultje 2004-04-28 23:33:47 UTC
I checked, it's $LIBS, not $LDFLAGS. Please retry with that.
Comment 5 DJ 2004-04-29 05:57:52 UTC
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?
Comment 6 Ronald Bultje 2004-04-29 12:09:33 UTC
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.
Comment 7 DJ 2004-04-29 22:41:04 UTC
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.
Comment 8 Ronald Bultje 2004-04-30 00:46:15 UTC
I'll close this here then, it's not really a GStreamer bug... :).