This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: bootstrap/8657: No rule to make target `bootstrap' in directory 'gcc'



Hi,

For my second try I used the objdir /software/gcc-3.2.1-obj. There I invoked
the configure-script with absolute path: /software/gcc-3.2.1/configure 2>&1 | tee configure.out.
Then I did gmake bootstrap 2>&1 | tee gmake.out
and still got the error "no rule to make target bootstrap".

(See attached file: gmake.out.gz)(See attached file: configure.out.gz)

Does anybody see further mistakes I may have made?


Datum:         20.11.2002 22:46
An:            Neil Booth <neil@daikokuya.co.uk>
Kopie:         reichelt@igpm.rwth-aachen.de
               gcc-bugs@gcc.gnu.org
               gcc-prs@gcc.gnu.org
               nobody@gcc.gnu.org
               Rolf-Alois Walter/OuB/Zentrale/DeuBa@Zentrale
               gcc-gnats@gcc.gnu.org


Betreff:       Re: bootstrap/8657: No rule to make target `bootstrap' in directory 'gcc'
Nachrichtentext:

Neil Booth <neil@daikokuya.co.uk> writes:

>>
>>     First, we highly recommend that GCC be built into a separate
>>     directory than the sources which does not reside within the
>>     source tree. This is how we generally build GCC; building where
>>     srcdir == objdir should still work, but doesn't get extensive
>>     testing; building where objdir is a subdirectory of srcdir is
>>     unsupported.
>
> This latter "unsupported" configuration is what (at least) me and
> Jakub build on, and it has *always* worked.  Maybe the docs should
> be updated.

In my experience, if objdir is a subdirectory of srcdir AND configure
is invoked by a relative pathname, it doesn't work.  But if configure
is invoked by an absolute pathname, objdir can happily be a
subdirectory of srcdir; and if objdir is not a subdirectory of srcdir,
relative paths work fine.

I don't remember the exact failure mode, but it was clearly a case of
some shell script fragment somewhere getting mixed up about how many
../ components it needed to put in a pathname.

zw






--

Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

Attachment: gmake.out.gz
Description: Binary data

Attachment: configure.out.gz
Description: Binary data


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]