gcc and include dirs -> do we need a /etc/includes.conf?

gcc and include dirs -> do we need a /etc/includes.conf?

[Gerold J. Wucherpfennig]

I've installed many packages into /opt to
get rid of "put everything into /usr/bin".

Now my CFLAGS and CXXFLAGS lines are _really_ long,
because I have to include the include dir of each /opt dir.
( -I/opt/package/include ...)

Is there any chance to get a "includes.conf" file in /etc ?
This should be a kind of ld.so.conf and list all include directories
which gcc should include at compile time.

Maybe a /etc/includes.conf can even let some distributors put some things
out of /usr/bin...  that would be _really_ good :-)


Please CC me

Gerold

Re: gcc and include dirs -> do we need a /etc/includes.conf?

[Michael S. Zick]

On Friday 28 February 2003 01:19 am, Gerold J. Wucherpfennig wrote:
> I've installed many packages into /opt to
> get rid of "put everything into /usr/bin".
>
> Now my CFLAGS and CXXFLAGS lines are _really_ long,
> because I have to include the include dir of each /opt dir.
> ( -I/opt/package/include ...)
>
> Is there any chance to get a "includes.conf" file in /etc ?
> This should be a kind of ld.so.conf and list all include directories
> which gcc should include at compile time.
>
> Maybe a /etc/includes.conf can even let some distributors put some things
> out of /usr/bin...  that would be _really_ good :-)
>
>
> Please CC me
>
> Gerold
Try it this way (If ASCII art still works)

/opt/<product><release>/{bin, lib, include, man, infc, ...}
 - - - -
/opt/<product><release>/{bin, lib, include, man, info, ...}

For every product-release your have. (Which I understand is what you
have already done.)

Then "fake" a unified installation with:

