On 2/4/06, Ralf Corsepius <[EMAIL PROTECTED]> wrote:
> On Fri, 2006-02-03 at 09:45 -0600, Joel Sherrill wrote:
> > >>>The problem is with using stdint.h integer types without checking if
> > >>>they are actually
> > >>>available. I have posted a fix for this already that needs to be
> > >>>reviewe
On Fri, 2006-02-03 at 09:45 -0600, Joel Sherrill wrote:
> >>>The problem is with using stdint.h integer types without checking if
> >>>they are actually
> >>>available. I have posted a fix for this already that needs to be
> >>>reviewed. Along with
> >>>some other fixes for similar target OS depe
Richard Guenther wrote:
On 2/3/06, Richard Guenther <[EMAIL PROTECTED]> wrote:
Can you try using
libsse2_la_AM_CFLAGS instead of libsse2_la_CFLAGS in i386/Makefile.am?
Forget that. This automake seems to ignore.
What can I do to help you. Do you want a build log?
If you want to
On 2/3/06, Richard Guenther <[EMAIL PROTECTED]> wrote:
> Can you try using
> libsse2_la_AM_CFLAGS instead of libsse2_la_CFLAGS in i386/Makefile.am?
Forget that. This automake seems to ignore.
Richard.
On 2/3/06, Joel Sherrill <[EMAIL PROTECTED]> wrote:
>
> >>>The problem is with using stdint.h integer types without checking if
> >>>they are actually
> >>>available. I have posted a fix for this already that needs to be
> >>>reviewed. Along with
> >>>some other fixes for similar target OS depend
The problem is with using stdint.h integer types without checking if
they are actually
available. I have posted a fix for this already that needs to be
reviewed. Along with
some other fixes for similar target OS dependent bugs. Patch is here:
http://gcc.gnu.org/ml/gcc-patches/2006-02/msg00032
On 2/3/06, Joel Sherrill <[EMAIL PROTECTED]> wrote:
> Richard Guenther wrote:
>
> >On 2/2/06, Joel Sherrill <[EMAIL PROTECTED]> wrote:
> >
> >
> >>Karel Gardas wrote:
> >>
> >>
> >>
> >>>If this help, I'd like to add that I succesfully compiled
> >>>gcc-4.2-20060128.tar.bz2 for the same configurati
Richard Guenther wrote:
On 2/2/06, Joel Sherrill <[EMAIL PROTECTED]> wrote:
Karel Gardas wrote:
If this help, I'd like to add that I succesfully compiled
gcc-4.2-20060128.tar.bz2 for the same configuration.
I think my last SVN update that built for me was a couple of days bef
On 2/2/06, Joel Sherrill <[EMAIL PROTECTED]> wrote:
> Karel Gardas wrote:
>
> >
> > If this help, I'd like to add that I succesfully compiled
> > gcc-4.2-20060128.tar.bz2 for the same configuration.
> >
> I think my last SVN update that built for me was a couple of days before
> that.
The problem
Karel Gardas wrote:
If this help, I'd like to add that I succesfully compiled
gcc-4.2-20060128.tar.bz2 for the same configuration.
I think my last SVN update that built for me was a couple of days before
that.
--joel
Cheers,
Karel
On Thu, 2 Feb 2006, Joel Sherrill wrote:
This is a
If this help, I'd like to add that I succesfully compiled
gcc-4.2-20060128.tar.bz2 for the same configuration.
Cheers,
Karel
On Thu, 2 Feb 2006, Joel Sherrill wrote:
This is a breakage in about the past week. I built
a native compiler from the same source. Does this look
familiar to any
This is a breakage in about the past week. I built
a native compiler from the same source. Does this look
familiar to anyone?
home/joel/gcc-work/head/b-i386-rtems4.7/./gcc/xgcc
-B/home/joel/gcc-work/head/b-i386-rtems4.7/./gcc/ -nostdinc -B/ho
me/joel/gcc-work/head/b-i386-rtems4.7/i386-rtems4.
12 matches
Mail list logo