Re: native or target?

[Andrew Cagney <ac131313@ges.redhat.com>]

>
>> BTW: Is it a requirement for a new port to be buildable as a target
>> only, or can we provide a native-only port as a first step, and then
>> eventually improve it to support "--host=--target=interix"? This is
>> out-of-the-box thinking, I don't see how this would help the problem we
>> have been discussing, but I think this is an interesting piece of
>> information to know.
> 
> 
> I'm inclined to say yes.  If I can configure GDB with
> --target=i386-interix on my i386-freebsd system, I can test the
> target-dependent code, and you run a smaller risk of me accidentally
> breaking your port when making changes to the common i386 code.

Two conflicting answers, hmm :-)

It's all smoke and mirrors anyway.  What gets built with the cross 
debugger is determined by what is listed in config/i386/interix.mt.  If 
a file isn't in that list then it won't get built so no one will see the 
problems it contains ;-)  As Mark points out, it is very much to your 
advantage to have all code working as a cross target.

Anyway, I think this thread has identified the need for a 
i386-interix-tdep.c file.  If you haven't already, I think a good easy 
(????) step would be to create an (almost) empty i386-interix-tdep.c 
that just contains the interix ``sniffer''.  Since you'll be needing to 
override architecture methods, you'll definitly need this bit of 
infrastructure working.

Andrew