This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug bootstrap/11621] 'make all' fails with "No rule to make target `../libiberty/libiberty.a'
- From: "mec at shout dot net" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 21 Jul 2003 20:54:12 -0000
- Subject: [Bug bootstrap/11621] 'make all' fails with "No rule to make target `../libiberty/libiberty.a'
- References: <20030721201355.11621.mec@shout.net>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11621
------- Additional Comments From mec at shout dot net 2003-07-21 20:54 -------
Subject: Re: 'make all' fails with "No rule to make target `../libiberty/libiberty.a'
It was my error. I was running configure in the 'gcc' subdirectory,
not the top directory. Check out my 'configure' command:
/berman/fsf/_today_/source/gcc-3.3.1-20030720/gcc/configure ...
^^^
If you are curious, I often checkout trees from CVS. A tree from CVS
has that level of 'gcc' as part of its name. However, released trees do
not have that level of 'gcc' in their name. I tried to build the
snapshot tree with my CVS-oriented build script and that's how I
configured the 'gcc' subdirectory.
I fixed that and 'make all' is running fine now.
It would be nice to get a better message for this case, where the user
mistakenly configures in the 'gcc' subdirectory instead of the top level
directory. But it was operator error.
Just for completeness, although this part is moot:
I did not try removing the '--disable-shared'.
I don't have any $MAKEFLAGS.
There was no ../libiberty directory in the build tree.