Re: [uclibc-ng-devel] uclibc with gcc 8.3.1

[Ata, John (US)]

Hi Waldemar,

Thanks for your reply. I believe RHEL/Centos 8 now uses gcc 8.3.1 
(https://centos.pkgs.org/8/centos-appstream-x86_64/gcc-8.3.1-4.5.el8.x86_64.rpm.html).
  However, I'm glad that 8.3.0 has been used successfully with uClibc-ng.  I'm 
having the usual porting problems (x86_64, 64 bit and 32 bit) upgrading from 
gcc 4.8.5).  So far, the biggest problem I'm having is with the sanitizer since 
the data structures from uClibc can be slightly different than glibc causing 
problems. Did you turn the sanitizer off in your build? Are there are buildroot 
patches for gcc 8.3 specific to uClibc that I might have missed?

Take care,
 
John Ata, CISSP
Senior Principal Software Engineer
Electronics Systems
STOP Operating System Software Development

T 703-563-8115 | F 703-668-4359 | john@baesystems.com
http://www.baesystems.com/csp


-Original Message-
From: Waldemar Brodkorb  
Sent: Thursday, February 27, 2020 7:43 AM
To: Ata, John (US) 
Cc: devel@uclibc-ng.org
Subject: Re: [uclibc-ng-devel] uclibc with gcc 8.3.1

*** WARNING ***
EXTERNAL EMAIL -- This message originates from outside our organization.


Hi John,
Ata, John  (US) wrote,

> Hi all,
> 
>  
> 
> Has anyone successfully created a toolchain with the latest uClibc and gcc
> 8.3.1?

What issues do you have?
gcc 8.3.0 is the latest release and I see no problems with it.

best regards
 Waldemar
___
devel mailing list
devel@uclibc-ng.org
https://mailman.uclibc-ng.org/cgi-bin/mailman/listinfo/devel

Re: [uclibc-ng-devel] uclibc with gcc 8.3.1

[Michael 'veremitz' Everitt]

On 22/02/20 19:56, Michael 'veremitz' Everitt wrote:
> On 22/02/20 01:21, Ata, John (US) wrote:
>>
>> Hi all,
>>
>>  
>>
>> Has anyone successfully created a toolchain with the latest uClibc and
>> gcc 8.3.1?
>>
>>  
>>
>> Thanks,
>>
>> 
>>
> Closest I have is:
>
> Using built-in specs.
> COLLECT_GCC=armv6zk-unknown-linux-uclibceabihf-gcc-8.3.0
> COLLECT_LTO_WRAPPER=/usr/libexec/gcc/armv6zk-unknown-linux-uclibceabihf/8.3.0/lto-wrapper
> Target: armv6zk-unknown-linux-uclibceabihf
> Configured with:
> /var/tmp/portage/cross-armv6zk-unknown-linux-uclibceabihf/gcc-8.3.0-r1/work/gcc-8.3.0/configure
> --host=x86_64-pc-linux-gnu --target=armv6zk-unknown-linux-uclibceabihf
> --build=x86_64-pc-linux-gnu --prefix=/usr
> --bindir=/usr/x86_64-pc-linux-gnu/armv6zk-unknown-linux-uclibceabihf/gcc-bin/8.3.0
> --includedir=/usr/lib/gcc/armv6zk-unknown-linux-uclibceabihf/8.3.0/include
> --datadir=/usr/share/gcc-data/armv6zk-unknown-linux-uclibceabihf/8.3.0
> --mandir=/usr/share/gcc-data/armv6zk-unknown-linux-uclibceabihf/8.3.0/man
> --infodir=/usr/share/gcc-data/armv6zk-unknown-linux-uclibceabihf/8.3.0/info
> --with-gxx-include-dir=/usr/lib/gcc/armv6zk-unknown-linux-uclibceabihf/8.3.0/include/g++-v8
> --with-python-dir=/share/gcc-data/armv6zk-unknown-linux-uclibceabihf/8.3.0/python
> --enable-languages=c,c++,fortran --enable-obsolete --enable-secureplt
> --disable-werror --with-system-zlib --enable-nls
> --without-included-gettext --enable-checking=release
> --with-bugurl=https://bugs.gentoo.org/ --with-pkgversion='Gentoo 8.3.0-r1
> p1.1' --disable-esp --enable-libstdcxx-time
> --enable-poison-system-directories
> --with-sysroot=/usr/armv6zk-unknown-linux-uclibceabihf
> --disable-bootstrap --disable-__cxa_atexit --enable-tls
> --disable-multilib --disable-altivec --disable-fixed-point
> --with-float=hard --with-arch=armv6zk --with-float=hard --with-fpu=vfp
> --enable-libgomp --disable-libmudflap --disable-libssp --disable-libmpx
> --disable-systemtap --disable-vtable-verify --disable-libvtv --enable-lto
> --without-isl --disable-libsanitizer --enable-default-pie
> --enable-default-ssp
> Thread model: posix
> gcc version 8.3.0 (Gentoo 8.3.0-r1 p1.1)
>
> uclibc-ng version is 1.0.31.
> But I am aware it's not generating good ARM executables because of
> another bug.
>
> http://distfiles.gentoo.org/releases/amd64/autobuilds/current-stage3-amd64-uclibc-vanilla/
> appears to have a functional x86_64 toolchain, unless I'm mistaken, but
> this is quite likely to have rolled over to gcc-9.2 now. We certainly
> would have had 8.3.0 if this build series has been continuous over the
> past year or so.
>
> Is it specifically 8.3._1_ you're having a problem with?
>
>
> ___
> devel mailing list
> devel@uclibc-ng.org
> https://mailman.uclibc-ng.org/cgi-bin/mailman/listinfo/devel
Sanity-checking, I can't actually find an 8.3.1 release anywhere .. there's
a new snapshot posted for gcc-8-20200221, and we're due 8.4 Soon, but I
can' t see anything official for 8.3.1 .. am I missing something?! :)
Cheers,
Michael.


