This is the mail archive of the
insight@sources.redhat.com
mailing list for the Insight project.
Re: Problems building TCL for insight on cygwin & win2k
- To: "Keith Seitz" <keiths at cygnus dot com>
- Subject: Re: Problems building TCL for insight on cygwin & win2k
- From: "Andy Hare" <ahare at btinternet dot com>
- Date: Thu, 25 Oct 2001 21:54:30 +0100
- Cc: "Insight Mail list" <insight at sourceware dot cygnus dot com>
- References: <Pine.GSO.4.33.0110251215490.23990-100000@makita.cygnus.com>
Keith,
Thanks for your input I am trying the configure again without the host=
line. The reason for the with-headers is that I am using newlib and the
compiler is to be used on an embedded ARM micro, the configure actually
configs the whole toolchain, binutils, gcc and insight.
uname -a gives
CYGWIN_NT-5.0 DUAL-BEAST 1.3.3(0.46/3/2) 2001-09-12 23:54 i686 unknown
Will let you know what happens with the new build when it finishes.
Andy Hare
www.ahare.btinternet.co.uk
----- Original Message -----
From: "Keith Seitz" <keiths@cygnus.com>
>
> Hmmm. What version of cygwin are you using? (uname -a) Right now, you can
> ONLY use a current net release of cygwin to build the public repository.
> (This should be the case for everyone except Red Hat GNUPro customers.)
>
> I know I just built this thing yesterday without incident.
>
> I'm updating my sources now, just in case, but I can see some obvious
> differences between the way you have configured your toolchain and the way
> I do it. Of course, this may not be the problem, but who knows? It's
> worked once this week already. ;-)
>
> Actually, I'm gonna say almost the same thing that I told the last person
> with configure problems. When configuring, either specify "--target" alone
> OR specify "--target", "--host", and "--build". Never use just two of
> them. This is empirical only. YMMV.
>
> I think that if you did this, your problem would go away. I don't think
> that "i586-cygwin32" is the appropriate host triple nowadays. I use
> "i686-pc-cgywin".
>
> I also never use the 'CC="gcc -mwin32"' thing. I know this was needed some
> time in the past, but I've never needed it at all in the last few months.
>
> Finally, the last thing that causes me some concern.. Why do you need to
> use "--with-headers"? I've never used that before except when doing a
> cross build for another OS.
>
> So, try using:
>
> /GNU-Source-Code/src/configure -v \
> --prefix=/xgcc-arm/gnu \
> --exec-prefix=/xgcc-arm/gnu \
> --target=arm-elf >$(HOME)/configure.out 2>&1
>
> Let us know if it helps.
>
> > I hope you can help as I have been trying to get insight built for the
last
> > week.
>
> You should have spoken up sooner...
>
> Keith
>
>
>