[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [avr-libc-dev] How attached are people to the implementation of rand
From: |
George Spelvin |
Subject: |
Re: [avr-libc-dev] How attached are people to the implementation of rand()/random()? |
Date: |
6 Dec 2016 15:20:40 -0500 |
> Either Debian is running patches atop GNU, or avr-libc test suite has
> not been adjusted to factor out different gcc versions.
The Debian diffs can be found in the right-hand column of
https://packages.debian.org/sid/gcc-avr
specifically
http://http.debian.net/debian/pool/main/g/gcc-avr/gcc-avr_4.9.2+Atmel3.5.3-1.diff.gz
They do disable the documentation, to prevent conflicts with other GCC
versions, and there are a couple of small patches that look like bugfixes
(one is documented as allowing building with GCC 6), but I don't see much.
The ./configure arguments are
CONFARGS = -v \
--enable-languages=c,c++ \
--prefix=/usr/lib \
--infodir=/usr/share/info \
--mandir=/usr/share/man \
--bindir=/usr/bin \
--libexecdir=/usr/lib \
--libdir=/usr/lib \
--enable-shared \
--with-system-zlib \
--enable-long-long \
--enable-nls \
--without-included-gettext \
--disable-libssp \
--build=$(DEB_BUILD_GNU_TYPE) \
--host=$(DEB_HOST_GNU_TYPE) \
--target=$(TARGET) \
$(shell dpkg-buildflags --export=configure | sed -e
's/-Werror=format-security//g')
> Presumably, someone adds this option by hand, because if avr-gcc
> added it the error message would be "ld: cannot find -latmega128".
That is indeed what runtest.sh does. Here's the result of "bash -x
./runtest.sh -s".
The actual compiler invocation is the tenth last line.
+ set -e
+ myname=./runtest.sh
+ : avr-gcc
+ : avr-nm
+ : avr-objcopy
+ : simulavr
+ : ../..
+ : atmega128 at90s8515
+ : atmega128 at90s2313 at90s4414 at90s8515 atmega8 atmega16
+ HOST_PASS=
+ HOST_ONLY=
+ MAKE_ONLY=
+ FLAG_STOP=
+ FLAG_KEEPCORE=
+ getopts a:icg:ktTsh opt
+ case $opt in
+ FLAG_STOP=1
+ getopts a:icg:ktTsh opt
+ shift 1
+ test_list='time/*.c regression/*.c stdlib/*.c string/*.c pmstring/*.c
printf/*.c scanf/*.c fplib/*.c math/*.c other/*.c
avr/*.[cS]'
+ CPPFLAGS='-Wundef -I.'
+ CFLAGS='-gdwarf-4 -W -Wall -pipe -Os'
+ CORE=core_avr_dump.core
+ HOST_CC=gcc
+ HOST_CFLAGS='-W -Wall -std=gnu99 -pipe -O2 -I.'
+ n_files=0
+ n_emake=0
+ n_ehost=0
+ n_esimul=0
+ for test_file in $test_list
+ case `basename $test_file` in
++ basename time/aux.c
+ n_files=1
++ basename time/aux.c .c
+ rootname=aux
+ '[' ']'
+ '[' -z ']'
+ case $rootname in
+ prlist=PR_STD
+ case `dirname $test_file` in
++ dirname time/aux.c
+ mcu_list='atmega128 at90s8515'
+ elf_file=aux.elf
+ for prvers in $prlist
+ for mcu in $mcu_list
+ echo -n 'Simulate: time/aux.c '
Simulate: time/aux.c + case $prvers in
+ echo -n 'atmega128 ... '
atmega128 ... + Compile time/aux.c atmega128 aux.elf PR_STD
+ local crt=
+ local libs=
+ local flags=
+ '[' -z ../.. ']'
++ avr-gcc -mmcu=atmega128 -print-multi-directory
+ local multilibdir=avr51
+ [[ avr51 != \a\v\r* ]]
+ crt=crtatmega128.o
+ flags='-isystem ../../include -nostdlib'
++ find ../../avr/lib -name crtatmega128.o -print
++ head -1
+ crt=
+ libs='../../avr/lib/avr51/libc.a ../../avr/lib/avr51/libm.a
../../avr/lib/avr51/atmega128/libatmega128.a -lgcc'
+ case $4 in
+ case `basename $1` in
++ basename time/aux.c
+ flags='-isystem ../../include -nostdlib -std=gnu99'
+ avr-gcc -Wundef -I. -gdwarf-4 -W -Wall -pipe -Os -isystem ../../include
-nostdlib -std=gnu99 -mmcu=atmega128 -o aux.elf time/aux.c
../../avr/lib/avr51/libc.a ../../avr/lib/avr51/libm.a
../../avr/lib/avr51/atmega128/libatmega128.a -lgcc
avr-gcc: error: ../../avr/lib/avr51/atmega128/libatmega128.a: No such file or
directory
+ Err_echo 'compile failed'
+ echo '*** compile failed'
*** compile failed
+ '[' 1 ']'
+ Errx Stop
+ echo './runtest.sh: Stop'
./runtest.sh: Stop
+ exit 1
- [avr-libc-dev] How attached are people to the implementation of rand()/random()?, George Spelvin, 2016/12/06
- Re: [avr-libc-dev] How attached are people to the implementation of rand()/random()?, Joerg Wunsch, 2016/12/06
- Re: [avr-libc-dev] How attached are people to the implementation of rand()/random()?, George Spelvin, 2016/12/06
- Re: [avr-libc-dev] How attached are people to the implementation of rand()/random()?, Georg-Johann Lay, 2016/12/06
- Re: [avr-libc-dev] How attached are people to the implementation of rand()/random()?, George Spelvin, 2016/12/06
- Re: [avr-libc-dev] How attached are people to the implementation of rand()/random()?, Georg-Johann Lay, 2016/12/06
- Re: [avr-libc-dev] How attached are people to the implementation of rand()/random()?,
George Spelvin <=
- Re: [avr-libc-dev] How attached are people to the implementation of rand()/random()?, Georg-Johann Lay, 2016/12/06
- Re: [avr-libc-dev] Testsuite (Was: How attached are people ...), Joerg Wunsch, 2016/12/06
- Re: [avr-libc-dev] Testsuite (Was: How attached are people ...), Joerg Wunsch, 2016/12/06
- Re: [avr-libc-dev] Testsuite (Was: How attached are people ...), Georg-Johann Lay, 2016/12/07
- Re: [avr-libc-dev] Testsuite (Was: How attached are people ...), Joerg Wunsch, 2016/12/07
- Re: [avr-libc-dev] How attached are people to the implementation of rand()/random()?, Pitchumani Sivanupandi, 2016/12/07
- Re: [avr-libc-dev] How attached are people to the implementation of rand()/random()?, George Spelvin, 2016/12/07
- Re: [avr-libc-dev] How attached are people to the implementation of rand()/random()?, Joerg Wunsch, 2016/12/07
- [avr-libc-dev] Testsuite (Was: How attached are people ...), George Spelvin, 2016/12/07
- Re: [avr-libc-dev] Testsuite (Was: How attached are people ...), Joerg Wunsch, 2016/12/07