From: Bob Rossi <bob_rossi@cox.net>
To: Carlos O'Donell <carlos@codesourcery.com>
Cc: gcc-help@gcc.gnu.org, mark@codesourcery.com
Subject: Re: mingw svn trunk failure
Date: Wed, 20 Dec 2006 00:24:00 -0000 [thread overview]
Message-ID: <20061220002415.GD3022@cox.net> (raw)
In-Reply-To: <20061219235825.GY14845@lios>
On Tue, Dec 19, 2006 at 06:58:26PM -0500, Carlos O'Donell wrote:
> On Tue, Dec 19, 2006 at 05:59:09PM -0500, Bob Rossi wrote:
> > > Bob, could you please provide your gcc configure options?
> >
> > Hi Carlos,
> >
> > It's all here,
> > http://gcc.gnu.org/ml/gcc-help/2006-12/msg00279.html
> > What do you think?
>
> -----
> The values of the varaiables are,
> p->fname=/c/mingw/include cpp_PREFIX=c:/mingw cpp_PREFIX_len=8
> -----
>
> This is not at all what I expected. The problem here is that you are
> configuring mingw under cygwin, and the cygwin paths are not translated.
> I will have to think about this.
>
> Could you tell me what errors you get when using --prefix='c:/mingw'?
No, I'm not configuring mingw under cygwin. I'm configuring it in a
native mingw sh shell. Yeah, I tried C:/mingw, and that gives me lot's
Makefile errors. Is it a problem for the C:/ to be in the prefix for
Makefile targets?
I'll rebuild with that as the prefix and tell you what the problems are.
Bob Rossi
next prev parent reply other threads:[~2006-12-20 0:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-19 15:54 Bob Rossi
2006-12-19 22:32 ` Bob Rossi
2006-12-19 22:50 ` Carlos O'Donell
2006-12-19 22:59 ` Bob Rossi
2006-12-19 23:58 ` Carlos O'Donell
2006-12-20 0:24 ` Bob Rossi [this message]
2006-12-20 1:23 ` Carlos O'Donell
2006-12-20 1:56 ` Bob Rossi
2006-12-20 2:33 ` Carlos O'Donell
2006-12-19 23:47 ` Carlos O'Donell
2006-12-20 0:29 ` Bob Rossi
2006-12-20 1:45 ` Carlos O'Donell
2006-12-20 4:53 ` Bob Rossi
2006-12-20 17:24 ` Carlos O'Donell
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=20061220002415.GD3022@cox.net \
--to=bob_rossi@cox.net \
--cc=carlos@codesourcery.com \
--cc=gcc-help@gcc.gnu.org \
--cc=mark@codesourcery.com \
/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).