On Thu, Sep 9, 2010 at 12:09 PM, John E. / TDM wrote:
> On 9/8/2010 9:43 PM, Xiaofan Chen wrote:
>> I see. This makes sense. However, TDM64 does use "gcc", under
>> 32bit or 64bit Windows. I think it is a cross-compiler as well.
>
> No, TDM64 GCC is a native x86_64-w64-mingw32 compiler -- in othe
On 9/8/2010 9:43 PM, Xiaofan Chen wrote:
> I see. This makes sense. However, TDM64 does use "gcc", under
> 32bit or 64bit Windows. I think it is a cross-compiler as well.
No, TDM64 GCC is a native x86_64-w64-mingw32 compiler -- in other words,
it runs under Windows 64-bit and targets (by defaul
On Thu, Sep 9, 2010 at 11:11 AM, JonY wrote:
>> Can this be fixed and lib64 directory be removed?
>>
> If you have moved them and lib64 becomes empty, yes.
Move them to lib, right? What are the use of those files?
>> Another thing, typically other MinGW-w64 binaries for Windows
>> will have gcc
On 9/9/2010 08:00, Xiaofan Chen wrote:
> On Tue, Sep 7, 2010 at 8:00 PM, Xiaofan Chen wrote:
>> On Tue, Sep 7, 2010 at 10:36 AM, JonY wrote:
>>>
>>> Ok, to clear everything up, for non-multilib 4.6, you should only have
>>> "lib", "lib64" only if you have non-multilib 4.5.
>>>
>>
>> It seems the
On Tue, Sep 7, 2010 at 8:00 PM, Xiaofan Chen wrote:
> On Tue, Sep 7, 2010 at 10:36 AM, JonY wrote:
>>
>> Ok, to clear everything up, for non-multilib 4.6, you should only have
>> "lib", "lib64" only if you have non-multilib 4.5.
>>
>
> It seems the latest automatic build version still has the sam
On Tue, Sep 7, 2010 at 8:00 PM, Xiaofan Chen wrote:
> On Tue, Sep 7, 2010 at 10:36 AM, JonY wrote:
>>
>> Ok, to clear everything up, for non-multilib 4.6, you should only have
>> "lib", "lib64" only if you have non-multilib 4.5.
>>
>
> It seems the latest automatic build version still has the sam
On Tue, Sep 7, 2010 at 10:36 AM, JonY wrote:
>
> Ok, to clear everything up, for non-multilib 4.6, you should only have
> "lib", "lib64" only if you have non-multilib 4.5.
>
It seems the latest automatic build version still has the same issue
as previous versions, I just checked the following one
On 9/7/2010 10:07, Xiaofan Chen wrote:
> On Tue, Sep 7, 2010 at 9:40 AM, JonY wrote:
>> I think I can see where the problem is, but I'm still guessing at this
>> point.
>>
>> TDM multilib has lib and lib32, but your non-multilib has lib and lib64, and
>> they are not linked. I suppose the fix is t
On 9/6/2010 8:05 PM, Xiaofan Chen wrote:
> Sorry I am not a compiler expert here. What is the difference between a
> multilib x86_64-w64-mingw32 compiler and a multilib i686-w64-mingw32
> compiler?
One defaults to the 32-bit target (i686-w64-mingw32), and the other
defaults to the 64-bit target
On Tue, Sep 7, 2010 at 9:40 AM, JonY wrote:
> I think I can see where the problem is, but I'm still guessing at this
> point.
>
> TDM multilib has lib and lib32, but your non-multilib has lib and lib64, and
> they are not linked. I suppose the fix is to move all the contents in lib
> (or lib64) to
On Mon, Sep 6, 2010 at 11:15 PM, John E. / TDM wrote:
> It is correct that TDM64 GCC does not include a "lib64" directory of any
> sort (symlink or copy). I've simply never found it necessary when building
> GCC or any of the other software I build on a regular basis.
>
> Since GCC searches the "
On 9/6/2010 21:13, Kai Tietz wrote:
> 2010/9/6 Xiaofan Chen:
>> On Mon, Sep 6, 2010 at 7:26 PM, JonY wrote:
>>> Are you using a multilib setup? There should not be a lib64 directory around
>>> for non-multilib toolchains.
>>>
>>> If you are using a multilib setup, lib is where the arch default lib
On 9/7/2010 09:37, Xiaofan Chen wrote:
> On Tue, Sep 7, 2010 at 8:12 AM, JonY wrote:
>>> My problem is that libtool was pointing to lib64 directory in the 64bit
>>> cross build (under Linux or 32bit Windows) cases. I need to check again
>>> under 32bit Win 7 with TDM.
>>>
>>> I just checked under
On Tue, Sep 7, 2010 at 8:12 AM, JonY wrote:
>> My problem is that libtool was pointing to lib64 directory in the 64bit
>> cross build (under Linux or 32bit Windows) cases. I need to check again
>> under 32bit Win 7 with TDM.
>>
>> I just checked under Windows 7 64bit and TDM64 is okay there
>> wit
On 9/7/2010 07:53, Xiaofan Chen wrote:
> On Mon, Sep 6, 2010 at 11:15 PM, John E.> wrote:
>
>> It is correct that TDM64 GCC does not include a "lib64" directory of any
>> sort (symlink or copy). I've simply never found it necessary when building
>> GCC or any of the other software I build on a reg
On Mon, Sep 6, 2010 at 11:15 PM, John E. / TDM wrote:
> It is correct that TDM64 GCC does not include a "lib64" directory of any
> sort (symlink or copy). I've simply never found it necessary when building
> GCC or any of the other software I build on a regular basis.
>
> Since GCC searches the "
On 9/6/2010 8:49 AM, JonY wrote:
> On 9/6/2010 19:40, Xiaofan Chen wrote:
>> On Mon, Sep 6, 2010 at 7:26 PM, JonY wrote:
>>> Are you using a multilib setup? There should not be a lib64 directory around
>>> for non-multilib toolchains.
>> I also just tried TDM64 and it does not have lib64 direct
On 9/6/2010 19:40, Xiaofan Chen wrote:
> On Mon, Sep 6, 2010 at 7:26 PM, JonY wrote:
>> Are you using a multilib setup? There should not be a lib64 directory around
>> for non-multilib toolchains.
>
> I have tried different binary downloads. The one from MinGW-w64 Sourceforge
> site and the one fr
2010/9/6 Xiaofan Chen :
> On Mon, Sep 6, 2010 at 7:26 PM, JonY wrote:
>> Are you using a multilib setup? There should not be a lib64 directory around
>> for non-multilib toolchains.
>>
>> If you are using a multilib setup, lib is where the arch default libraries
>> are. For x86_64-w64-mingw32, lib
On Mon, Sep 6, 2010 at 7:26 PM, JonY wrote:
> Are you using a multilib setup? There should not be a lib64 directory around
> for non-multilib toolchains.
>
> If you are using a multilib setup, lib is where the arch default libraries
> are. For x86_64-w64-mingw32, lib points to lib64.
>
BTW, for T
On Mon, Sep 6, 2010 at 7:26 PM, JonY wrote:
> Are you using a multilib setup? There should not be a lib64 directory around
> for non-multilib toolchains.
I have tried different binary downloads. The one from MinGW-w64 Sourceforge
site and the one from http://www.drangon.org/mingw/ both are not
mu
On 9/6/2010 19:01, Xiaofan Chen wrote:
> Last time we had some discussions in the libusb mailing list about
> using MinGW-w64 to build 64bit libusb-1.0 Windows backend.
>
> http://libusb.6.n5.nabble.com/PATCH-28-37-core-now-references-windows-backend-td8410i80.html#a1046006
>
> One issue we found i
Last time we had some discussions in the libusb mailing list about
using MinGW-w64 to build 64bit libusb-1.0 Windows backend.
http://libusb.6.n5.nabble.com/PATCH-28-37-core-now-references-windows-backend-td8410i80.html#a1046006
One issue we found is that recent version of libtool is needed
to rec
23 matches
Mail list logo