signature.asc
Description: OpenPGP digital signature
___
devel mailing list
devel@uclibc-ng.org
https://mailman.uclibc-ng.org/cgi-bin/mailman/listinfo/devel

Re: [uclibc-ng-devel] uclibc with gcc 8.3.1

[Michael 'veremitz' Everitt]

On 22/02/20 01:21, Ata, John (US) wrote:
>
> Hi all,
>
>  
>
> Has anyone successfully created a toolchain with the latest uClibc and
> gcc 8.3.1?
>
>  
>
> Thanks,
>
> 
>
Closest I have is:

Using built-in specs.
COLLECT_GCC=armv6zk-unknown-linux-uclibceabihf-gcc-8.3.0
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/armv6zk-unknown-linux-uclibceabihf/8.3.0/lto-wrapper
Target: armv6zk-unknown-linux-uclibceabihf
Configured with:
/var/tmp/portage/cross-armv6zk-unknown-linux-uclibceabihf/gcc-8.3.0-r1/work/gcc-8.3.0/configure
--host=x86_64-pc-linux-gnu --target=armv6zk-unknown-linux-uclibceabihf
--build=x86_64-pc-linux-gnu --prefix=/usr
--bindir=/usr/x86_64-pc-linux-gnu/armv6zk-unknown-linux-uclibceabihf/gcc-bin/8.3.0
--includedir=/usr/lib/gcc/armv6zk-unknown-linux-uclibceabihf/8.3.0/include
--datadir=/usr/share/gcc-data/armv6zk-unknown-linux-uclibceabihf/8.3.0
--mandir=/usr/share/gcc-data/armv6zk-unknown-linux-uclibceabihf/8.3.0/man
--infodir=/usr/share/gcc-data/armv6zk-unknown-linux-uclibceabihf/8.3.0/info
--with-gxx-include-dir=/usr/lib/gcc/armv6zk-unknown-linux-uclibceabihf/8.3.0/include/g++-v8
--with-python-dir=/share/gcc-data/armv6zk-unknown-linux-uclibceabihf/8.3.0/python
--enable-languages=c,c++,fortran --enable-obsolete --enable-secureplt
--disable-werror --with-system-zlib --enable-nls --without-included-gettext
--enable-checking=release --with-bugurl=https://bugs.gentoo.org/
--with-pkgversion='Gentoo 8.3.0-r1 p1.1' --disable-esp
--enable-libstdcxx-time --enable-poison-system-directories
--with-sysroot=/usr/armv6zk-unknown-linux-uclibceabihf --disable-bootstrap
--disable-__cxa_atexit --enable-tls --disable-multilib --disable-altivec
--disable-fixed-point --with-float=hard --with-arch=armv6zk
--with-float=hard --with-fpu=vfp --enable-libgomp --disable-libmudflap
--disable-libssp --disable-libmpx --disable-systemtap
--disable-vtable-verify --disable-libvtv --enable-lto --without-isl
--disable-libsanitizer --enable-default-pie --enable-default-ssp
Thread model: posix
gcc version 8.3.0 (Gentoo 8.3.0-r1 p1.1)

uclibc-ng version is 1.0.31.
But I am aware it's not generating good ARM executables because of another bug.

http://distfiles.gentoo.org/releases/amd64/autobuilds/current-stage3-amd64-uclibc-vanilla/
appears to have a functional x86_64 toolchain, unless I'm mistaken, but
this is quite likely to have rolled over to gcc-9.2 now. We certainly would
have had 8.3.0 if this build series has been continuous over the past year
or so.

Is it specifically 8.3._1_ you're having a problem with?


signature.asc
Description: OpenPGP digital signature
___
devel mailing list
devel@uclibc-ng.org
https://mailman.uclibc-ng.org/cgi-bin/mailman/listinfo/devel

[uclibc-ng-devel] uclibc with gcc 8.3.1

[Ata, John (US)]

Hi all,

Has anyone successfully created a toolchain with the latest uClibc and gcc 
8.3.1?

Thanks,

John Ata, CISSP
Senior Principal Software Engineer
Electronics Systems
STOP Operating System Software 
Development

T 703-563-8115 | F 703-668-4359 | 
john@baesystems.com
http://www.baesystems.com/csp

[cid:image001.png@01D138BC.8E54E330][cid:image003.png@01D138BC.8E54E330][cid:image004.png@01D138BC.8E54E330][cid:image006.png@01D138BC.8E54E330]


___
devel mailing list
devel@uclibc-ng.org
https://mailman.uclibc-ng.org/cgi-bin/mailman/listinfo/devel