Edward Diener
writes:
>> At the end, adapting your PATH setting works the best. Just a simple
>> .bat file solves the problem for those of us that need to constantly
>> experiment with multiple installs:
>>
>> @rem mingw-w64-492.bat
>> @PATH=path-to-the-bin-directory;%PATH%
>> @%*
>>
>>
>> Now in
On 6/21/2015 8:22 PM, Óscar Fuentes wrote:
> Yaron Keren
> writes:
>
>>> Why in the world should I have to put anything in my PATH if these
>>> releases are self-enclosed ? I am executing gcc from the exact same
>>> directory where the libwinpthread-1.dll exists.
>>
>> I misunderstood you, thought
Yaron Keren
writes:
>>Why in the world should I have to put anything in my PATH if these
>>releases are self-enclosed ? I am executing gcc from the exact same
>>directory where the libwinpthread-1.dll exists.
>
> I misunderstood you, thought you refer to running compiled apps not gcc.
>
> It's ve
>Why in the world should I have to put anything in my PATH if these
>releases are self-enclosed ? I am executing gcc from the exact same
>directory where the libwinpthread-1.dll exists.
I misunderstood you, thought you refer to running compiled apps not gcc.
It's very convenient to have the gcc b
On 21.06.2015 18:56, Edward Diener wrote:
> On 6/21/2015 7:45 AM, LRN wrote:
>> On 21.06.2015 5:44, John E. / TDM wrote:
>>> On 6/20/2015 8:25 PM, Edward Diener wrote:
Any timeframe for a gcc 5.1 release ? I noticed the latest mingw-64
install now has gcc-5.1, but it has the same hardcode
On 6/21/2015 12:03 PM, Yaron Keren wrote:
> >I still get errors because libwinpthread-1.dll cannot be found even
>
> The system PATH needs to include the directory where these DLLs are or
> you can copy them to the directory where the compiled application resides.
I appreciate the free mingw-64 r
>I still get errors because libwinpthread-1.dll cannot be found even
The system PATH needs to include the directory where these DLLs are or you
can copy them to the directory where the compiled application resides.
2015-06-21 18:28 GMT+03:00 Edward Diener :
> On 6/21/2015 2:28 AM, Yaron Keren
On 6/21/2015 7:45 AM, LRN wrote:
> On 21.06.2015 5:44, John E. / TDM wrote:
>> On 6/20/2015 8:25 PM, Edward Diener wrote:
>>> Any timeframe for a gcc 5.1 release ? I noticed the latest mingw-64
>>> install now has gcc-5.1, but it has the same hardcoded to c:\mingw
>>> limitation which my OP is abou
On 6/21/2015 09:32, Edward Diener wrote:
>> Furthermore, GCC typically comes with a distro's package manager (which
>> is expected to install to a fixed location) or built from source (with
>> the sysroot derived from the configure arguments). Neither has any
>> issues with hardcoded paths.
>>
>> O
On 6/21/2015 2:28 AM, Yaron Keren wrote:
> The mingw-builds distro uses relative paths had worked well in any
> install location for the past two years at least.
>
> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/
>
> It also includes
On 21.06.2015 5:44, John E. / TDM wrote:
> On 6/20/2015 8:25 PM, Edward Diener wrote:
>> Any timeframe for a gcc 5.1 release ? I noticed the latest mingw-64
>> install now has gcc-5.1, but it has the same hardcoded to c:\mingw
>> limitation which my OP is about.
>
> My experience in the past with
11 matches
Mail list logo
