On Wed, Jun 27, 2001 at 08:44:38AM +0200, Emiliano wrote:
> Alexander Bokovoy wrote:
>
> > > Which is exactly why I want it there. Are there harmful side-effects
> > > if we have this in when used with 4.0.6?
> >
> > Nothing, I think. -DHAVE_CONFIG_H will be mentioned twice on the command
> > line but that's normal.
>
> *grin* define 'normal'[0]. Nothing normal about the 4.0.5 build env
> IMNSHO. Anyway, now in a CVS near you.
:-) My 'normal' wasn't touched 4.0.5 build env in any case. By 'normal'
here I meant that it is common to have several equal includes, defines,
library paths on GCC command line (-I/usr/local/include -DHAVE_CONFIG_H
-I/usr/local/include, for example). It is 'ugly', of course, but nobody
thought about reduction statements :-)
> Emile, gradually getting his momentum back.
>
> [0] yes, of course I knew you meant 'harmless'. But that would have
> ruined the joke.
:-) Yup.
Anyway, now libmidgard's configure tries to remove complexity from both C
flags and LD flags. It means that unneccessary -I/usr/include and
-L/usr/lib will go out, making resulting flags lighter.
--
--
Sincerely yours, Alexander Bokovoy
The Midgard Project | www.midgard-project.org | ALT Linux Team
Minsk Linux Users Group | www.minsk-lug.net | www.altlinux.ru
-- If it heals good, say it.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
