Jonathan Dieter wrote:
On Fri, 2018-10-19 at 21:37 -0700, Josh Stone wrote:
> On 10/19/18 6:19 PM, Robert-André Mauchin wrote:
>> On samedi 20 octobre 2018 00:31:50 CEST Jonathan Dieter wrote:
>>> I'm trying to build duperemove[1] for epel7[2], and it's building on
>>> all the arches except aarch64.
>>>
>>> I'm BR'ing libatomic, but the error it gives in build.log[3] for
>>> aarch64 is:
>>> /usr/bin/ld: cannot find -latomic
>>>
>>> All current Fedora release builds were fine.
>>>
>>> I'm sure I'm missing something obvious, but does anyone have an idea
>>> what's going on?
>>>
>>
>> libatomic is 4.8.5 like the gcc version for other arches.
>> On aarch64, libatomic is 8.2.1 whereas gcc is still 4.8.5.
>> Maybe this causes some issues.
>
> For aarch64, libatomic comes from the gcc-libraries source package,
> which I believe only exists to provide runtime support for devtoolset.
> It does not have libatomic.so, only libatomic.so.1 and .so.1.2.0. You
> probably need to use devtoolset gcc to actually build+link it.
> (Were those SCLs ever enabled for EPEL?)
They were enabled in koji for EPEL-7. (In mock, they are
enabled for EPEL-6 as well.)
Ok, thanks for the explanation. Unless there's an easy
BuildRequires I
can add, I think I'll just leave duperemove out of EPEL.
An example of using devtoolset in a spec file is here:
http://smoogespace.blogspot.com/2018/03/using-red-hat-developer-toolset-d...
I don't know if that will work out easily for your situation
or not.
--
Todd
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The best leaders inspire by example. When that's not an option, brute
intimidation works pretty well, too.
-- Demotivators (
www.despair.com)