Successful bootstrap and install of gcc (GCC) 7.2.0 on powerpc64-unknown-linux-gnu
Hi, Here's a report of a successful build and install of GCC: $ gcc-7.2.0/config.guess powerpc64-unknown-linux-gnu $ newcompiler/bin/gcc -v Using built-in specs. COLLECT_GCC=newcompiler/bin/gcc COLLECT_LTO_WRAPPER=/home/aaro/gcctest/newcompiler/libexec/gcc/powerpc-unknown-linux-gnu/7.2.0/lto-wrapper Target: powerpc-unknown-linux-gnu Configured with: ../gcc-7.2.0/configure --with-cpu-32=G4 --with-cpu-64=G5 --enable-targets=powerpc64-unknown-linux-gnu --disable-nls --prefix=/home/aaro/gcctest/newcompiler --enable-languages=c,c++ --host=powerpc-unknown-linux-gnu --build=powerpc-unknown-linux-gnu --target=powerpc-unknown-linux-gnu --with-system-zlib --with-sysroot=/ Thread model: posix gcc version 7.2.0 (GCC) -- Build environment -- host: g5-xserve-c distro: los.git rootfs=f834d native=f834d kernel: Linux 4.12.0-g5-los_f834d binutils: GNU binutils 2.29 make: GNU Make 4.2.1 libc: GNU C Library (GNU libc) stable release version 2.25 zlib: 1.2.11 mpfr: 3.1.3 gmp: 60102 -- Time consumed -- configure: real0m 7.94s user0m 7.02s sys 0m 3.26s bootstrap: real5h 47m 14s user10h 33m 08s sys 24m 6.64s install:real0m 25.49s user0m 17.77s sys 0m 21.50s -- Hardware details --- MemTotal: 8070196 kB processor : 0 cpu : PPC970FX, altivec supported clock : 2300.00MHz revision: 3.0 (pvr 003c 0300) processor : 1 cpu : PPC970FX, altivec supported clock : 2300.00MHz revision: 3.0 (pvr 003c 0300) timebase: platform: PowerMac model : RackMac3,1 machine : RackMac3,1 motherboard : RackMac3,1 MacRISC4 Power Macintosh detected as : 339 (XServe G5) pmac flags : L2 cache: 512K unified pmac-generation : NewWorld A.
tcl errors during testsuite run
Recently I get a lot of tcl errors during the testsuite run. for example: ERROR: tcl error sourcing /opt/devel/gnu/src/gcc-mingw-w64/gcc-8.0.0/gcc/testsuite/gcc.dg/torture/tls/tls.exp. ERROR: torture-init: torture_without_loops is not empty as expected Does anybody else sees this too? I'm on x86_64-w64-mingw32, msys2 system using tcl 8.5.18-1, dejagnu 1.5.3-1 and expect 5.45-1. Any ideas? Rainer signature.asc Description: OpenPGP digital signature
Re: [Bug web/?????] New: Fwd: failure notice: Bugzilla down.
On 16/08/17 18:38, Joseph Myers wrote: > On Wed, 16 Aug 2017, Eric Gallager wrote: >> I see Richi redid all his 7.2 release changes; does that imply that >> the server restore is now complete? > > No, there's still a search process ongoing to identify corrupted or > missing files by comparison with the last backup. > > My expectation is that all the other Bugzilla changes from 13 and 14 > August UTC need redoing manually (recreating bugs with new numbers in the > case of new bugs filed during that period, if those bugs are still > relevant, repeating comments, etc. - and possibly recreating accounts for > people who created accounts and filed bugs during that period). But I > haven't seen any official announcement from overseers to all affected > projects (for both GCC and Sourceware Bugzillas) yet. > can i resubmit my lost bug reports now?
Re: dejagnu version update?
FYI, DejaGNU 1.6.1 is not compatible with the GCC Testsuite. The GCC Testsuite uses "unsetenv" in multiple instances and that feature has been removed from DejaGNU. The testsuite is going to experience DejaGNU errors when Fedora or OpenSUSE upgrades to a more recent DejaGNU in the 1.6 series. - David
Re: dejagnu version update?
On Fri, Aug 25, 2017 at 6:01 AM, David Edelsohn wrote: > FYI, DejaGNU 1.6.1 is not compatible with the GCC Testsuite. The GCC > Testsuite uses "unsetenv" in multiple instances and that feature has > been removed from DejaGNU. The testsuite is going to experience > DejaGNU errors when Fedora or OpenSUSE upgrades to a more recent > DejaGNU in the 1.6 series. > I am running Fedora 26 with dejagnu-1.6-2.fc26. What should I look for? -- H.J.
Re: dejagnu version update?
On Fri, Aug 25, 2017 at 9:24 AM, H.J. Lu wrote:
> On Fri, Aug 25, 2017 at 6:01 AM, David Edelsohn wrote:
>> FYI, DejaGNU 1.6.1 is not compatible with the GCC Testsuite. The GCC
>> Testsuite uses "unsetenv" in multiple instances and that feature has
>> been removed from DejaGNU. The testsuite is going to experience
>> DejaGNU errors when Fedora or OpenSUSE upgrades to a more recent
>> DejaGNU in the 1.6 series.
>>
>
> I am running Fedora 26 with dejagnu-1.6-2.fc26. What should I
> look for?
ERROR: (DejaGnu) proc "unsetenv GCC_EXEC_PREFIX" does not exist.
The error code is NONE
The info on the error is:
invalid command name "unsetenv"
while executing
"::tcl_unknown unsetenv GCC_EXEC_PREFIX"
("uplevel" body line 1)
invoked from within
"uplevel 1 ::tcl_unknown $args"
- David
Re: [Bug web/?????] New: Fwd: failure notice: Bugzilla down.
On 8/25/17, Szabolcs Nagy wrote: > On 16/08/17 18:38, Joseph Myers wrote: >> On Wed, 16 Aug 2017, Eric Gallager wrote: >>> I see Richi redid all his 7.2 release changes; does that imply that >>> the server restore is now complete? >> >> No, there's still a search process ongoing to identify corrupted or >> missing files by comparison with the last backup. >> >> My expectation is that all the other Bugzilla changes from 13 and 14 >> August UTC need redoing manually (recreating bugs with new numbers in the >> >> case of new bugs filed during that period, if those bugs are still >> relevant, repeating comments, etc. - and possibly recreating accounts for >> >> people who created accounts and filed bugs during that period). But I >> haven't seen any official announcement from overseers to all affected >> projects (for both GCC and Sourceware Bugzillas) yet. >> > > can i resubmit my lost bug reports now? > > Yes, please do. Joseph said the restore was done in a comment on bug web/81846: http://gcc.gnu.org/ml/gcc-bugs/2017-08/msg01718.html
Re: dejagnu version update?
On Fri, Aug 25, 2017 at 6:32 AM, David Edelsohn wrote:
> On Fri, Aug 25, 2017 at 9:24 AM, H.J. Lu wrote:
>> On Fri, Aug 25, 2017 at 6:01 AM, David Edelsohn wrote:
>>> FYI, DejaGNU 1.6.1 is not compatible with the GCC Testsuite. The GCC
>>> Testsuite uses "unsetenv" in multiple instances and that feature has
>>> been removed from DejaGNU. The testsuite is going to experience
>>> DejaGNU errors when Fedora or OpenSUSE upgrades to a more recent
>>> DejaGNU in the 1.6 series.
>>>
>>
>> I am running Fedora 26 with dejagnu-1.6-2.fc26. What should I
>> look for?
>
> ERROR: (DejaGnu) proc "unsetenv GCC_EXEC_PREFIX" does not exist.
> The error code is NONE
> The info on the error is:
> invalid command name "unsetenv"
> while executing
> "::tcl_unknown unsetenv GCC_EXEC_PREFIX"
> ("uplevel" body line 1)
> invoked from within
> "uplevel 1 ::tcl_unknown $args"
>
I checked my log. I didn't see them. Which log file do they appear in?
--
H.J.
Re: dejagnu version update?
On Fri, Aug 25, 2017 at 9:43 AM, H.J. Lu wrote:
> On Fri, Aug 25, 2017 at 6:32 AM, David Edelsohn wrote:
>> On Fri, Aug 25, 2017 at 9:24 AM, H.J. Lu wrote:
>>> On Fri, Aug 25, 2017 at 6:01 AM, David Edelsohn wrote:
FYI, DejaGNU 1.6.1 is not compatible with the GCC Testsuite. The GCC
Testsuite uses "unsetenv" in multiple instances and that feature has
been removed from DejaGNU. The testsuite is going to experience
DejaGNU errors when Fedora or OpenSUSE upgrades to a more recent
DejaGNU in the 1.6 series.
>>>
>>> I am running Fedora 26 with dejagnu-1.6-2.fc26. What should I
>>> look for?
>>
>> ERROR: (DejaGnu) proc "unsetenv GCC_EXEC_PREFIX" does not exist.
>> The error code is NONE
>> The info on the error is:
>> invalid command name "unsetenv"
>> while executing
>> "::tcl_unknown unsetenv GCC_EXEC_PREFIX"
>> ("uplevel" body line 1)
>> invoked from within
>> "uplevel 1 ::tcl_unknown $args"
>>
>
> I checked my log. I didn't see them. Which log file do they appear in?
All log files. I don't know what is different about the invocation of
DejaGNU directives used by testcases on x86 that avoids the problem in
your runs.
One can see references to unsetenv in GCC Testsuite and those are not
valid for DejaGNU 1.6.1+.
- David
Re: dejagnu version update?
Hi H.J.,
> On Fri, Aug 25, 2017 at 6:32 AM, David Edelsohn wrote:
>> On Fri, Aug 25, 2017 at 9:24 AM, H.J. Lu wrote:
>>> On Fri, Aug 25, 2017 at 6:01 AM, David Edelsohn wrote:
FYI, DejaGNU 1.6.1 is not compatible with the GCC Testsuite. The GCC
Testsuite uses "unsetenv" in multiple instances and that feature has
been removed from DejaGNU. The testsuite is going to experience
DejaGNU errors when Fedora or OpenSUSE upgrades to a more recent
DejaGNU in the 1.6 series.
>>>
>>> I am running Fedora 26 with dejagnu-1.6-2.fc26. What should I
>>> look for?
>>
>> ERROR: (DejaGnu) proc "unsetenv GCC_EXEC_PREFIX" does not exist.
>> The error code is NONE
>> The info on the error is:
>> invalid command name "unsetenv"
>> while executing
>> "::tcl_unknown unsetenv GCC_EXEC_PREFIX"
>> ("uplevel" body line 1)
>> invoked from within
>> "uplevel 1 ::tcl_unknown $args"
>>
>
> I checked my log. I didn't see them. Which log file do they appear in?
unsetenv was only removed after DejaGnu 1.6 was released. The change is
in the git repo; so far there exists no post-1.6 release.
Rainer
--
-
Rainer Orth, Center for Biotechnology, Bielefeld University
Re: dejagnu version update?
On Fri, Aug 25, 2017 at 9:50 AM, Rainer Orth
wrote:
> Hi H.J.,
>
>> On Fri, Aug 25, 2017 at 6:32 AM, David Edelsohn wrote:
>>> On Fri, Aug 25, 2017 at 9:24 AM, H.J. Lu wrote:
On Fri, Aug 25, 2017 at 6:01 AM, David Edelsohn wrote:
> FYI, DejaGNU 1.6.1 is not compatible with the GCC Testsuite. The GCC
> Testsuite uses "unsetenv" in multiple instances and that feature has
> been removed from DejaGNU. The testsuite is going to experience
> DejaGNU errors when Fedora or OpenSUSE upgrades to a more recent
> DejaGNU in the 1.6 series.
>
I am running Fedora 26 with dejagnu-1.6-2.fc26. What should I
look for?
>>>
>>> ERROR: (DejaGnu) proc "unsetenv GCC_EXEC_PREFIX" does not exist.
>>> The error code is NONE
>>> The info on the error is:
>>> invalid command name "unsetenv"
>>> while executing
>>> "::tcl_unknown unsetenv GCC_EXEC_PREFIX"
>>> ("uplevel" body line 1)
>>> invoked from within
>>> "uplevel 1 ::tcl_unknown $args"
>>>
>>
>> I checked my log. I didn't see them. Which log file do they appear in?
>
> unsetenv was only removed after DejaGnu 1.6 was released. The change is
> in the git repo; so far there exists no post-1.6 release.
That is why I wrote 1.6.1. I didn't know if 1.6-2 was from snapshot after 1.6.
Future releases of DejaGNU will elicit errors from the GCC Testsuite
as currently written. My message is a warning about future
incompatibility.
Thanks, David
Re: dejagnu version update?
Hi,
On Fri, Aug 25, 2017 at 09:55:29AM -0400, David Edelsohn wrote:
> On Fri, Aug 25, 2017 at 9:50 AM, Rainer Orth
> wrote:
> > Hi H.J.,
> >
> >> On Fri, Aug 25, 2017 at 6:32 AM, David Edelsohn wrote:
> >>> On Fri, Aug 25, 2017 at 9:24 AM, H.J. Lu wrote:
> On Fri, Aug 25, 2017 at 6:01 AM, David Edelsohn
> wrote:
> > FYI, DejaGNU 1.6.1 is not compatible with the GCC Testsuite. The GCC
> > Testsuite uses "unsetenv" in multiple instances and that feature has
> > been removed from DejaGNU. The testsuite is going to experience
> > DejaGNU errors when Fedora or OpenSUSE upgrades to a more recent
> > DejaGNU in the 1.6 series.
> >
>
> I am running Fedora 26 with dejagnu-1.6-2.fc26. What should I
> look for?
> >>>
> >>> ERROR: (DejaGnu) proc "unsetenv GCC_EXEC_PREFIX" does not exist.
> >>> The error code is NONE
> >>> The info on the error is:
> >>> invalid command name "unsetenv"
> >>> while executing
> >>> "::tcl_unknown unsetenv GCC_EXEC_PREFIX"
> >>> ("uplevel" body line 1)
> >>> invoked from within
> >>> "uplevel 1 ::tcl_unknown $args"
> >>>
> >>
> >> I checked my log. I didn't see them. Which log file do they appear in?
> >
> > unsetenv was only removed after DejaGnu 1.6 was released. The change is
> > in the git repo; so far there exists no post-1.6 release.
>
> That is why I wrote 1.6.1. I didn't know if 1.6-2 was from snapshot after
> 1.6.
>
> Future releases of DejaGNU will elicit errors from the GCC Testsuite
> as currently written. My message is a warning about future
> incompatibility.
from the current git-branch:
+Changes since 1.6:
+
+1. The user-visible utility procedure `unsetenv' has been removed. If
+ a testsuite uses any of these procedures, a copy of the procedure
+ should be made and placed in the lib directory of the testsuite.
+
gcc is not the only testsuite which breaks. From a quick look on
some of my local source-packages:
Python-2.7.13
Python-3.6.2
libffi-3.2.1
gcc-7.2.0
Maybe reporting this to the dejagnu-developers might be the better
approach:
author Ben Elliston 2016-04-24 20:46:53 +1000
committer Ben Elliston 2016-04-24 20:46:53 +1000
commit c7185dfb66b0b278709d869ba020eec8348796ef (patch)
regards
winfried
Successful bootstrap and install of gcc (GCC) 7.2.0 on mips64-unknown-linux-gnu
Hi, Here's a report of a successful build and install of GCC: $ gcc-7.2.0/config.guess mips64-unknown-linux-gnu $ newcompiler/bin/gcc -v Using built-in specs. COLLECT_GCC=newcompiler/bin/gcc COLLECT_LTO_WRAPPER=/home/aaro/gcctest/newcompiler/libexec/gcc/mips-unknown-linux-gnu/7.2.0/lto-wrapper Target: mips-unknown-linux-gnu Configured with: ../gcc-7.2.0/configure --with-arch=octeon+ --with-abi=32 --enable-targets=all --with-float=soft --disable-nls --prefix=/home/aaro/gcctest/newcompiler --enable-languages=c,c++ --host=mips-unknown-linux-gnu --build=mips-unknown-linux-gnu --target=mips-unknown-linux-gnu --with-system-zlib --with-sysroot=/ Thread model: posix gcc version 7.2.0 (GCC) -- Build environment -- host: edgerouter-pro distro: los.git rootfs=f834d native=f834d kernel: Linux 4.12.0-octeon-los_f834d binutils: GNU binutils 2.29 make: GNU Make 4.2.1 libc: GNU C Library (GNU libc) stable release version 2.25 zlib: 1.2.11 mpfr: 3.1.3 gmp: 60102 -- Time consumed -- configure: real0m 10.74s user0m 12.49s sys 0m 1.25s bootstrap: real14h 50m 39s user26h 26m 53s sys 1h 47m 58s install:real9m 11.24s user3m 20.54s sys 4m 58.00s -- Hardware details --- MemTotal: 2011492 kB system type : ubnt,e200 (CN6120p1.1-1000-NSP) machine : Unknown processor : 0 cpu model : Cavium Octeon II V0.1 BogoMIPS: 2000.00 wait instruction: yes microsecond timers : yes tlb_entries : 128 extra interrupt vector : yes hardware watchpoint : yes, count: 2, address/irw mask: [0x0ffc, 0x0ffb] isa : mips2 mips3 mips4 mips5 mips64r2 ASEs implemented: shadow register sets: 1 kscratch registers : 3 package : 0 core: 0 VCED exceptions : not available VCEI exceptions : not available processor : 1 cpu model : Cavium Octeon II V0.1 BogoMIPS: 2000.00 wait instruction: yes microsecond timers : yes tlb_entries : 128 extra interrupt vector : yes hardware watchpoint : yes, count: 2, address/irw mask: [0x0ffc, 0x0ffb] isa : mips2 mips3 mips4 mips5 mips64r2 ASEs implemented: shadow register sets: 1 kscratch registers : 3 package : 0 core: 1 VCED exceptions : not available VCEI exceptions : not available A.
