Re: Crossgcc for m68k under Gentoo Linux

[Rick Jenkins <rick at hartmantech dot com>]

Hi Jim,

On Wednesday 26 July 2006 18:12, Jim Tison wrote:
> My (Linux FC4) system has it as:
> ? ? /usr/include/linux/limits.h:#define PATH_MAX ? ? ? ?4096
> 
> <limits.h> appears to be the 'standard' place for it per the Single Unix 
> Standard.

Right. Turns out that my system defines it in exactly the same place (and 
with the same value).

The entire test code in question, which is generated within the testhello.sh 
script, is:

#include <stdio.h>
#include <limits.h>
static long x = LONG_MIN;
int main() { printf("Hello, world!  LONG_MIN is %ld, PATH_MAX is %d\n", x, 
PATH_MAX); return 0; }

As far as I can see, the relevant file for the cross-compiler is 
/opt/crosstool/gcc-3.3.3-glibc-2.3.2/m68k-unknown-linux-gnu/m68k-unknown-linux-gnu/include/linux/limits.h
and this file would be included in the 
/opt/crosstool/gcc-3.3.3-glibc-2.3.2/m68k-unknown-linux-gnu/m68k-unknown-linux-gnu/include/limits.h
by a #include_next statement, if the include tree were correctly set up. Some 
error in the include tree prevents this inclusion from taking place.

This is not a vital issue for me, since I deprecate #include_next in my 
embedded code for just this sort of reason. It does bring a premature halt 
to the test suite, however.
-- 
Rick Jenkins <rick@hartmantech.com>
Hartman Technica           http://www.hartmantech.com 
Phone +1 (403) 230-1987 voice & fax
221 35 Avenue. N.E., Calgary, Alberta, Canada T2E 2K5

--
For unsubscribe information see http://sourceware.org/lists.html#faq