gcc 2.95

gcc 2.95

[Barry Hancock]

Sir,

I am experiencing real difficulties in compiling the above version of the 
compiler as a cross compiler for the m68k.

I am following the guidelines as described in www.sthoward.com/CrossGCC as 
recommended in one of the gcc readme files, but am struggling to get it to 
compile without error.

In following the example, gcc compiles up to a point, then it errors with the 
following message :-
"
as: unrecognised option: -c68020
"

I presume a makefile or whatever should be -mc68020, but is missing the m, 
however, I cannot find it in any file.

This is not the only example - I have tried m68k-unknown-elf, m68k-aout, 
m68k-elf, m68k-gnu-elf, and so on, all with various errors.

I am wondering - is this a lost cause ? Is the m68k tree out of date or 
something ?

I am attempting to build from the sources supplied with Mandrake Linux 8.2 on 
a Red Hat Linux 6.2 system which uses egcs 2.91 on a PC.

Generally, the binary utilities build, with one or two exceptions (related to 
BFD), but gcc does not want to know.

Please save my sanity.

Sincerely

Barry Hancock

Re: gcc 2.95

[Jim Wilson]

Barry Hancock wrote:
> I presume a makefile or whatever should be -mc68020, but is missing the m, 
> however, I cannot find it in any file.

It is probably internal to gcc.  Try adding -v to the failing gcc 
command line.  I would guess a bug in one of the various *SPEC macros in 
the gcc m68k port.

> I am wondering - is this a lost cause ? Is the m68k tree out of date or 
> something ?

The m68k toolchain is not as well maintained as it used to be, but it 
should be possible to build a working m68k-elf toolchain with a bit of 
hacking.

> I am attempting to build from the sources supplied with Mandrake Linux 8.2 on 
> a Red Hat Linux 6.2 system which uses egcs 2.91 on a PC.

2.91 is really old.  We stopped supporting it a long time ago.  We are 
at 3.3.1 now.  I'd suggest trying something newer.
-- 
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com

gcc 2.95

[John Summerfield]

There are many problems;-(

I'm trying to build gcc 2.95 on Red Hat Linux 4.2 - libc.

The configure fails because it can't figure the libc minir number.

I'm using a Red Hat rpm, so to this point I'd not read how to do it.

I go to the source directory and find a README that tells me to look in the 
INSTALL directory.

In there, there's a README telling me not to be silly, go look at 
http://www.gnu.org/software/gcc/

So I have no instructions included with the package about how to build it.

Well, this is especially inconvenient to us dialup users, but never mind, I'm 
trying to work on a box separate from my by mode; that is, I'm currently 
dialled up.

The site mentions some requirements; none suggests that what I'm trying to do 
should not work.

There's a link to a FAQ. The target of the link says the FAQ's moved and 
mentions some relevant to languages.

I don't want a FAQ list about languages; I want one about the compiler itself.

There are other links to pages that have moved; the site needs careful 
revision.

I went searching for how to report bugs. One alternative was to refer to the 
BUGS file included in the package.
The BUGS file (I found it) tells me to read the documentation:
(2) With Info.  Start Emacs, do C-h i to enter Info,
then m gcc RET to get to the GCC manual, then m Bugs RET
to get to the section on bugs.  Or use standalone Info in
a like manner.  (Standalone Info is part of the Texinfo distribution.)         


Terrific. I can't build it so I can read the documentation to see how to 
report the problem that I can't build it.

To be fair, the website DIS give this email address; as you can see the basic 
documentaion included in the package and the website both needs some careful 
revision.

Now for the original question. How do I build this on a libc system? I 
currently have gcc 2.7.2.3 and libc-5.4.46-1rh42?