Re: [Mingw-w64-public] The compilation of the cross compiler is failing but I'm not sure as to why.

[Geoff H. <geo...@t-...>]

On 07/07/2011 5:14 PM, Geoff Hilton wrote:
> On 07/07/2011 4:49 PM, Ruben Van Boxem wrote:
>> 2011/7/7 Geoff Hilton<geo...@t-...>:
>>> Hi, I signed up to the mailing list to ask if someone here could please
>>> assist me with a problem I'm currently having with building a cross
>>> compiler, the link with more information is below.
>>>
>>> Thanks very much for any help you can provide.
>>
>> Sorry to be so short in words, but you should add /usr/local/bin to
>> PATH and try a clean reconfigure. I believe configure is trying to use
>> the wrong executables (in the x86_64-w64-mingw32/bin directory, which
>> should not be called directly). This will allow for the proper tools
>> to be used.
>>
>> If you just want a working cross-compiler built and are tired of
>> trying, try my source package:
>> http://sourceforge.net/projects/mingw-w64/files/Toolchain%20sources/Personal%20Builds/rubenvb/
>>
>> Unzip the latest one, modify the first lines of buildmingw64.sh:
>> export HOST=i686-w64-mingw32
>> export TARGET=x86_64-w64-mingw32
>> export BUILD=i686-w64-mingw32
>>
>> and use my 32-bit toolchain from
>> sourceforge.net/projects/mingw-w64/files/Toolchains targetting
>> Win32/Personal Builds/rubenvb/
>>
>> to rule out any external factors. Add mingw32/bin to PATH, and run
>> ./buildmingw64.sh from the main directory where you unzipped the
>> source package.
>>
>> PS: Also feel free to modify scripts/common.sh
>> GCC_LANGUAGES: remove what you don't need
>> BUILD_CFLAGS: the -mtune parameter: either keep or modify to something
>> better suited to your system
>>
>> Hope this helps!
>>
>> ------------------------------------------------------------------------------
>> All of the data generated in your IT infrastructure is seriously valuable.
>> Why? It contains a definitive record of application performance, security
>> threats, fraudulent activity, and more. Splunk takes this data and makes
>> sense of it. IT sense. And common sense.
>> http://p.sf.net/sfu/splunk-d2d-c2
>
> I may end up doing exactly as you propose, though I'd also like to see
> if I can fix the problem I was having so that I might at least learn
> something and not feel as though time ended up getting wasted. :S
> I'll try rebuilding with the /usr/local/bin/ on my path. In windows
> terms (ie outside the shell) that would be C:\MinGW\msys\1.0\local\bin,
> right (starting from an ordinary install of mingw/msys)?
>
>
> ------------------------------------------------------------------------------
> All of the data generated in your IT infrastructure is seriously valuable.
> Why? It contains a definitive record of application performance, security
> threats, fraudulent activity, and more. Splunk takes this data and makes
> sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-d2d-c2


It seems that despite my adding C:\MinGW\msys\1.0\local\bin 
(/usr/local/bin?) to the path it still picks what I understand you're 
saying is the wrong location for some of the files (ar, as, dlltool, etc).

C:\MinGW\bin is in the path and contains these files as well, in fact 
C:\MinGW\bin has always been in the path environment variable.. mind you 
I'm working off limited knowledge here, but I do find it rather odd that 
these weren't selected right away.

Meanwhile in C:\MinGW\msys\1.0\local\bin there are files such as the 
i686-pc-mingw32-gcc.exe and x86_64-w64-mingw32-ar.exe, 
x86_64-w64-mingw32-as.exe, x86_64-w64-mingw32-dlltool.exe, etc. (naming 
off possibly distinctive filenames at random in case it helps get a 
frame of reference as to what's what...