COLLECT_LTO_WRAPPER - declaration sys wide - where/how?

[lejeczek via gcc-help]

On 31/08/18 23:14, Jonathan Wakely wrote:
> On Fri, 31 Aug 2018 at 21:15, lejeczek <peljasz@yahoo.co.uk> wrote:
>>
>>
>> On 31/08/18 19:56, Jonathan Wakely wrote:
>>> On Fri, 31 Aug 2018 at 18:55, lejeczek via gcc-help
>>> <gcc-help@gcc.gnu.org> wrote:
>>>> hi guys
>>>>
>>>> I have cron which is supposed to update a few things which involves
>>>> compiler but it fails. I could find only one bit which is not there, but
>>>> which there for root when root does the same thing.
>>>>
>>>> Cron does not seem to get COLLECT_LTO_WRAPPER declared. And that is on
>>>> one box where a sister box's cron gets it okey.
>>>>
>>>> How to fix that? (I'm on Centos 7.5)
>>> You haven't said what the problem is.
>>>
>>> You need to tell us what you're trying to do and what the error you
>>> get is. Just saying it "involves compiler but it fails" is not enough
>>> for us to help.
>> could we just keep it simple for now?
> I'm trying to.
>
>> When as root in bash session I do:
>> ] gcc -v
>> Using built-in specs.
>> COLLECT_GCC=gcc
>> COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-redhat-linux/4.8.5/lto-wrapper
>> Target: x86_64-redhat-linux
>> ...
>> But when crond does the same then COLLECT_LTO_WRAPPER is not
>> there.
> That suggests you're looking at two different 'gcc' executables.
>
>> Is it possible to fix that first?
> You can't change that, it's baked in when GCC is built. It's not
> something that "cron gets declared".
>
> Why does it matter? Is the cron job trying to print the name of GCC's
> LTO wrapper? Are using using LTO? If not, why do you think that's the
> problem?
>
> What are you actually trying to do that fails? Tell us that, instead
> of what you think is wrong and needs to be fixed. That's an XY problem
> (https://en.wikipedia.org/wiki/XY_problem).

okey, so, in my case it was crond which ran with '-P' which cased the 
problem of crond not able to find gcc

thanks, L.