This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Cross-build for x86_64-pc-mingw32

From: NightStrike <nightstrike at gmail dot com>
To: "FX Coudert" <fxcoudert at gmail dot com>
Cc: tprince at computer dot org, gcc-help at gcc dot gnu dot org, mingw-w64-public at lists dot sourceforge dot net
Date: Sun, 2 Dec 2007 12:23:42 -0500
Subject: Re: Cross-build for x86_64-pc-mingw32
References: <19c433eb0711300950r43f1ccffi28ef6b7a2e51548d@mail.gmail.com> <b609cb3b0711301053g178ed7c7pb7f225f3579a4591@mail.gmail.com> <15BB3B75-14C5-4E4E-8C44-EBD567E70A79@gmail.com> <47519B7A.C4E7AC23@dessent.net> <57AF140A-DB8A-4A06-9927-1CE74793959C@gmail.com> <4751c936.073a360a.4d2f.ffffd1bfSMTPIN_ADDED@mx.google.com> <E21309FE-9106-42DC-9548-179243000A71@gmail.com>

On 12/1/07, FX Coudert <fxcoudert@gmail.com> wrote:
> > Don't linux x86-64 builds of gcc look for 64-bit support in lib64/
> > and 32-bit in lib/ ?  It looks reasonable to me to follow the same
> > plan.
>
> All linux distros except Debian-based ones, IIRC. I think that, since
> current mingw32 has libs in lib/, it would be better to have lib64/
> and lib/.

This is easy enough to do in terms of editing the automake file.  What
is necessary in terms of modifying gcc itself to search those places?

Follow-Ups:
- Re: Cross-build for x86_64-pc-mingw32
  - From: FX Coudert

References:
- Cross-build for x86_64-pc-mingw32
  - From: FX Coudert
- Re: Cross-build for x86_64-pc-mingw32
  - From: Brian Dessent
- Re: Cross-build for x86_64-pc-mingw32
  - From: FX Coudert
- Re: Cross-build for x86_64-pc-mingw32
  - From: FX Coudert

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]