Re: Cannot find -latomic when building for epel7 aarch64

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sat, 2018-10-20 at 11:17 -0400, Todd Zullinger wrote:
> 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-too
> lset-dts-in.html
> 
> I don't know if that will work out easily for your situation
> or not.

Hi,

I had checked mock-core-config [1] , which are in use in copr (I guess)
and can't enable developer tools .
But on koji runs well , can you review this ? please .

I could build azureus [4] on koji [2] which need eclipse-swt , but not
on copr `Error: No Package found for rh-eclipse46-eclipse-swt >= 3.5` 
Unfortunately I didn't have much time to dig it ... 

Many thanks,

[1] 
https://github.com/rpm-software-management/mock/pull/222
[2]
https://koji.fedoraproject.org/koji/taskinfo?taskID=29875958
[3]
https://copr.fedorainfracloud.org/coprs/sergiomb/builds_for_Stable_Rele
ases/build/802448/ 
[4]
https://github.com/sergiomb2/azureus/commits/master
-- 
Sérgio M. B.
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux