Re: Problem in split_basic_block

["Zack Weinberg" <zack@codesourcery.com>]

"Douglas B Rupp" <rupp@gnat.com> writes:
>> > + prefix=/gnu
>> > + local_prefix=/gnu
>>
>> > + #define MD_EXEC_PREFIX "/gnu/lib/gcc-lib/"
>> > + #define MD_STARTFILE_PREFIX "/gnu/lib/gcc-lib/"
>> > +
>> > + /* Specify the list of include file directories.  */
>> > + #define INCLUDE_DEFAULTS    \
>> > + {    \
>> > +   { "/gnu/lib/gcc-lib/include", 0, 0, 0 }, \
>> > +   { "/gnu_gxx_include", 0, 1, 1 },    \
>> > +   { "/gnu_cc_include", 0, 0, 0 },    \
>> > +   { "/gnu/include", 0, 0, 0 },            \
>> > +   { 0, 0, 0, 0 }    \
>> > + }
>>
>> this also interferes with cross compiler use
>
> I admit I don't know this stuff very well, so I fiddled around with
> these macros until I got something that worked.  In the past
> building a full cross compiler hasn't been an issue. If there's a
> better way to do it, please work with me to figure it out.

I'm the wrong person to ask.  I know that hardcoding values for
anything with "prefix" in the name causes problems, and I know that
defining INCLUDE_DEFAULTS does the same (because it overrides the
variations that cppdefaults.c puts in when cross compiling).

Talk to people like Dan Jacobowitz and Eric Christopher, they know
more about cross compiling.

zw