Tom Browder wrote:
Attached is a log of my build attempt (and the config.log).
There is a config.log file in every directory that gets configured. It
looks like you attached the one from the top-level dir which is not
where the problem is occurring.
The "make -j3" makes the output hard to read. You might try a "make
all" build from scratch to get a better look at what is wrong.
You can build a host libiberty with "make all-libiberty" and a target
libiberty with "make all-target-libiberty". The same is true for other
things, e.g. "make all-gcc" will just build the gcc directory, and "make
all-target-libstdc++" will build a target libstdc++. But "make all"
works just as well to get back to the error point.
It looks to me as if libiberty is getting compiled and tested Ok, but,
for some reason, make reports an error which then prevents a good
build completion.
These lines in the output are suspect:
/bin/sh: /usr/bin/true: Success
I don't have a /usr/bin/true on my F7 machines. There is a /bin/true.
The program true should just return without error and not do anything else.
--
Jim Wilson, GNU Tools Support, http://www.specifix.com
