This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Porting GCC to RDOS and C++ issues
- From: kaih at khms dot westfalen dot de (Kai Henningsen)
- To: leif at rdos dot net
- Cc: gcc at gcc dot gnu dot org
- Date: 31 Dec 2005 13:41:00 +0200
- Subject: Re: Porting GCC to RDOS and C++ issues
- References: <043101c60d52$110f69e0$410aa8c0@codab.home>
leif@rdos.net (Leif Ekblad) wrote on 30.12.05 in <043101c60d52$110f69e0$410aa8c0@codab.home>:
> Mike Stump:
> > make will build libgcc for the target, specifically, you should be
> > able to cd gcc && make libgcc.a to build it.
>
> It did when I added --host=rdos to the configuration script and
> changed a couple of other files. My only current problem is that
> since RDOS uses the .exe suffix for executables, the xgcc cross-compiler
> is named xgcc.exe, even though it is a Linux executable. This problem
> is fixed by copying this file to xgcc (no extension), and re-starting
> the make process. I don't know if this is a bug in some scripts, or
> it is some misconfiguration on my part. The system should know
> that Linux executables never have an .exe extension.
Sounds like you need to study up on the --build, --host, and --target
options.
See, for example, the autoconf manual, "Specifying the System Type"; and
the gcc internals manual, "6.1 Configure Terms and History", and go from
there.
> After this build is complete, there is a gcclib.a file in the rdos-host
> directory. When I install it, however, the gcclib.a file isn't copied
> to /usr/local/rdos/lib, like the other libraries from the build without
> --host=rdos, but in another directory. I fixed this by copying the
> file to the correct location.
Yes, definitely looks like that. You should use these options exactly
once, on the top-level configure, and use the same set for everything.
MfG Kai