public inbox for cygwin-talk@cygwin.com
 help / color / mirror / Atom feed
From: Vincent Richomme <forumer@smartmobili.com>
To: The Vulgar and Unprofessional Cygwin-Talk List <cygwin-talk@cygwin.com>
Subject: Re: [OT] Re: question about cygwin package
Date: Sat, 27 Feb 2010 21:49:00 -0000	[thread overview]
Message-ID: <b90bac7e6fa10d7e23a6c7a7e1f32ccf@mail.smartmobili.com> (raw)
In-Reply-To: <4B89904F.60305@gmail.com>

On Sat, 27 Feb 2010 21:36:15 +0000, Dave Korn
<dave.korn.cygwin@googlemail.com> wrote:
> On 27/02/2010 20:48, Vincent Richomme wrote:
>>> Add '-v' to see how gcc is using relative paths to look for cc1.exe
(and
>>> presumably failing).  
> 
>> $ gcc -v test.c
> 
>>  cc1 -quiet -v -iprefix
> 
>   Hmm, that means it has no idea at all where to find cc1.  So take a
look
>   at
> what "gcc -print-search-dirs" says for "programs:".
> 

programs:
=c:/developer/easymingw-devel/mingw32/bin/../libexec/gcc/i686-w64-min
w32/4.4.4/;c:/developer/easymingw-devel/mingw32/bin/../libexec/gcc/;/usr/libexe
/gcc/i686-w64-mingw32/4.4.4/;/usr/libexec/gcc/i686-w64-mingw32/;/usr/lib/gcc/i6
6-w64-mingw32/4.4.4/;/usr/lib/gcc/i686-w64-mingw32/;c:/developer/easymingw-deve
/mingw32/bin/../lib/gcc/i686-w64-mingw32/4.4.4/../../../../i686-w64-mingw32/bin
i686-w64-mingw32/4.4.4/;c:/developer/easymingw-devel/mingw32/bin/../lib/gcc/i68
-w64-mingw32/4.4.4/../../../../i686-w64-mingw32/bin/

Ok so now I understand why it doesn't work it searches inside
.../mingw32/bin/../libexec
but programs are in ../mingw32/bin/../usr/libexec
So I suppose my only choice is to keep using mingw logic.

Thanks

  reply	other threads:[~2010-02-27 21:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-27 20:48 Vincent Richomme
2010-02-27 21:18 ` Dave Korn
2010-02-27 21:49   ` Vincent Richomme [this message]
2010-02-28  0:39     ` Christopher Faylor
2010-02-28  0:54       ` Dave Korn

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=b90bac7e6fa10d7e23a6c7a7e1f32ccf@mail.smartmobili.com \
    --to=forumer@smartmobili.com \
    --cc=cygwin-talk@cygwin.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).