/opt/bin {ln -s /opt/<product><release>/bin/* . } (The period counts)
/opt/lib {ln -s /opt/<product><release>/lib/* . } (The period counts)
/opt/include {ln -s /opt/<product><release>/include/* . } (The period counts)
/opt/man {ln -s /opt/<product><release>/man/* . } (The period counts)

Then to get the new stuff first in path: export PATH=/opt/bin:$PATH

Tell ld.so about them, by putting "/opt/lib" in ld.so.conf and running
ldconfig.  Which leaves the ld.so cache pointing into /opt/lib/<library>
which is really a link to the actual product's location - but I expect that
it will work.

I am not sure if everything in the world will follow the /opt/include/*=>link
but I do expect some version of this scheme to work.

If I run into problems with this scheme (I am building a personal distro),
I'll post a follow-up -- so consider this an untested suggestion.

Mike

Mike

Re: gcc and include dirs -> do we need a /etc/includes.conf?

[Gerold J. Wucherpfennig]

On Friday February 28 2003 08:19, I wrote:
> I've installed many packages into /opt to
> get rid of "put everything into /usr/bin".
>
> Now my CFLAGS and CXXFLAGS lines are _really_ long,
> because I have to include the include dir of each /opt dir.
> ( -I/opt/package/include ...)
>
> Is there any chance to get a "includes.conf" file in /etc ?
> This should be a kind of ld.so.conf and list all include directories
> which gcc should include at compile time.

Alternatively there could be a special envionment variable "INCLUDE_PATH" - a 
kind of LD_LIBRARY_PATH ...


Please CC me

Gerold

Re: gcc and include dirs -> do we need a /etc/includes.conf?

[Daniel Jacobowitz]

On Fri, Feb 28, 2003 at 04:32:12PM +0100, Gerold J. Wucherpfennig wrote:
> On Friday February 28 2003 08:19, I wrote:
> > I've installed many packages into /opt to
> > get rid of "put everything into /usr/bin".
> >
> > Now my CFLAGS and CXXFLAGS lines are _really_ long,
> > because I have to include the include dir of each /opt dir.
> > ( -I/opt/package/include ...)
> >
> > Is there any chance to get a "includes.conf" file in /etc ?
> > This should be a kind of ld.so.conf and list all include directories
> > which gcc should include at compile time.
> 
> Alternatively there could be a special envionment variable "INCLUDE_PATH" - a 
> kind of LD_LIBRARY_PATH ...

Try C_INCLUDE_PATH.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer

Re: gcc and include dirs -> do we need a /etc/includes.conf?

[Gerold J. Wucherpfennig]

> symlinks...

Oh, this is really heavy :-)
so many symlinks...


My current solution to this issue is to use
a custom shell script which is in /etc/profile.d :

PATH="$PATH:/usr/local/bin";
for i in /opt/*/bin /opt/*/sbin
do
	PATH="$PATH:$i"
done

CPPFLAGS="-I/usr/X11R6/include"
for i in /opt/*/include
do
  CPPFLAGS="$CPPFLAGS -I$i"
done

LD_LIBRARY_PATH="/usr/local/lib:/usr/X11R6/lib"
for i in /opt/*/lib
do
  LD_LIBRARY_PATH="$LD_LIBRARY_PATH:$i"
done

CFLAGS="$CPPFLAGS -mcpu=athlon -O2"
CXXFLAGS="$CFLAGS"

export PATH CPPFLAGS CFLAGS CXXFLAGS




On Friday February 28 2003 15:20, you wrote:
> On Friday 28 February 2003 01:19 am, Gerold J. Wucherpfennig wrote:
...
>
> Try it this way (If ASCII art still works)
>
> /opt/<product><release>/{bin, lib, include, man, infc, ...}
>  - - - -
> /opt/<product><release>/{bin, lib, include, man, info, ...}
>
> For every product-release your have. (Which I understand is what you
> have already done.)
>
> Then "fake" a unified installation with:
>
> /opt/bin {ln -s /opt/<product><release>/bin/* . } (The period counts)
> /opt/lib {ln -s /opt/<product><release>/lib/* . } (The period counts)
> /opt/include {ln -s /opt/<product><release>/include/* . } (The period
> counts) /opt/man {ln -s /opt/<product><release>/man/* . } (The period
> counts)
>
> Then to get the new stuff first in path: export PATH=/opt/bin:$PATH
>
> Tell ld.so about them, by putting "/opt/lib" in ld.so.conf and running
> ldconfig.  Which leaves the ld.so cache pointing into /opt/lib/<library>
> which is really a link to the actual product's location - but I expect that
> it will work.
>
> I am not sure if everything in the world will follow the
> /opt/include/*=>link but I do expect some version of this scheme to work.
>
> If I run into problems with this scheme (I am building a personal distro),
> I'll post a follow-up -- so consider this an untested suggestion.
>
> Mike
>
> Mike

Re: gcc and include dirs -> do we need a /etc/includes.conf?

[Michael S. Zick]

On Friday 28 February 2003 09:43 am, Gerold J. Wucherpfennig wrote:
> > symlinks...
>
> Oh, this is really heavy :-)
> so many symlinks...
>
I didn't say elegant...
I didn't say efficient...
I did say "should work"
>
> My current solution to this issue is to use
> a custom shell script which is in /etc/profile.d :
>
> PATH="$PATH:/usr/local/bin";
> for i in /opt/*/bin /opt/*/sbin
> do
> 	PATH="$PATH:$i"
> done
>
For small projects, that should never exceed 
the line length limits.

Better yet - use the option Daniel posted for gcc.
And separate solutions for everything else.

Mike

Re: gcc and include dirs -> do we need a /etc/includes.conf?

[Mike Stump]

On Thursday, February 27, 2003, at 11:19 PM, Gerold J. Wucherpfennig 
wrote:
> I've installed many packages into /opt to
> get rid of "put everything into /usr/bin".
>
> Now my CFLAGS and CXXFLAGS lines are _really_ long,
> because I have to include the include dir of each /opt dir.
> ( -I/opt/package/include ...)
>
> Is there any chance to get a "includes.conf" file in /etc ?
> This should be a kind of ld.so.conf and list all include directories
> which gcc should include at compile time.
>
> Maybe a /etc/includes.conf can even let some distributors put some 
> things
> out of /usr/bin...  that would be _really_ good :-)

The way this is normally handled is to sym link all the

	/opt/emacs-20.31/include/*

files into

	/opt/include

This way, a single -I/opt/include will pick up all packages.  Further, 
you can
link all the

	/opt/emacs-20.31/bin/*

files into
	/opt/bin

and then just put /opt/bin into your PATH.  Works pretty well.  Some 
software that
uses argv[0] to relocate the install dir, might need to be fixed to do 
a readlink
and be more intelligent about it, but in the mean time, one can create 
shell
scripts to exec real_path ${1+"$@"}.

Here is what you get when you do this:

cd lair bash[1] cd /usr/local/bin
lair bash[2] ls -lt
total 17563
lrwxrwxrwx   1 root     root           23 Jan  9 15:44 bison -> 
../bison-1.25/bin/bison
lrwxrwxrwx   1 root     root           30 Jan  7 07:16 yydecode -> 
../yydecode-0.2.9/bin/yydecode
lrwxrwxrwx   1 root     root           23 Jan  5 15:52 yacc -> 
../bison-1.875/bin/yacc
lrwxrwxrwx   1 root     root           27 Dec 29 03:39 ffmpeg -> 
../ffmpeg-281202/bin/ffmpeg
lrwxrwxrwx   1 root     root           27 Dec 29 03:39 ffplay -> 
../ffmpeg-281202/bin/ffplay
lrwxrwxrwx   1 root     root           29 Dec 29 03:39 ffserver -> 
../ffmpeg-281202/bin/ffserver
lair bash[4] cd ../include/
lair bash[5] ls -lt
total 39
lrwxrwxrwx   1 root     root           31 Jan 14  2001 libdv -> 
../libdv-20010114/include/libdv
lrwxrwxrwx   1 root     root           41 Jan 14  2001 libraw1394 -> 
../libraw1394-20010114/include/libraw1394
lrwxrwxrwx   1 root     root           29 Jan 13  2001 zconf.h -> 
../zlib-1.1.3/include/zconf.h
lrwxrwxrwx   1 root     root           28 Jan 13  2001 zlib.h -> 
../zlib-1.1.3/include/zlib.h
lrwxrwxrwx   1 root     root           29 Jul 31  2000 gtk -> 
../glibgtk+-1.2.8/include/gtk

Additioanlly, info/*, man/*/* lib/* should all also be linked.  The the 
MANPATH can
be short, the PATH can be short, the -I and -L lines can be short, you 
can switch
packages on the fly anytime you want, and it just works, backwards or 
forwards, you
can install as many packages as many times as you need, rm -rf will 
deinstall nicely,
and best of all, if you need to, you can do things like
PATH=/opt/goodemacs-20.31/bin:$PATH to hand pick a non-default package, 
or -I -L the
non-default package, if you need to.

Someday this will be obvious to all, until then, spread the word.

With this style of management, gcc doesn't really need a way to do this.

Re: gcc and include dirs -> do we need a /etc/includes.conf?

[Michael S. Zick]

[-- Attachment #1: Type: text/plain, Size: 718 bytes --]

On Friday 28 February 2003 12:47 pm, Mike Stump wrote:
> On Thursday, February 27, 2003, at 11:19 PM, Gerold J. Wucherpfennig
>
> wrote:
> > I've installed many packages into /opt to
> > get rid of "put everything into /usr/bin".
> >
> > Now my CFLAGS and CXXFLAGS lines are _really_ long,
> > because I have to include the include dir of each /opt dir.
> > ( -I/opt/package/include ...)
> >
> > Is there any chance to get a "includes.conf" file in /etc ?
> > This should be a kind of ld.so.conf and list all include directories
> > which gcc should include at compile time.
> >
If using the GNU configure/make system...
Consider setting up a "config.site" file.

Attached sample is from the tiff-v3.5.7 package.

Mike

[-- Attachment #2: Sample Site Config File --]
[-- Type: application/x-bzip2, Size: 3061 bytes --]

BZh91AY&SY
«ðF\0\x02‰ÿ€dp\b\0|÷ÿ¿?ÿÿð¿ÿÿþ`\füº' †ä\x0eo´®÷¹ow½Õ]·¦â¤®Ç@â)2Ñ\x06„	£Hi‚4ž‰©§\r\x1354ÐôƒF™=&ƒ&@5=&€™OBjOSdÔõ=OPh\x06€\0\0\0\0\x01 \x13B\x13\x12jŸˆ\x12=CÒh\fš4\x06€Ñ“Ñ\r\x0fH\x02BB\x10&\x13
¦ÄõGꍨÑêm@\0oT?Q¨z€\x06š\x0e\x1a\x194ÐÓ#CLŒƒ##C 14dÐ\x06LŒC	\x12FM	„\x11 Òž‘êh\r44\0Ð\04\01,…’M$\x1a\bMlŸ+¦:ø¢þÌ,ìÂ166#í\x7f/Ÿæ®>\x7fD³Ç¡e\x7fñ]ùB&Ó\x06u„û©.LÖM<\x15ÙÝТý\x18å1\x19™ƒ0G•\x02k4\x100‹£\÷{ÏñÎúâ¹zÊÕÕ˜ìÁÒó\é*\x05A^[b,Áý]mFy\x7fO+ÆøuèOå$ä\x04Ì«"\x0fµ-\0\2\x01`´m,‹Rx0ü5\x1fúÚm\x0e9zûÐ(Rç\v\x19\aF\x18½¾V\x04xÍݱVD]¢kÚî^>½Ý»‘Å&½©V\x03¶ÌUZÆÎ|ªË.z7˜“fT\0¹%ÁvF¡(IR”Q0{::Ìs·x·Ãõ¡i’dbú™_ÜfDVµ\x1f\x1f*Òº7ž\x12ç\x04}<ú6OJeùGrv±èúº¯d¯;9Á‘‹¾-îäÝÕÁ·Š¬áÖ&åd›\x1f °s»sᇠÝ\x01q¬VbN-K’\r\x0e Y¢!P­™\x18\x15ˆ&NéÃSáˆE„z25sm¿{€´Ùí¦*=¾DÎc\r óõè4— \x15ëáfä‘\x02ZÚµ^[\f÷ù ,\x1a\fûÒC[„\x1a¬\x0fyî¯\x0e€)ÔéŠbÔT\x19-™>ø™«Šv\x1d¬\x1c&ͳ\x0e‰eîÆ7Jò³VŽ\x17¡1au¼ÙœÀæ°¥Ž2T…äDed”â©	g\x1c}ø{ ;R¸­FØIS» $6D\féQÇlC\x16È\x1en[‹`üLlÔ}\x18\x05ϤM^["$r&â›ëÆÇM¨tXJqJ5á'€Y\x18–?ù^[+ÏR+%i@y¥š‹„`ÝA‡vÒ€™ÀjhÈ_™·A	\x18A±<TX¬RþLó—Ü2šk„¥Œ¯Š[5\x12.­ymPˆ¸(¦¾Ê\x1a\Ø`qŠf\x0eï+ï”\rMãLbç`\x1c$k•žêQ` Á䚘¦©Œ\x04Ô\x11L®gD\x0e\x12àɦKØ—Kè²y3lìÝdø\x1c\x03ï¹
î«ñŸ\x1få@¾F‘ùÀKɯÜÒòb¦£ó` ÆÚÃ\x14^[Cc´b´â^[I‰¤"½Þ‚\a  \x1d#5´Ê\5U\x10"àÄy\aš¿\x10퇉[\x1eœ,NnoR2”<ðˆo\vÉ\x0e-\x0e^^ÏŽøÇ=äN£NCš2ÝP~ェ6ô˜Ò¹Ôu_£\x11†\x05\x13sR +7jJ£ÂŠã„¯`óß¾~€),EÔó B>‚Æ\x13ëa`V‘\r{²¶Ê¤¦‚\x17R\x1c´ém¢ô¶Ç&ˆ	T¤ºÂ\v±ÑVäp°\x1a¤”„Ì\x0e«¶ÿiû­J\x05\x7f\x02˜ÕêPxÕ\x12‘»ö†L¶«'ƒ\x19$a !\x18€\x16GM3ŠóÒ\x11Ø\0âŽ\x7f\x11ÏV¡*\x0e£ûŒ¥|?$zQf\x13ãJ|Ë߉ð5ðÁ’Öeë š\x1fâ?Hd\x02L\x06\x0f¡‹èN(%\x12\x14 #Ÿ'h¨uQŸM¢½S®Y\x10ç\x05f{ÇÙ¢2†t—\x18ÝE_Óy\rÒÜîež‡M—Y:\x15•\x14‹^[OŒ‚Ã<x\x7fwfS1ù¡\r\fÆ\x12ýF•¶™âZ cN3êß\x19𝧄\0.&6ìÑÚRiýºñÙzfe™\x04°ÙÌÍyHM§Ñ·rèßu6Ý#c°Ö?Ý\x13¨§^!\x06e9æE¹À¯	œy9)D)p‰2Òxu]Ìuô\x17V\0\x1cÁ\v\x1f\aæ†RÀE3-Ç\x11\x04 ²AÄ^[Szçë8ÝÌq\x1er\x12R–»xn·®KiµcimWPÑžÒ0â\x10:”,R+QšäØ}O\ˆ:ΉiƒÉD\x0f\x03—\x12¢B¸G‰Ã\x1dÖî\r3Z²ô¾í³J\x11îÛ§6}1³\x10\x03]^[»?êT“\x04 I\x17¥êˆG(EÛlYYãGTìnŽ81‹KƒñÑŸ\bÏ…Ý\x06Ø\x1f<å Ç´‚}…\x10a\x1dA““Âùó7tb3ŽÊw\x01f¯M¶œÆ\x13ñ3€¶@VI1«â\x1c5u\x0fBVÚS\îìuçŠfYs´í\v¢äfŽ„eÆZBi\x1dc†,PáÀ™´@“£^[
صL\x04ŽKf¿s\x05\x1a\x10á2`&ÉÁ\x05ÀiDˆ=X`&¸5\x12	À¥‘„B–Üð©×€\x15Â|\f,l²ô°0ò×\x17ZPØ«°17›J\x06MuV­À1  5_­…ˆÁ] nw'\f\x06ƒ©cG\x18#\f!Ľ\x15 Fžì2óüÝù1F³åªý‡«Ëßó\x15AݱŠ\x18«#¢eâ±\x10B\x01 £b‘\x14ã觃В(H\bÊMç³nã"pü-Li£-\x17*ª\r­\x14]½¾Ý¾ël\x1eo\0Æ·Ò1Î)¥‚¨\x14\x04/¥\x1dØ@D\x0fæfcò¤|¥‰b"¥Û‘\x11™ð}œ„W@$ùÐ]„\x12¤\\x0e\f!¥@ῼ/+¤8î\x10–2ª—ç|iCŐïÐòÉf‚I†
h$‘\0L›\x05`8Â\x10\x195xZ\x12epº·‰X‹à²cLm6khæT»‹\f‰6©®´aÞù‹F€"óbD”8X\x16“(b\0u\x1e†@6\x15NJg¸'NV„xz@¡a N$LIB«•\x02¸\x1aºnbe\x06ê#lhÀø\ba6¨z†p«Š™\x12Œk\x10¨LÉBF\x06ìB˜\b2S)»\vÞ\x16Ç\x06\x14CÜ$Û\x14 —\r›ò­È7\x7fÅ¿=\x16E%\x04ª™®koeN\x12ì­Ã\x14u\fPz°QŸ¸·’\x0f\x021\x17	®\x17åb–)½WTHM’YÝéï‹ø\vX’˜«ž’‰\x10¢9èi]€n$wRŽ¬Pcä°Ë²\rî\x1f#dµ¾5•ÒÖ\r\x11eoÀXš²£ôá\x16Ø\x15øyE˜Ò=¯§‹=&\x1cñÉ:P;„¥Á´˜KÕ"(s5˜ÿçzNà¥Â^[H¾\b~Áa\x12;ýÂ(ÃI€¾ˆ+Y‹‚ÓÃŽåÕ¸<é\x1f^[›¢\x17±¤6’űX\x02˜2]Ž¾¨¨¦Ø]\f\và‡\x0f{ì\x1dÇ©w>H\x14\x03+Î\x18Bì°LV÷™£3&vÞ\rŽòÓ±À-a\x01Q´˜¼\x01À¯DÖ8´¸€Å¹Ô8ßÅïmñmËoœÝ›å™Þµ#[W\r\x181€Ø*ÐkÙaTŽû30ª[\x06Ómµà¿ep[«U\x16C 6\rçX%wM³R9ō×WeXÁV8˜1\b X_íd\x0fOÁºÆÎ4
*õ.ר6^[Ô^[iÝÂðͦ3›\x03odß\x16¼¶ÓH’^[ud\x1dö]Û­»y\x1aŒr&í}\x18þ³\b«\x01’1’àr\x03ŠëÍç’m\x1d&”AÖâ0A
…H"\x17!“©\0èSÝž\x01Ð\x10ŠíQFb“`誠de1ltË\x16P-,éFA;,d\x04‡®c\0l‚n4£™6ðUÍ|V\x12X\x01´.÷†ŒçÞ\x0fZÔ‘\f€³ÂOU1w9mŽôŽ'ÔõNn›hoÐ×­¤YÙ5Þ‘ÊØ\x17C²<%\x1cD\x1fc\x02É\x06îÕáAcf±\x13‚ 3Fƒâ<Y½›L!~g€‹îê\viiáH+!ÖÛaÆÒ\x18ÄÙ›2ø¢ÊNXö!H\x13¬’ÓÄ\x10u‹qqÏ•†]rô³¸…^[nYày;Å•†Vj\x19®7žT0[\x18miN}4\x17˜[ævŠ9 ‘¥õHÜ÷i]A;ƒ–\x11£\x11sÚ\x16|¹B\x0eØ6X4M1¶™²\x11ÆFöI"D	T”§ÁÈ\x0e¹Eì\x02à<ßá\x06q\x05kš\x1e½F¢®\x17¢\x12‚(8ÓP$|\a¸·\x01-\vˆ]í\x0eThúUóš¼;‰Ð¬`\x14\x11N¸¦È/šRj ®qs‘$\r6›\x1cÓ<è=M™l£\x11[<©\x16Wf{¬°ä°k±+Æ©æ¡8KéjÙöõeíwfç-ÖB™!ÏF‰a‘¬ i¢Ìmtõ…³Ê\x04zö¸ZÓ\fpSž\x13Ï¢vŠ±„šjhÀðç~O$áÄïJ¹ô…¡†\x16Î@‹L\x166\x05kðè\v¨Ê16à‘0á’š0wÕɐ0¤ej\aC;©RÐïP³
Ö”J™H*\06åì-Á@ÆäU,l$‰Œ t—H°„ ´eè\x05­a\x12\x02Á’7rÏ~¼S§LÚÀêîS“B‘gˆV ¸Ãk\x12ˆaKP¥É\x15íÑ+V†²‚‰an‹&°U$rÏ€\x19cª^r\x05Ø\x18^[ÈÒF•‡@P¹\rˆÊ-\x12|\x11|\x06!€\x1cU=ëîß=k$Î\x0f\x1dÑdíÖÅ=\x02Æ \x11áj5–]?^F³‡N¯!þ;]\x05BGfuÆÉ…‹…1÷ÏŸ]ã\x02Ê#Lû7¿žI‡˜\x1e|Ö‚ù8žÏ—§à?ø»’)„€U_‚0

Re: gcc and include dirs -> do we need a /etc/includes.conf?

[Russ Allbery]

Gerold J Wucherpfennig <gjwucherpfennig@gmx.net> writes:

> Oh, this is really heavy :-)
> so many symlinks...

The GNU stow program will manage them all for you if you want.

-- 
Russ Allbery (rra@stanford.edu)             <http://www.eyrie.org/~eagle/>

Re: gcc and include dirs -> use the C_INCLUDE_PATH var.

[Gerold J. Wucherpfennig]

C_INCLUDE_PATH does exist?

[root@pc103 ~/cvssources/gcccvs]# grep -rl C_INCLUDE_PATH  .
./gcc/gcc/ada/gnat_ug.texi
./gcc/gcc/doc/cpp.1
./gcc/gcc/doc/gcc.1
./gcc/gcc/doc/cpp.info-4
./gcc/gcc/doc/cppenv.texi
./gcc/gcc/doc/gcc.info-10
./gcc/gcc/doc/gcc.info-23
./gcc/gcc/doc/gcc.info-39
./gcc/gcc/doc/gcc.info-40
./gcc/gcc/cppinit.c
./gcc/gcc/gcc.info-36
./gcc/gcc/ChangeLog.1
./gcc/gcc/gcc.info-9
[root@pc103 ~/cvssources/gcccvs]#

That's great :-)

So we don't need a special config file.

I hope that some of the major distributors will use this
variable and put more things into /opt/* instead of /usr (/usr/bin ...)


Thank you very much for this info :-) 


On Friday February 28 2003 16:34, you wrote:
> On Fri, Feb 28, 2003 at 04:32:12PM +0100, Gerold J. Wucherpfennig wrote:
> > On Friday February 28 2003 08:19, I wrote:
> > > I've installed many packages into /opt to
> > > get rid of "put everything into /usr/bin".
> > >
> > > Now my CFLAGS and CXXFLAGS lines are _really_ long,
> > > because I have to include the include dir of each /opt dir.
> > > ( -I/opt/package/include ...)
> > >
> > > Is there any chance to get a "includes.conf" file in /etc ?
> > > This should be a kind of ld.so.conf and list all include directories
> > > which gcc should include at compile time.
> >
> > Alternatively there could be a special envionment variable "INCLUDE_PATH"
> > - a kind of LD_LIBRARY_PATH ...
>
> Try C_INCLUDE_PATH.

Re: gcc and include dirs

[Michael S. Zick]

On Friday 28 February 2003 05:40 pm, Gerold J. Wucherpfennig wrote:
> On Friday February 28 2003 17:56, Michael S. Zick wrote:
> > On Friday 28 February 2003 09:43 am, Gerold J. Wucherpfennig wrote:
>
> The only (but not really) "clean" solution I can imagine is to
> - fix gcc to look into /opt/*/include,
> - fix ld to look into /opt/*/lib
> - fix bash to look into /opt/*/bin and /opt/*/sbin
> - fix man to look into /opt/*/man
> - fix info to look into /opt/*/info
> - ...
That will be a hard sell. 
The convention in the *nix system world is for the
command shell to do all wildcard expansions, not
the individual programs.

Mike

Re: gcc and include dirs

[Gerold J. Wucherpfennig]

On Saturday March 1 2003 01:41, Michael S. Zick wrote:
> On Friday 28 February 2003 05:40 pm, Gerold J. Wucherpfennig wrote:
> > On Friday February 28 2003 17:56, Michael S. Zick wrote:
> > > On Friday 28 February 2003 09:43 am, Gerold J. Wucherpfennig wrote:
> >
> > The only (but not really) "clean" solution I can imagine is to
> > - fix gcc to look into /opt/*/include,
> > - fix ld to look into /opt/*/lib
> > - fix bash to look into /opt/*/bin and /opt/*/sbin
> > - fix man to look into /opt/*/man
> > - fix info to look into /opt/*/info
> > - ...
>
> That will be a hard sell.
> The convention in the *nix system world is for the
> command shell to do all wildcard expansions, not
> the individual programs.

Yes indeed, GCC and CO. can't use shell wildcards.

They have to examine the dirs in /opt and (maybe) cache the results!
(I just used wildcards to to make it easy to understand.)

What do others think about this proposual?
(Alternatively GCC and CO. could use configuration files like ld.so.conf)


IMHO there has to be a "clean" solution to this "/opt" issue.


Please CC me

Gerold

Re: gcc and include dirs

[Zack Weinberg]

"Gerold J. Wucherpfennig" <gjwucherpfennig@gmx.net> writes:

> IMHO there has to be a "clean" solution to this "/opt" issue.

There is.  Use a real package manager and put everything in /usr as
God intended.

zw

Re: gcc and include dirs

[Michael S. Zick]

On Saturday 01 March 2003 03:30 pm, Zack Weinberg wrote:
> "Gerold J. Wucherpfennig" <gjwucherpfennig@gmx.net> writes:
> > IMHO there has to be a "clean" solution to this "/opt" issue.
>
> There is.  Use a real package manager and put everything in /usr as
> God intended.
>
> zw
Some times the obvious answer is the best answer.
Mike

Re: gcc and include dirs

[Michael S. Zick]

On Saturday 01 March 2003 04:51 pm, Michael S. Zick wrote:
> On Saturday 01 March 2003 03:30 pm, Zack Weinberg wrote:
> > "Gerold J. Wucherpfennig" <gjwucherpfennig@gmx.net> writes:
> > > IMHO there has to be a "clean" solution to this "/opt" issue.
> >
> > There is.  Use a real package manager and put everything in /usr as
> > God intended.
> >
> > zw
>
> Some times the obvious answer is the best answer.
> Mike
And then there is:
http://relink.sourceforge.net/
Mike