From: "Andy Hare" <andy@hare.u-net.com>
To: "GCC-Help" <gcc-help@gcc.gnu.org>
Subject: Compiling EGCS under cygnus b20.1
Date: Sat, 01 Apr 2000 00:00:00 -0000 [thread overview]
Message-ID: <000401bf70e3$ca77d000$0100000a@dualbeast> (raw)
Message-ID: <20000401000000.89yfHu1shdAUu6DknaseylbRgQ9-72f7WASLqVxfDrE@z> (raw)
Hi,
I am trying to compile the egcs snapshot from the 31/1/00 from cygnus
sourceware. I am running cygnus b20.1 under NT and cross compiling to an ARM
target using the following configure and make commands
> /c/cygnus/GNU-Source-Code/egcs/configure -v \
> --prefix=/c/cygnus/xgcc-arm/gnu \
> --exec-prefix=/c/cygnus/xgcc-arm/gnu \
> --host=i586-cygwin32 --target=arm-elf >configure.out 2>&1
>
> make -w all-gcc install LIBGCC2_DEBUG_CFLAGS="-g1 -O1" LANGUAGES="c" >
make.out 2>&1
When compiling I get the following errors:
>In file included from
/c/cygnus/GNU-Source-Code/egcs/gcc/fixinc/fixincl.c:25:
>/c/cygnus/GNU-Source-Code/egcs/gcc/fixinc/fixlib.h:28: auto-host.h: No such
file
> or directory
>/c/cygnus/GNU-Source-Code/egcs/gcc/fixinc/fixlib.h:29: gansidecl.h: No such
file
> or directory
>/c/cygnus/GNU-Source-Code/egcs/gcc/fixinc/fixlib.h:30: system.h: No such
file or
> directory
>make[2]: *** [fixincl] Error 1
>/c/cygnus/GNU-Source-Code/egcs/gcc/cpp.texi: No such file or directory
>make[1]: *** [cpp.info] Error 2
>make: *** [all-gcc] Error 2
The makefile in fixinc also was missing the exeent variable to generate the
correct filenames during compiling and then the subsequent install.
Has anyone managed to get this working or is it a known problem. cpp.texi
definitely exists and it can be listed to the console.
I have the ecos ARM toolset compiling but wanted to get the latest tools
running.
Andy Hare
next reply other threads:[~2000-04-01 0:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-06 12:50 Andy Hare [this message]
2000-04-01 0:00 ` Andy Hare
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='000401bf70e3$ca77d000$0100000a@dualbeast' \
--to=andy@hare.u-net.com \
--cc=gcc-help@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).