My guess is that these errors are mostly likely caused by the fact that Fedora puts the libmpeg3 headers in a different place:
pd@debian-stable-i386:~$ grep mpeg3_close /usr/include/*.h /usr/include/libmpeg3.h:int mpeg3_close(mpeg3_t *file);
root@fedora9-i386.idmi.poly.edu:~ > grep mpeg3_close /usr/include/*/*.h /usr/include/mpeg3/libmpeg3.h:int mpeg3_close(mpeg3_t *file);
Message: 5 Date: Thu, 4 Dec 2008 04:20:50 -0500 From: pd@fedora9-i386.idmi.poly.edu Subject: [PD-cvs] autobuild: pd-extended fedora9-i386 2008-12-04 04.09.13 To: pd-cvs@iem.at Message-ID: 200812040920.mB49KopS022041@fedora9-i386.idmi.poly.edu
filmMPEG3.cpp:53: error: 'mpeg_file' was not declared in this scope filmMPEG3.cpp:53: error: 'mpeg3_close' was not declared in this scope filmMPEG3.cpp:54: error: 'mpeg_file' was not declared in this scope filmMPEG3.cpp:63: error: 'mpeg3_check_sig' was not declared in this scope filmMPEG3.cpp:64: error: 'mpeg_file' was not declared in this scope filmMPEG3.cpp:64: error: 'mpeg3_open' was not declared in this scope filmMPEG3.cpp:65: error: 'mpeg3_has_video' was not declared in this scope filmMPEG3.cpp:69: error: 'mpeg3_total_vstreams' was not declared in this scope filmMPEG3.cpp:72: error: 'mpeg3_video_frames' was not declared in this scope filmMPEG3.cpp:73: error: 'mpeg3_frame_rate' was not declared in this scope filmMPEG3.cpp:75: error: 'mpeg3_video_width' was not declared in this scope filmMPEG3.cpp:76: error: 'mpeg3_video_height' was not declared in this scope filmMPEG3.cpp:118: error: 'mpeg_file' was not declared in this scope filmMPEG3.cpp:122: error: 'MPEG3_RGBA8888' was not declared in this scope filmMPEG3.cpp:123: error: 'mpeg3_read_frame' was not declared in this scope filmMPEG3.cpp:139: error: 'mpeg_file' was not declared in this scope filmMPEG3.cpp:139: error: 'mpeg3_read_yuvframe_ptr' was not declared in this scope filmMPEG3.cpp:157: error: 'mpeg_file' was not declared in this scope filmMPEG3.cpp:157: error: 'mpeg3_set_frame' was not declared in this scope rsync error: syntax or usage error (code 1) at main.c(1216) [receiver=3.0.4]
the full logfile - if it has been succesfully uploaded - can be viewed at: http://autobuild.puredata.info/auto-build/2008-12-04/logs/ 2008-12-04_04.09.13_linux_fedora9-i386_pd-extended_run-automated- builder.txt
Pd-cvs mailing list Pd-cvs@iem.at http://lists.puredata.info/listinfo/pd-cvs
End of Pd-cvs Digest, Vol 46, Issue 4
------------------------------------------------------------------------ ----
You can't steal a gift. Bird gave the world his music, and if you can hear it, you can have it. - Dizzy Gillespie
Hans-Christoph Steiner wrote:
My guess is that these errors are mostly likely caused by the fact that Fedora puts the libmpeg3 headers in a different place:
pd@debian-stable-i386:~$ grep mpeg3_close /usr/include/*.h /usr/include/libmpeg3.h:int mpeg3_close(mpeg3_t *file);
root@fedora9-i386.idmi.poly.edu:~ > grep mpeg3_close /usr/include/*/*.h /usr/include/mpeg3/libmpeg3.h:int mpeg3_close(mpeg3_t *file);
well, the joys of multiple distros...
i suggest that either the distro or the upstream maintainers create a pkg-config for libmpeg3. this would be used automatically by Gem's build system.
alternatively it should be possible to use: % PKG_MPEG3_CFLAGS="-I/usr/include/mpeg3" ./configure
to add specific cflags manually.
fgmadsr IOhannes
On Dec 5, 2008, at 7:58 AM, IOhannes m zmölnig wrote:
Hans-Christoph Steiner wrote:
My guess is that these errors are mostly likely caused by the fact that Fedora puts the libmpeg3 headers in a different place:
pd@debian-stable-i386:~$ grep mpeg3_close /usr/include/*.h /usr/include/libmpeg3.h:int mpeg3_close(mpeg3_t *file);
root@fedora9-i386.idmi.poly.edu:~ > grep mpeg3_close /usr/include/ */*.h /usr/include/mpeg3/libmpeg3.h:int mpeg3_close(mpeg3_t *file);
well, the joys of multiple distros...
i suggest that either the distro or the upstream maintainers create a pkg-config for libmpeg3. this would be used automatically by Gem's build system.
alternatively it should be possible to use: % PKG_MPEG3_CFLAGS="-I/usr/include/mpeg3" ./configure
to add specific cflags manually.
Such a suggestion sounds a like a good idea. I take your response to mean that you are not going to support Fedora as it is? That is a common arrangement for headers in Fedora, this is not the only package setup like that.
.hc
fgmadsr IOhannes
Pd-dev mailing list Pd-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
------------------------------------------------------------------------ ----
You can't steal a gift. Bird gave the world his music, and if you can hear it, you can have it. - Dizzy Gillespie
Hans-Christoph Steiner wrote:
well, the joys of multiple distros...
i suggest that either the distro or the upstream maintainers create a pkg-config for libmpeg3. this would be used automatically by Gem's build system.
alternatively it should be possible to use: % PKG_MPEG3_CFLAGS="-I/usr/include/mpeg3" ./configure
to add specific cflags manually.
Such a suggestion sounds a like a good idea. I take your response to mean that you are not going to support Fedora as it is? That is a common arrangement for headers in Fedora, this is not the only package setup like that.
i try to avoid supporting a distro as such. (but i am using debian as my ultimate standard :-))
if distros decides to put header files into different places, then - imho - distros are responsible to provide a mechanism to find the header.
i don't see so many solutions for this: - include whatever directories people ask me to include in the upstream code - try to figure-out which dirs to include by using some standardized mechanism - give the user the possibilty to add arbitrary dirs to the build-process - automatically include all directories in the system.
i hope to have implemented #2 (via pkg-config) and #3 (via configure-flags and/or environment variables). i don't want to do #1 ("hey my new distro installs all headers into /home/foo/bar/; please include this path") and i don't want to talk about #4 :-)
however, i think i probably should pay more attention to where the upstream libraries actually want their headers installed rather than taking debian as the reference system...
fgmasrd IOhannes
On Dec 7, 2008, at 12:02 PM, IOhannes m zmölnig wrote:
Hans-Christoph Steiner wrote:
well, the joys of multiple distros...
i suggest that either the distro or the upstream maintainers create a pkg-config for libmpeg3. this would be used automatically by Gem's build system.
alternatively it should be possible to use: % PKG_MPEG3_CFLAGS="-I/usr/include/mpeg3" ./configure
to add specific cflags manually.
Such a suggestion sounds a like a good idea. I take your response to mean that you are not going to support Fedora as it is? That is a common arrangement for headers in Fedora, this is not the only package setup like that.
i try to avoid supporting a distro as such. (but i am using debian as my ultimate standard :-))
if distros decides to put header files into different places, then - imho - distros are responsible to provide a mechanism to find the header.
i don't see so many solutions for this:
- include whatever directories people ask me to include in the
upstream code
- try to figure-out which dirs to include by using some standardized
mechanism
- give the user the possibilty to add arbitrary dirs to the build-
process
- automatically include all directories in the system.
i hope to have implemented #2 (via pkg-config) and #3 (via configure-flags and/or environment variables). i don't want to do #1 ("hey my new distro installs all headers into /home/foo/bar/; please include this path") and i don't want to talk about #4 :-)
however, i think i probably should pay more attention to where the upstream libraries actually want their headers installed rather than taking debian as the reference system...
There are lots of users of Fedora and lots of packages, so I am sure there is a way. Any Fedora users want to help out here?
.hc
fgmasrd IOhannes
------------------------------------------------------------------------ ----
Hans-Christoph Steiner wrote:
There are lots of users of Fedora and lots of packages, so I am sure there is a way. Any Fedora users want to help out here?
so after all my rants i finally found out that fedora did exactly as it should: while moving the headers around, they also provide a pkg-config for libmpeg3, enabling the adept programmer to find the headers...
unfortunately Gem's configure did check for "mpeg3" rather than "libmpeg3", so it didn't get this information.
i have (hopefully) fixed it now -- let's wait for tomorrows logs.
the fix's side-effect is, that the configure-flags for mpeg3 are now renamed to (e.g.) "--without-libmpeg3" (instead of "--without-mpeg3"
mfg.asdr IOhannes
On Dec 12, 2008, at 3:21 PM, IOhannes m zmölnig wrote:
IOhannes m zmoelnig wrote:
i have (hopefully) fixed it now -- let's wait for tomorrows logs.
argh! while my changes no make Gem find the correct headers, it's only to discover that they changed the API :-(
Everyone should just use Debian anyway ;)
.hc
mfdat IOhannes
------------------------------------------------------------------------ ----
Looking at things from a more basic level, you can come up with a more direct solution... It may sound small in theory, but it in practice, it can change entire economies. - Amy Smith
Hans-Christoph Steiner wrote:
On Dec 12, 2008, at 3:21 PM, IOhannes m zmölnig wrote:
IOhannes m zmoelnig wrote:
i have (hopefully) fixed it now -- let's wait for tomorrows logs.
argh! while my changes no make Gem find the correct headers, it's only to discover that they changed the API :-(
i noticed that "they" has changing meaning in my posts. the "they" that changed the API are heroinewarrior. fedora is innocent here.
Everyone should just use Debian anyway ;)
i wholeheartily agree.
fdmadr IOhannes
IOhannes m zmölnig wrote:
IOhannes m zmoelnig wrote:
i have (hopefully) fixed it now -- let's wait for tomorrows logs.
argh! while my changes no make Gem find the correct headers, it's only to discover that they changed the API :-(
so now we are getting close:
g++ -o Gem.pd_linux -shared -Wl,-export-dynamic ./Objects/*.o -ldv
-ljpeg -ltiff -lGLU -lGL -lXext -lXext -lX11 -ldl -lz -lm -lpthread -L/home/pd/auto-build/pd-extended/pd/bin -lGLU -lGL -lftgl -lfreetype -laviplay -lmpeg3 -lpthread -la52 -L/usr/lib -lquicktime -lpthread -lm -lz -ldl -lquicktime -lpthread -lm -lz -ldl -lMagick++ -lWand -lMagick
/usr/bin/ld: cannot find -la52
liba52 is pulled in via the pkg-config for libmpeg3.
so either someone has to manually install liba52 or please file a bug-report for fedora's pkg-config script as this has a dependeny not satisfied by the rpm-dependencies. (ah finally i'm back again to where i can lean back and say "it's all their fault")
gfmar IOhannes
-
Hans-Christoph Steiner -
IOhannes m zmoelnig -
IOhannes m zmölnig