dongoodman
2001-Jan-22 15:02 UTC
[vorbis] several (different and seperate) compiling problems
I thought I had seen something about this earlier, but a search through the archives revealed nothing... first problem: Under Windows ME, using VC++6 (sp4), VC does not recognize the project files in the beta3 source tarball as being valid project files. it complains that they were not generated by VC++6, and would I like to create a wrapper for these makefiles? It doesn't work. I checked them out manually, and they appear fine...I wonder if its not because of service pack 4? i have no clue at all... econd problem: installing and compiling beta3 ogg and vorbis source RPMS: ogg goes ok...only after its compiled, and I've generated an RPM, it doesn't install the header files in /usr/include/ogg...it doesn't, in fact install them anywhere. minor problem, easily corrected by hand for now. but the real hum-dinger is when i try to configure vorbis, from the source RPM's or from the tarball...it complains that ogg has not been installed! error: -logg is an invalid library (on test compiles). however, /usr/lib/libogg.so.0 (or whatever the shared library is called, can't remember off the top of my head) is very much there...is it expecting libogg.a? argh! vorbis-tools give the same error. arghle. have fun dongoodman %--------------------------------------------deg3@ra.msstate.edu| |bleu| |`I invented the term 'object oriented', pobox 2516| |----| |and I can tell you mississippi state ms| | () | /. |I did not have C++ in mind.' 39762| | /\ | |Alan Kay-------------------------------------------------------% Hi, I'm a .sig Virus, put me in yours :-) --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to 'vorbis-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
Jack Moffitt
2001-Jan-22 15:09 UTC
[vorbis] several (different and seperate) compiling problems
> first problem: > Under Windows ME, using VC++6 (sp4), VC does not recognize the project > files in the beta3 source tarball as being valid project files. it complains > that they were not generated by VC++6, and would I like to create a wrapper > for these makefiles? It doesn't work. I checked them out manually, and > they appear fine...I wonder if its not because of service pack 4? i have > no clue at all...I built everything for beta3 with VC++6sp4 on Win98SE. Dunno why they were bad but maybe it's an issue of line separators.> second problem: > installing and compiling beta3 ogg and vorbis source RPMS: > ogg goes ok...only after its compiled, and I've generated an RPM, it > doesn't install the header files in /usr/include/ogg...it doesn't, in fact > install them anywhere. minor problem, easily corrected by hand for now. > but the real hum-dinger is when i try to configure vorbis, from > the source RPM's or from the tarball...it complains that ogg has not > been installed! error: -logg is an invalid library (on test compiles). > however, /usr/lib/libogg.so.0 (or whatever the shared library is called, > can't remember off the top of my head) is very much there...is it expecting > libogg.a? argh! vorbis-tools give the same error.I doubt I would have missed the ogg includes, but I'll check. As for not finding libogg, did you run ldconfig? jack. --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to 'vorbis-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
Michael Smith
2001-Jan-22 16:12 UTC
[vorbis] several (different and seperate) compiling problems
dongoodman wrote:> > I thought I had seen something about this earlier, but a search through > the archives revealed nothing... > > first problem: > Under Windows ME, using VC++6 (sp4), VC does not recognize the project > files in the beta3 source tarball as being valid project files. it complains > that they were not generated by VC++6, and would I like to create a wrapper > for these makefiles? It doesn't work. I checked them out manually, and > they appear fine...I wonder if its not because of service pack 4? i have > no clue at all...VC project files MUST have dos-style line-end mangling. If you check something out from a different system (e.g. a unix system), they'll definately not have these (I guess the project files should really be tagged as binary so that cvs doesn't do this). If you check them out from windows, anything could happen. Try converting them to dos-style line endings, see if that helps. Michael --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to 'vorbis-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
Ingo Saitz
2001-Jan-23 05:09 UTC
[vorbis] several (different and seperate) compiling problems
On Mon, Jan 22, 2001 at 05:02:45PM -0600, dongoodman wrote:> ogg goes ok...only after its compiled, and I've generated an RPM, it > doesn't install the header files in /usr/include/ogg...[...]> ...it [libvorbis] complains that ogg has not > been installed! error: -logg is an invalid library (on test compiles). > however, /usr/lib/libogg.so.0 (or whatever the shared library is called,Did you install the generated libogg-devel rpm, too? According to the .sec file, this rpm contains the needed includes and the file libogg.so (symlink to libogg.so.0.0.0). That file is needed to link binaries against the shared library. Ingo -- 16 Hard coded constant for amount of room allowed for cache align and faster forwarding (tunable) -- seen in /usr/src/linux-2.2.14/net/TUNABLE --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to 'vorbis-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.