2011/7/2 Robert Millan :
> 2011/7/2 Benjamin Kaduk :
>> There is a functional difference between '-nostdinc -I/usr/include -I.' even
>> when the standard include search path is just /usr/include -- the standard
>> include paths are always searched last (unless -nostdinc is given), even if
>> they a
2011/7/3 Matthias Andree :
> Note that there are GCC-version-specific directories for the more
> intricate details such as stdarg.h and compiler-specific builtins -- you
> don't get those with -I/usr/include either.
I know. That's actually the problem I'm trying to solve ( not found).
--
Robert
Am 02.07.2011 17:25, schrieb Benjamin Kaduk:
> On Sat, 2 Jul 2011, Robert Millan wrote:
>
>> The userland aicasm utility in sys/dev/aic7xxx/aicasm/Makefile is being
>> built with "-nostdinc -I/usr/include" options. Unfortunately this breaks
>> building aicasm on systems using the upstream version
2011/7/2 Benjamin Kaduk :
> There is a functional difference between '-nostdinc -I/usr/include -I.' even
> when the standard include search path is just /usr/include -- the standard
> include paths are always searched last (unless -nostdinc is given), even if
> they are explicitly listed on the com
On Sat, 2 Jul 2011, Robert Millan wrote:
The userland aicasm utility in sys/dev/aic7xxx/aicasm/Makefile is being
built with "-nostdinc -I/usr/include" options. Unfortunately this breaks
building aicasm on systems using the upstream version of GCC, where
"-nostdinc" disables more search director
The userland aicasm utility in sys/dev/aic7xxx/aicasm/Makefile is being
built with "-nostdinc -I/usr/include" options. Unfortunately this breaks
building aicasm on systems using the upstream version of GCC, where
"-nostdinc" disables more search directories than are enabled by
"-I/usr/include".
T
6 matches
Mail list logo
