[Clfs-dev] configure: error: compiler support for visibility attribute is required

[Pierre Lorenzon]

From: Pierre Lorenzon <devel at pollock-nageoire.net>
Subject: Re: [Clfs-dev] configure: error: compiler support for visibility attribute is required
Date: Thu, 20 Dec 2012 10:45:24 +0100 (CET)

> 
> Hi,
> 
> From: Pierre Lorenzon <devel at pollock-nageoire.net>
> Subject: Re: [Clfs-dev] configure: error: compiler support for visibility attribute is required
> Date: Wed, 19 Dec 2012 15:10:28 +0100 (CET)
> 
>> 
>> Hi,
>> 
>> After investigating gcc code itself I discovered that the error
>> message I got appears when HAVE_GAS_HIDDEN is not defined. This
>> macro is likely to be defined at gcc configure stage. So I'll
>> investigate why it it is not set to TRUE or 1 of whatever not
>> ZERO !
> 
>   Welll it seems that state of this variable is determined by
>   detecting the linker. Unfortunatly the linker seems not to be
>   found on my system. Here is the relevant part of the
>   config.log found in gcc subdirectory in gcc-build.
> 
>   >>>  -- config.log 
> 
> configure:20896: checking for x86_64-unknown-linux-gnu-as
> configure:20914: found /cross-tools/bin/x86_64-unknown-linux-gnu-as
> configure:20926: result: /cross-tools/bin/x86_64-unknown-linux-gnu-as
> configure:20945: checking what assembler to use
> configure:20982: result: /cross-tools/bin/x86_64-unknown-linux-gnu-as
> configure:21017: checking for x86_64-unknown-linux-gnu-ld 
> configure:21050: result: no
> configure:21077: checking whether we are using gold
> configure:21086: result: no
> configure:21097: checking what linker to use
> configure:21122: result: 
> configure:21185: checking what nm to use
> configure:21193: result: /mnt/clfs/cross-tools/bin/../lib/gcc/x86_64-unknown-linux-gnu/4.6.0/../../../../x86_64-unknown-linux-gnu/bin/nm
> 
> 
>>>>  -- End config.log 

      And what looks more surprising to me is that as is found
      when it is located exactly at the same place and tests to
      find one or the other look very similar.

      Pierre



> 
>      At the moment I cannot understand why ld is not detected
>      even if the corresponding file exists in /cross-tools and
>      seems to be functional when trying to use it by passing a
>      --version oprtion for instance.
> 
>      Any advice would be appreciated !
> 
>      Regards 
> 
>      Pierre
> 
>> 
>> Regards
>> 
>> Pierre
>> 
>> 
>> 
>> From: Pierre Lorenzon <devel at pollock-nageoire.net>
>> Subject: Re: [Clfs-dev] configure: error: compiler support for visibility attribute is required
>> Date: Sat, 15 Dec 2012 14:33:39 +0100 (CET)
>> 
>>> 
>>> Hi,
>>> 
>>> After reading many things about ld problems with respect with
>>> the problem of visibility atribute I suspected binutils to be
>>> responsible for the fail. Unfortunately even when downgrading
>>> to binutils 2.21.1a the fail persists. So I should investigate
>>> further. But if anyone can give me a good advice it would be
>>> greatly appreciated !
>>> 
>>> 
>>> Regards 
>>> 
>>> Pierre
>>> 
>>> 
>>> 
>>> From: Pierre Lorenzon <devel at pollock-nageoire.net>
>>> Subject: Re: [Clfs-dev] configure: error: compiler support for visibility attribute is required
>>> Date: Tue, 11 Dec 2012 04:26:32 +0100 (CET)
>>> 
>>>> 
>>>> Hi William,
>>>> 
>>>> Thanks you for your answer :
>>>> 
>>>> From: William Harrington <berzerkula at cox.net>
>>>> Subject: Re: [Clfs-dev] configure: error: compiler support for visibility attribute is required
>>>> Date: Mon, 10 Dec 2012 14:56:15 -0600
>>>> 
>>>>> 
>>>>> On Dec 10, 2012, at 1:09 AM, Pierre Lorenzon wrote:
>>>>> 
>>>>>> checking whether __attribute__((visibility())) is
>>>>>> supported... no
>>>>>> configure: error: compiler support for visibility attribute is
>>>>>> required
>>>>> 
>>>>> Can you verify that your tools grep is linked to the
>>>>> interepreter in /tools?
>>>> 
>>>>   Sure I can and the output is :
>>>> 
>>>>   >>>  -- readelf 
>>>> 
>>>>       [Requesting program interpreter: /tools/lib64/ld-linux-x86-64.so.2]
>>>> 
>>>> 
>>>>   >>>  -- End readelf 
>>>> 
>>>> 
>>>>   It looks correct to me. In fact I did not know that grep
>>>>   could be responsible of this trouble. In the various thinkgs
>>>>   I read ld was most of the time the problem. But people were
>>>>   compiling on environment without gnu ld (solaris or things
>>>>   like that). In my situation I am in a complete gnu linux.
>>>> 
>>>> 
>>>>   Regards 
>>>> 
>>>>   Pierre
>>>>> 
>>>>> readelf -e /tools/bin/grep | grep interpreter
>>>>> 
>>>>> Sincerely,
>>>>> 
>>>>> William Harrington
>>>> _______________________________________________
>>>> Clfs-dev mailing list
>>>> Clfs-dev at lists.cross-lfs.org
>>>> http://lists.cross-lfs.org/listinfo.cgi/clfs-dev-cross-lfs.org
>>> _______________________________________________
>>> Clfs-dev mailing list
>>> Clfs-dev at lists.cross-lfs.org
>>> http://lists.cross-lfs.org/listinfo.cgi/clfs-dev-cross-lfs.org
>> _______________________________________________
>> Clfs-dev mailing list
>> Clfs-dev at lists.cross-lfs.org
>> http://lists.cross-lfs.org/listinfo.cgi/clfs-dev-cross-lfs.org
> _______________________________________________
> Clfs-dev mailing list
> Clfs-dev at lists.cross-lfs.org
> http://lists.cross-lfs.org/listinfo.cgi/clfs-dev-cross-lfs.org