On 7/17/2018 2:55 PM, NightStrike wrote:
> On Tue, Jul 17, 2018 at 11:52 AM, Paul Eggert wrote:
>> On 07/16/2018 08:11 PM, NightStrike wrote:
>>>
>>> Is there a way to tell configure to pipe input into gcc as stdin for
>>> compile tests instead of writing out a temp file and compiling that?
>>
>>
NightStrike wrote:
In my environment, I don't have permission to run the build in a non-NFS area.
Even /tmp lives in NFS? Wow. Well, good luck.
___
Autoconf mailing list
Autoconf@gnu.org
https://lists.gnu.org/mailman/listinfo/autoconf
On Tue, Jul 17, 2018 at 11:52 AM, Paul Eggert wrote:
> On 07/16/2018 08:11 PM, NightStrike wrote:
>>
>> Is there a way to tell configure to pipe input into gcc as stdin for
>> compile tests instead of writing out a temp file and compiling that?
>
>
> Not that I know of.
>
>> When working on slow,
On 07/16/2018 08:11 PM, NightStrike wrote:
Is there a way to tell configure to pipe input into gcc as stdin for
compile tests instead of writing out a temp file and compiling that?
Not that I know of.
When working on slow, remotely mounted nfs areas, the very large
amount of file i/o latency
Is there a way to tell configure to pipe input into gcc as stdin for
compile tests instead of writing out a temp file and compiling that?
When working on slow, remotely mounted nfs areas, the very large
amount of file i/o latency multiplies its effects considerably.
