Re: [pam_radius] aarch64 GCC failures during ./configure's working compiler step?

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

 



On Mon, Jul 27, 2020 at 1:19 PM Alex Scheel <ascheel@xxxxxxxxxx> wrote:
>
> Not to pile on to what seems like a common topic... :-)
>
> Koschei notified me that one of my co-owned packages, pam_radius failed
> to build on aarch64 with the recent gcc update (10.1.1 -> 10.2.1). ppc and
> x86 built just fine.
>
> Looking at the build log, I'm almost inclined to kick off a new build
> on aarch64 to see if it is still there, or just issued at the wrong
> time:

Try a new scratch and see if the problem persists, it seems very
similar to some issues that should now be resolved.

Peter

> https://kojipkgs.fedoraproject.org/work/tasks/8159/47858159/build.log
>
> > + ./configure --build=aarch64-redhat-linux-gnu --host=aarch64-redhat-linux-gnu --program-prefix= --disable-dependency-tracking --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc --datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib64 --libexecdir=/usr/libexec --localstatedir=/var --sharedstatedir=/var/lib --mandir=/usr/share/man --infodir=/usr/share/info --enable-werror
> > configure: WARNING: unrecognized options: --disable-dependency-tracking
> > checking build system type... aarch64-redhat-linux-gnu
> > checking host system type... aarch64-redhat-linux-gnu
> > checking target system type... aarch64-redhat-linux-gnu
> > checking for aarch64-redhat-linux-gnu-gcc... gcc
> > checking whether the C compiler works... no
> > configure: error: in `/builddir/build/BUILD/pam_radius-1.4.0':
> > configure: error: C compiler cannot create executables
> > See `config.log' for more details
> > error: Bad exit status from /var/tmp/rpm-tmp.McMZL0 (%build)
> >     Bad exit status from /var/tmp/rpm-tmp.McMZL0 (%build)
> > RPM build errors:
> > Child return code was: 1
>
> The spec file was well before my time but seems fairly straight
> forward:
>
> https://src.fedoraproject.org/rpms/pam_radius/blob/master/f/pam_radius.spec#_43
>
>
> The configure script is admittedly from 7 years ago, perhaps I should
> just nuke it and rebuild it from configure.ac with a newer version of
> autotools?
>
> https://github.com/FreeRADIUS/pam_radius/blob/release_1_4_0/configure
>
>
> Any thoughts? Should I try and grab the config.log from a scratch build?
>
>
> Thanks!
>
> - Alex
> _______________________________________________
> devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
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