RE: Configure errors using host=i386-pc-interix

[Donn Terry <donnte at microsoft dot com>]

Joe:   An interested user.  Great!

 

Here's the status of what's in the official CVS for the toolchain for native Interix support.

I submitted patches for gcc and binutils over a year ago.  Some got applied, some didn't.

Then Softway got bought, and I just recently was able to get signed releases to the FSF

with my new employer on board.

 

Since then:

gcc: I have a few patches yet to re-submit (some for the first time, some old).

       There a couple of patches that have been sitting a couple of weeks awaiting

       attention.

binutils: In various states of repair.  Since getting releases signed I haven't had bandwidth

        to get the patches cleaned up and resubmitted.

gdb: Nothing yet submitted, but otherwise in the same state as binutils.

tcl, tk, readline, ...: many need a minor tweak to configure to recognize interix, but mostly

        other than that they just work.  A few "real" patches are needed.  All are also

        awaiting bandwidth.

 

I will take your comment "under advisement" (as I haven't played with cross-platform

development) and (probably) submit a patch at some point.  Or you can if you wish.

(Whether the changes I have queued up for gdb are sufficient to fix your problem,

I just can't say, but in the case of gdb, I'm not horribly surprised.)

 

Donn

-----Original Message-----
From: Joe Cossette [mailto:joec@infoark.com]
Sent: Monday, July 17, 2000 3:57 AM
To: bug-gnu-utils@gnu.org
Cc: bug-gdb@gnu.org; bug-gcc@gnu.org
Subject: Configure errors using host=i386-pc-interix

Am building for cross platform development (ARM-ELF) on a Windows 2000 system with Interix v2.2 installed instead of using the CYGWIN.

 

I had to make a minor adjustment to the configure script in the base directory to get the shell configured properly.

 

The configure script in the base directory has some code in it that looks like this:

 

  case "${OSTYPE}" in
  *win32*)

 

This code properly sets up the shell being used to run the script (i.e. CONFIG_SHELL) under a WindowsNT build environment.

 

Interix v2.2 sets the OSTYPE environment variable to "Interix", so I simply duplicated (i.e. copied) the complete block of code that did the case.  This resulted in the desired behaviour (i.e. configure appeared to run properly and I could build the source).

 

Using the above "patch" I was able to successfully build BINUTILS and GCC, but GDB would not properly build (actually, I didn't get to the "make" stage because it bombs out towards the end of the configure).

 

Thought you folks would like to know, perhaps you don't have anyone actively building on Windows 2000 w/Interix v2.2 yet.

 

If there's anything else I might be able to do that might help in fixing this problems let me know.

 

Thanks for your continued support.

 

-----------

Joe Cossette