On Thu, Apr 22, 2010 at 5:33 AM, Sisyphus wrote:
>
> - Original Message - From: "NightStrike"
> To: "Doug Semler"
>
>>> LIBRARY_PATH is ignored in cross compilers.
>
>>
>> The toolchain in question is host=win32 target=win64. So it is meant
>> to cross compile from a 32-bit windows gene
- Original Message -
From: "NightStrike"
To: "Doug Semler"
>> LIBRARY_PATH is ignored in cross compilers.
>
> The toolchain in question is host=win32 target=win64. So it is meant
> to cross compile from a 32-bit windows generating binaries for a
> 64-bit windows. It just so happens
On Wed, Apr 21, 2010 at 3:30 PM, NightStrike wrote:
> On Wed, Apr 21, 2010 at 11:41 AM, Doug Semler wrote:
>> Well, it looks like the compiler may be being built with host !=
>> target... In other words it wasn't bootstrapped and has been
>> configured as a cross compiler...
>>
>> LIBRARY_PATH is
Sisyphus писал в своём
письме Mon, 19 Apr 2010 04:06:11 +0500:
>
> Is there some other way of adding C:/_64/msys/1.0/local/lib to the
> default
> library search path so that I can avoid using the -L switch all the time
> ?
>
You can use spec file magic: http://www.mingw.org/wiki/SpecsFileH
On Wed, Apr 21, 2010 at 11:41 AM, Doug Semler wrote:
> Well, it looks like the compiler may be being built with host !=
> target... In other words it wasn't bootstrapped and has been
> configured as a cross compiler...
>
> LIBRARY_PATH is ignored in cross compilers.
That's because it is a cross c
On Wed, Apr 21, 2010 at 6:05 AM, Sisyphus wrote:
>
> - Original Message - From: "Doug Semler"
> To: "Sisyphus"
> Cc: "mingw64"
> Sent: Wednesday, April 21, 2010 2:45 AM
> Subject: Re: [Mingw-w64-public] [Repost] LIBRARY_PATH environment v
- Original Message -
From: "Doug Semler"
To: "Sisyphus"
Cc: "mingw64"
Sent: Wednesday, April 21, 2010 2:45 AM
Subject: Re: [Mingw-w64-public] [Repost] LIBRARY_PATH environment variable
not honoured.
Oops, should have qualified that - i meant th
Monday, April 19, 2010 10:30 PM
> Subject: Re: [Mingw-w64-public] [Repost] LIBRARY_PATH environment variable
> not honoured.
>
>
>> Can you post the output of gcc -v so I can see what the search path
>> actually ends up being on that link attempt ( without the -L param
>> that
- Original Message -
From: "Doug Semler"
To: "Sisyphus"
Cc: "mingw64"
Sent: Monday, April 19, 2010 10:30 PM
Subject: Re: [Mingw-w64-public] [Repost] LIBRARY_PATH environment variable
not honoured.
Can you post the output of gcc -v so I can see what
Can you post the output of gcc -v so I can see what the search path
actually ends up being on that link attempt ( without the -L param
that is).
Thx
On Sunday, April 18, 2010, Sisyphus wrote:
>
> - Original Message - From: "Doug Semler"
>
>
> With mingw64, is there currently some way I
- Original Message -
From: "Doug Semler"
>> With mingw64, is there currently some way I can avoid having to use
>> the -L
>> switch in relation to libraries in that location ?
>> If not, are there any plans to introduce such a feature ?
> This is an environment/gcc thing, and not a min
On Sun, 18 Apr 2010 10:52:26 Sisyphus wrote:
> Hi,
>
> I asked about this on 14 Oct last year
> (http://sourceforge.net/mailarchive/forum.php?thread_name=A00A469F7EBE44199
> 92A92CBC29D03F5%40desktop2&forum_name=mingw-w64-public) and didn't get any
> replies - so I thought I'd ask again and see wh
Hi,
I asked about this on 14 Oct last year
(http://sourceforge.net/mailarchive/forum.php?thread_name=A00A469F7EBE4419992A92CBC29D03F5%40desktop2&forum_name=mingw-w64-public)
and didn't get any replies - so I thought I'd ask again and see what
information I can glean this time.
With mingw32 (fr
13 matches
Mail list logo
