public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "aschorr at telemetry-investments dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/29482] libcpp/configure - no usable dependency style found Date: Thu, 15 Mar 2007 13:23:00 -0000 [thread overview] Message-ID: <20070315132250.30743.qmail@sourceware.org> (raw) In-Reply-To: <bug-29482-13401@http.gcc.gnu.org/bugzilla/> ------- Comment #5 from aschorr at telemetry-investments dot com 2007-03-15 13:22 ------- FYI, I had this same problem trying to build gcc-4.1.2 on Solaris 8. After a lot of experimentation, I found that it could be solved by changing my PATH so that any invocations of 'make' will actually result in the execution of gnu make, and not the bundled solaris make. It seems that just running the toplevel 'gmake bootstrap' with gnu make is not sufficient: there are embedded calls to 'make' down below, and you need to have your PATH configured in such a way that these calls to 'make' will end up running gnu make. Once I made this change, I was able to complete 'make bootstrap' with no problems at all. However, for some reason I was unable to chase down, 'make install' still failed with gcc-4.1.2. But this bug must have been fixed shortly after the release of gcc-4.1.2, because I was able to build and install a gcc-4.1.3 prerelease snapshot from 20070312 with no problems at all (given that 'make' is now resolving to gnu make). I hope this helps. Regards, Andy -- aschorr at telemetry-investments dot com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aschorr at telemetry- | |investments dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29482
next prev parent reply other threads:[~2007-03-15 13:23 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-10-16 14:59 [Bug bootstrap/29482] New: " mircea_lutic at yahoo dot com 2006-10-16 15:46 ` [Bug bootstrap/29482] " pinskia at gcc dot gnu dot org 2007-01-02 16:38 ` maxim dot yegorushkin at gmail dot com 2007-01-03 12:31 ` maxim dot yegorushkin at gmail dot com 2007-01-19 22:57 ` tromey at gcc dot gnu dot org 2007-03-15 13:23 ` aschorr at telemetry-investments dot com [this message] 2009-08-08 22:53 ` steven at gcc dot gnu dot org 2009-08-09 0:09 ` tromey at gcc dot gnu dot org [not found] <bug-29482-4@http.gcc.gnu.org/bugzilla/> 2011-02-10 15:18 ` kevin at teews dot com 2021-06-06 12:59 ` nicolas at debian dot org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20070315132250.30743.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).