[OT] Re: question about cygwin package

[OT] Re: question about cygwin package

[Vincent Richomme]

> Add '-v' to see how gcc is using relative paths to look for cc1.exe (and
>presumably failing).  The relative layout of the various installed files
must
>match what was specified in the configure options for relocating an
>installation to work, bascially you have to move the entire thing
wholesale.
>
>[ Any further posts on this topic -> TITTTL.  Reply-to set. ]


$ gcc -v test.c
Using built-in specs.
Target: i686-w64-mingw32
Configured with: ../gcc44-svn/configure --host=i686-w64-mingw32
--target=i686-w6
4-mingw32 --disable-multilib --enable-checking=release --prefix=/mingw32
--with-
sysroot=/mingw32 --enable-languages=c,c++,fortran,objc,obj-c++
--with-gmp=/mingw
32 --with-mpfr=/mingw32 --disable-nls --disable-win32-registry
Thread model: win32
gcc version 4.4.4 20100212 (prerelease) [svn/rev.156740 - mingw-w64/oz]
(GCC)
COLLECT_GCC_OPTIONS='-v' '-mtune=generic'
 cc1 -quiet -v -iprefix
c:\developer\easymingw-devel\mingw32\bin\../lib/gcc/i686
-w64-mingw32/4.4.4/ -isysroot
c:\developer\easymingw-devel\mingw32\bin\../../min
gw32 test.c -quiet -dumpbase test.c -mtune=generic -auxbase test -version
-o C:\
DOCUME~1\Vincent\LOCALS~1\Temp\ccREMxQF.s
gcc.exe: CreateProcess: No such file or directory

$ mount
C:\Developer\EasyMingw-devel\mingw32\bin on /mingw32/usr/bin type user
(binmode)
C:\Developer\EasyMingw-devel\mingw32\lib on /mingw32/usr/lib type user
(binmode)
C:\DOCUME~1\Vincent\LOCALS~1\Temp on /tmp type user (binmode,noumount)
C:\Developer\EasyMingw-devel\etc on /mingw32/etc type user (binmode)
C:\Developer\EasyMingw-devel on / type user (binmode,noumount)
C:\Developer\EasyMingw-devel on /usr type user (binmode,noumount)
a: on /a type user (binmode,noumount)
c: on /c type user (binmode,noumount)
d: on /d type user (binmode,noumount)
e: on /e type user (binmode,noumount)
h: on /h type user (binmode,noumount)

Vincent@gynoid /mingw32
$ find . -maxdepth 2 -type d
.
./bin
./lib
./lib/gcc
./tmp
./tmp/usr
./usr
./usr/i686-w64-mingw32
./usr/include
./usr/info
./usr/lib32
./usr/libexec
./usr/man
./usr/mingw
./usr/share

I have no idea of what is going wrong, I would say a msys bug(or maybe I
should say a feature) ... 

Re: [OT] Re: question about cygwin package

[Dave Korn]

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:".

    cheers,
      DaveK

Re: [OT] Re: question about cygwin package

[Vincent Richomme]

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

Re: [OT] Re: question about cygwin package

[Christopher Faylor]

On Sat, Feb 27, 2010 at 10:48:50PM +0100, Vincent Richomme wrote:
>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.

I don't think this discussion is even appropriate for the cygwin-talk
list.  While msys may be somewhat related to cygwin, I have to draw the
line at discussions about msys and mingw here.

If you're having msys or mingw issues there are much better mailing lists
to use than ones with the word "cygwin" in them.

cgf

Re: [OT] Re: question about cygwin package

[Dave Korn]

On 28/02/2010 00:39, Christopher Faylor wrote:
> On Sat, Feb 27, 2010 at 10:48:50PM +0100, Vincent Richomme wrote:
>> On Sat, 27 Feb 2010 21:36:15 +0000, Dave Korn 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.
> 
> I don't think this discussion is even appropriate for the cygwin-talk
> list.  While msys may be somewhat related to cygwin, I have to draw the
> line at discussions about msys and mingw here.
> 
> If you're having msys or mingw issues there are much better mailing lists
> to use than ones with the word "cygwin" in them.
> 
> cgf


 *goes off to write steganography program that encodes hidden messages in
minor variants in spelling, spacing, word-ordering and punctuation of hippo jokes*

    cheers,
      DaveK