2015-06-23 9:31 GMT+02:00 Alexpux <alex...@gmail.com>:
>
> 23 июня 2015 г., в 10:22, Ruben Van Boxem <vanboxem.ru...@gmail.com>
> написал(а):
>
>
>
> 2015-06-23 2:17 GMT+02:00 Óscar Fuentes <o...@wanadoo.es>:
>
>>
>> So moving cc1plus.exe to `bin' makes the toolchain "self contained", but
>> it is no solution as soon as you try to execute the programs you created
>> with that toolchain.
>>
>
>
>
> Let me just jump in here and add an extra data point to the discussion: I
> had a user once ask me about Eclipse and my toolchains, where Eclipse was
> calling the compiler with a fully qualified path and didn't add th
> toolchain directory to PATH. To solve this, I built the toolchain with
> -static, as to make sure all compiler executables were self-contained. To
> do this, I added LDFLAGS="-static" to GCC configure. This worked great.
>
> I cannot seem to find this flag in MinGW-builds' scripts though. Perhaps
> it is worth adding to solve this issue in a graceful way.
>
>
> I’m not build GCC using ming-builds scripts for a year, but as I remember
> this option can build static GCC:
> https://github.com/niXman/mingw-builds/blob/master/build#L64
>
That builds the GCC runtime statically, not the compiler executables:
https://github.com/niXman/mingw-builds/blob/develop/library/config.sh#L80
There doesn't seem to be an option to add "-static" to GCC's LDFLAGS
currently.
Ruben
------------------------------------------------------------------------------
Monitor 25 network devices or servers for free with OpManager!
OpManager is web-based network management software that monitors
network devices and physical & virtual servers, alerts via email & sms
for fault. Monitor 25 devices for free with no restriction. Download now
http://ad.doubleclick.net/ddm/clk/292181274;119417398;o
_______________________________________________
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
