On Wed, Nov 15, 2000 at 04:15:15PM +0100, Bernhard Rosenkraenzer wrote:
> On Wed, 15 Nov 2000, Thomas Ribbrock wrote:
>
> That's why they're using -I/usr/include/kde in the CFLAGS.
"they" as in the RPMs in question, I presume? Ok, makes sense.
Hm, is there actually an equivalent to ldconfig for header files?
> /usr/include/kde *is* one of the standard locations that gets searched
> because it's the FHS compliant location.
Ok, in that case it looks like I need someone to give me a slow motion
explanation of the FHS... ... I can only find
/usr/include/X11
bsd
g++
asm
linux
in there (interesting that sys isn't mentioned).
/opt/<package>/include seems to be FHS 2.1 compliant, too, btw... ;-)
(interesting bit about /etc/opt/<package>, though - hadn't seen that
before)
In case anybody else is interested in having a read:
http://www.pathname.com/fhs/
> $KDEDIR/include/kde won't work unless $KDEDIR == /usr.
>
> What you can do is add --with-kde-includes=$KDEDIR/include/kde to the
> configure parameters; most KDE applications will know what to do with
> that.
Yep, that's what I figured. Kind of annoying, though: More work... :-)
But as I said: In my case I'll go for a rebuild anyway, so I'll get
everything where I want it to be... ;-)
Thanks,
Thomas
--
"Look, Ma, no obsolete quotes and plain text only!"
Thomas Ribbrock | http://www.bigfoot.com/~kaytan | ICQ#: 15839919
"You have to live on the edge of reality - to make your dreams come true!"
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
