Jeremy Bierbach wrote: Hi Jeremy> It seems likely to me that you still have libshout 1.x installed.No, it's not that. # rpm -q libshout libshout-2.0-1.dag # rpm -q libshout-devel libshout-devel-2.0-1.dag It's the half-hard-coded shout/shout.h path in the source. Since libshout is installed by rpm in /usr/include, the path will never match. Even if "/usr/include/" would be prepended to the path, it would still result in /usr/include/shout/shout.h, which doesn't exist. Now, what I don't know is whether things would work out any better if the rpm put the header files in /usr/include/shout instead of in /usr/include. If so, then perhaps the libshout rpm should be adjusted. I'll try modifying the rpm, see what happens, and report tomorrow. Z
On Thu, 2004-11-18 at 00:42, Zenon Panoussis wrote:> Jeremy Bierbach wrote: > > Hi Jeremy > > > It seems likely to me that you still have libshout 1.x installed. > > No, it's not that. > > # rpm -q libshout > libshout-2.0-1.dag > # rpm -q libshout-devel > libshout-devel-2.0-1.dag > > It's the half-hard-coded shout/shout.h path in the source. Since > libshout is installed by rpm in /usr/include, the path will never > match. Even if "/usr/include/" would be prepended to the path, it > would still result in /usr/include/shout/shout.h, which doesn't > exist.certain directories are searched for include files, /usr/include is the default include location. libshout places its header in shout/shout.h so if the rpm is placing it incorrectly then the question is where did the rpm come from? karl.
Karl Heyes wrote:>> It's the half-hard-coded shout/shout.h path in the source. Since >> libshout is installed by rpm in /usr/include, the path will never >> match. Even if "/usr/include/" would be prepended to the path, it >> would still result in /usr/include/shout/shout.h, which doesn't >> exist.> certain directories are searched for include files, /usr/include is the > default include location. libshout places its header in shout/shout.h > so if the rpm is placing it incorrectly then the question is where did > the rpm come from?It came from http://dag.wieers.com/packages/libshout/ . I checked what's happening there and it's not the rpm's fault. It produces ./configure --build=i686-redhat-linux-gnu --host=i686-redhat-linux-gnu \ --target=i386-redhat-linux-gnu --program-prefix= --prefix=/usr \ --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc \ --datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib \ --libexecdir=/usr/libexec --localstatedir=/var --sharedstatedir=/usr/com \ --mandir=/usr/share/man --infodir=/usr/share/info and that in turn puts shout.h in /usr/include/ and not in /usr/include/shout/ . The problem is somewhere in the way libshout understands "--includedir=/usr/include" I haven't managed to figure that. Z