Richard Sandiford writes:
> Gerald Pfeifer writes:
>> On Sat, 17 May 2014, Richard Sandiford wrote:
>>> To rule out one possibility: which GCC are you using for stage1?
>>
>> I think that may the smoking gun. When I use GCC 4.7 to bootstrap,
>> FreeBSD 8, 9 and 10 all build fine on i386 (= i486)
Gerald Pfeifer writes:
> On Sat, 17 May 2014, Richard Sandiford wrote:
>> To rule out one possibility: which GCC are you using for stage1?
>
> I think that may the smoking gun. When I use GCC 4.7 to bootstrap,
> FreeBSD 8, 9 and 10 all build fine on i386 (= i486) and amd64.
>
> When I use the sys
On Sat, 17 May 2014, Richard Sandiford wrote:
> To rule out one possibility: which GCC are you using for stage1?
I think that may the smoking gun. When I use GCC 4.7 to bootstrap,
FreeBSD 8, 9 and 10 all build fine on i386 (= i486) and amd64.
When I use the system compiler, which is GCC 4.2 on F
Gerald Pfeifer writes:
> On Sat, 10 May 2014, Gerald Pfeifer wrote:
>> Since (at least) 16:40 UTC that day my i386-unknown-freebsd10.0 builds
>> fail as follows:
>>
>> Comparing stages 2 and 3
>> warning: gcc/cc1obj-checksum.o differs
>> warning: gcc/cc1-checksum.o differs
>> warning: gcc
On Sat, 10 May 2014, Gerald Pfeifer wrote:
> Since (at least) 16:40 UTC that day my i386-unknown-freebsd10.0 builds
> fail as follows:
>
> Comparing stages 2 and 3
> warning: gcc/cc1obj-checksum.o differs
> warning: gcc/cc1-checksum.o differs
> warning: gcc/cc1plus-checksum.o differs
> B
On Tue, 6 May 2014, Mike Stump wrote:
> All done… It is in.
Since (at least) 16:40 UTC that day my i386-unknown-freebsd10.0 builds
fail as follows:
Comparing stages 2 and 3
warning: gcc/cc1obj-checksum.o differs
warning: gcc/cc1-checksum.o differs
warning: gcc/cc1plus-checksum.o differs
Jan-Benedict Glaw writes:
> On Tue, 2014-05-06 12:20:54 -0700, Mike Stump wrote:
>> On May 6, 2014, at 8:19 AM, Kenneth Zadeck wrote:
>> > please hold off on committing patches for the next couple of hours
>> > as we have a very large merge to do.
>> > thanks.
>>
>> All done… It is in.
>
> Jus
On 7 May 2014 09:48, Andreas Schwab wrote:
> Christophe Lyon writes:
>
>> It also looks like the git-svn-id property is now wrong/incomplete.
>> For instance, commit 9a5942c1d4d9116ab74b0741cfe3894a89fd17fb has:
>> git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/branches/wide-int@201706
>> 138bc75d
Christophe Lyon writes:
> It also looks like the git-svn-id property is now wrong/incomplete.
> For instance, commit 9a5942c1d4d9116ab74b0741cfe3894a89fd17fb has:
> git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/branches/wide-int@201706
> 138bc75d-0d04-0410-961f-82ee72b054a4
>
> How does it map to
On Tue, 2014-05-06 12:20:54 -0700, Mike Stump wrote:
> On May 6, 2014, at 8:19 AM, Kenneth Zadeck wrote:
> > please hold off on committing patches for the next couple of hours as we
> > have a very large merge to do.
> > thanks.
>
> All done… It is in.
Just found one more:
g++ -c -g -O2 -D
On May 6, 2014, at 3:54 PM, Mike Stump wrote:
>
>> My build robot experiences errors like this:
>>
>> g++ -c -g -O2 -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -fno-exceptions
>> -fno-rtti -fasynchronous-unwind-tables -W -Wall -Wno-narrowing
>> -Wwrite-strings -Wcast-qual -Wmissing-format-attribu
On May 6, 2014, at 3:54 PM, Mike Stump wrote:
>
> I’m pretty sure this:
> will fix it. If someone can confirm that would be great.
I tried that on my p7 and on my x86_64 machines, they both build fine.
On Tue, 2014-05-06 15:54:05 -0700, Mike Stump wrote:
> On May 6, 2014, at 2:17 PM, Jan-Benedict Glaw wrote:
> > On Tue, 2014-05-06 12:20:54 -0700, Mike Stump wrote:
> > > On May 6, 2014, at 8:19 AM, Kenneth Zadeck
> > > wrote:
> > > > please hold off on committing patches for the next couple o
I have noticed build failures too (arm, aarch64).
It also looks like the git-svn-id property is now wrong/incomplete.
For instance, commit 9a5942c1d4d9116ab74b0741cfe3894a89fd17fb has:
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/branches/wide-int@201706
138bc75d-0d04-0410-961f-82ee72b054a4
How
On May 6, 2014, at 2:17 PM, Jan-Benedict Glaw wrote:
> On Tue, 2014-05-06 12:20:54 -0700, Mike Stump wrote:
>> On May 6, 2014, at 8:19 AM, Kenneth Zadeck wrote:
>>> please hold off on committing patches for the next couple of hours as we
>>> have a very large merge to do.
>>> thanks.
>>
>> All
On Tue, 2014-05-06 12:20:54 -0700, Mike Stump wrote:
> On May 6, 2014, at 8:19 AM, Kenneth Zadeck wrote:
> > please hold off on committing patches for the next couple of hours as we
> > have a very large merge to do.
> > thanks.
>
> All done… It is in.
My build robot experiences errors like t
On May 6, 2014, at 8:19 AM, Kenneth Zadeck wrote:
> please hold off on committing patches for the next couple of hours as we have
> a very large merge to do.
> thanks.
All done… It is in.
17 matches
Mail list logo