From: se7en_hills <elumalai_selvan@yahoo.com>
To: gcc-help@gcc.gnu.org
Subject: Re: Help!!! build failed for GCC-3.2.3
Date: Sat, 22 Mar 2008 15:05:00 -0000 [thread overview]
Message-ID: <16222770.post@talk.nabble.com> (raw)
In-Reply-To: <47E45227.801@myrealbox.com>
Sir,
I tried with gcc-4.1.2 to build and after i configure,it ended up showing
the following error message
Administrator@lakshmih-588bf4 /cygdrive/c
$ cd gcc_build
Administrator@lakshmih-588bf4 /cygdrive/c/gcc_build
$ make
cd /cygdrive/c/gcc-4.1.2 && autogen Makefile.def
/cygdrive/c/djgpp/tmp/dj100000: line 1: autogen: command not found
make.exe: *** [/cygdrive/c/gcc-4.1.2/Makefile.in] Error 127
The source is in C:/gcc-4.1.2
and i created a folder named gcc_build to build.
Thanks and regards,
karthik
Tim Prince-7 wrote:
>
> Rupert Wood wrote:
>> se7en_hills wrote:
>>
>>> $f:/project/gcc-3.2.3/configure
>>
>> I'm not a cygwin guru but I suspect this is the problem. Try using
>> "/cygdrive/f/project" here too rather than "f:/project".
>>
>> I'd guess the path with the f: is getting written into the Makefile as
>> the path to the GCC source directory and it's only cygwin shells that
>> understand the f: syntax.
>>
> It's possible "7" has run into the situation where
> export HOME=/cygdrive/f/project/gcc-3.2.3/
> will help.
> Reference to the options required/supported in cygwin gcc builds would
> help.
> It's also important to decide on the objective. Re-building all of cygwin
> with a compiler older than the usual one could be an endless task. So
> could building all languages of a version of gcc older than the one used
> to build cygwin, while attempting (default) options not supported for
> cygwin, possibly without installing the prerequisite components.
>
>
--
View this message in context: http://www.nabble.com/Help%21%21%21-build-failed-for-GCC-3.2.3-tp16202260p16222770.html
Sent from the gcc - Help mailing list archive at Nabble.com.
next prev parent reply other threads:[~2008-03-22 15:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-21 17:06 se7en_hills
2008-03-21 17:33 ` Rupert Wood
2008-03-22 0:26 ` Tim Prince
2008-03-22 15:05 ` se7en_hills [this message]
2008-03-23 4:18 ` Tim Prince
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=16222770.post@talk.nabble.com \
--to=elumalai_selvan@yahoo.com \
--cc=gcc-help@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: link
Be 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).