Hi all I have build the toolchain:
binutils-2.20
gcc-4.3.5
newlib-1.18.0
for target sh-elf
for c and c++
successfully
T htink it will be usefull to write this (very very usefull for firmware
developer) news onto the successfully building list
How can I do this?
Do I need to make alse the test su
Status
==
GCC 4.4.5 release tarballs have been uploaded to gcc.gnu.org and to
ftp.gnu.org, the 4.4 branch is again open for commits under the
usual release branch rules. It took a little longer than I've initially
expected, but there were important P1 regressions that caused delays.
I'll a
On 09/20/2010 07:06 PM, Rodrigo Rivas wrote:
Are you sure? As I said in other post, I am no longer sure that the
C++0x draft forbids the type definition in this context.
But I'm no expert in standarese, so I'm still undecided.
It took me some searching, but yes, it does:
"A type-specifier-seq
Hi,
I was wondering how people manage to get the branch and svn revision into the
subject of a contrib/test_summary submission. Is it supposed to be detected
automagically? Or is it something you add with configure --with-pkgversion when
building?
Thanks in advance,
Sean
On 10/01/2010 10:58 AM, Sean McGovern wrote:
> Hi,
>
> I was wondering how people manage to get the branch and svn revision into the
> subject of a contrib/test_summary submission. Is it supposed to be detected
> automagically? Or is it something you add with configure --with-pkgversion
> when
"Sean McGovern" writes:
> I was wondering how people manage to get the branch and svn revision into the
> subject of a contrib/test_summary submission. Is it supposed to be detected
> automagically? Or is it something you add with configure --with-pkgversion
> when building?
It is recorded by
Thanks. I guess I missed that part in the online documentation.
-- Sean
--Original Message--
From: Richard Henderson
To: Sean McGovern
Cc: gcc@gcc.gnu.org
Subject: Re: gcc-testresults submissions
Sent: Oct 1, 2010 14:02
On 10/01/2010 10:58 AM, Sean McGovern wrote:
> Hi,
>
> I was wonderi
