compile on Linux-pmac

Brett Dikeman brett@arthur.malebolge.com
Fri Sep 19 21:14:00 GMT 1997


Greetings,
As you can probalby tell, I'm new to the list(wrote this after checking
the archives like a good little list member.)
I currently run Linux-pmac, and I was very interested in the egcs project.
I downloaded the most recent snapshot(9-17-97) and tried a compile, follow
this procedure, from what I could find in the docs:
-./configure
-make
well, it crunched for about 30-40 minutes, and then launched into the
libraries, and now, it's hung on a header file that (oddly enough)
references itself.  Now, I don't know much about compilers, but that seems
like an awefully silly thing to do, being recursive and all that.  So, I
thought it was simply a reference to the existing gcc stdio-lock.h, and
that made a lot more sense.  Yet it complains about:
egcs-970917/libraries/nof/libio/bits/stdio-lock.h
stdio-lock.h contains:
#include <stdio-lock.h>
now, egcs-gcc complains that it can't find it, and rightly so, since a
find / -name didn't turn up _anything_ except another stdio-lock.h in a
similar directory off the egcs tree.

Now I also have a linux-intel box(redhat 4.2) and it doesn't complain
about it.

In the past, when I needed header files, I simply stole them from other
systems.  For example, I needed a random header for my linux-pmac box, so
I stole the header file off of a BSDi box.  Worked amazingly well(heh, so
far.)
What are the recommendations/comments here?

My apologies if this is an overly silly question, or if this has been
previously covered(I checked the archives as much as I could, but they
were long and put a little too much strain on poor old Arena, which also
claims the sept. archive index contains "BAD HTML")

Thanks,
Brett Dikeman




More information about the Gcc mailing list