On Fri, 30 Mar 2007, Christopher Faylor wrote:
> On Fri, Mar 30, 2007 at 10:30:11AM +0200, Angelo Graziosi wrote:
> >Dave Korn wrote:
> >
> >> Patch prepared, I'll finish writing it up and submit to the newlib list
> >> later tonight, but first I'm going to have a celebratory beer or two on
> >> t
On Fri, Mar 30, 2007 at 10:30:11AM +0200, Angelo Graziosi wrote:
>Dave Korn wrote:
>
>> Patch prepared, I'll finish writing it up and submit to the newlib list
>> later tonight, but first I'm going to have a celebratory beer or two on
>> the way home...
>
>I have applied the patch
>(http://sourcewa
Dave Korn wrote:
> Patch prepared, I'll finish writing it up and submit to the newlib list
> later tonight, but first I'm going to have a celebratory beer or two on
> the way home...
I have applied the patch
(http://sourceware.org/ml/newlib/2007/msg00292.html) an GCC-4.3
(core+gfortran) builds (
On 25 March 2007 00:55, Dave Korn wrote:
> On 22 March 2007 22:08, Brian Dessent wrote:
>
>> The real problem seems to be that the libgcc is broken:
>
>> /home/User/cvsroot/gcc-obj/./prev-gcc/libgcc.a(_ctors.o): In function
>> `__sgetc_r': /usr/include/stdio.h:414: undefined reference to `_unget
On 22 March 2007 22:08, Brian Dessent wrote:
> The real problem seems to be that the libgcc is broken:
> /home/User/cvsroot/gcc-obj/./prev-gcc/libgcc.a(_ctors.o): In function
> `__sgetc_r':
> /usr/include/stdio.h:414: undefined reference to `_ungetc'
> /usr/include/stdio.h:410: undefined referenc
[EMAIL PROTECTED] wrote:
Angelo Graziosi wrote:
As I wrote:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31039
Ah, okay. I failed to see that you'd posted the config.log there. (And
I mentioned gmp/mpfr as I have seen that cause the build to fail in
exactly the way you described, but it's
On Thu, Mar 22, 2007 at 06:55:16PM -0700, Tim Prince wrote:
>[EMAIL PROTECTED] wrote:
>>There is no conspiracy. What is needed is for there to be a vocal
>>advocate on the gcc list for Windows patches. I can only approve a very
>>limited amount of stuff so we need gcc global maintainers to approv
[EMAIL PROTECTED] wrote:
There is no conspiracy. What is needed is for there to be a vocal
advocate on the gcc list for Windows patches. I can only approve a very
limited amount of stuff so we need gcc global maintainers to approve the
majority of Windows fixes.
I didn't call it a conspiracy,
Angelo Graziosi wrote:
> As I wrote:
>
> >> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31039
Ah, okay. I failed to see that you'd posted the config.log there. (And
I mentioned gmp/mpfr as I have seen that cause the build to fail in
exactly the way you described, but it's clearly not the case
Brian Dessent wrote:
> You'll have to look at config.log but this is probably a problem with
> your system lacking all the required gmp and mpfr library packages.
> Make sure you have them all.
I have obviously GMP and MPFR installed and, as I wrote
>>...
>> The last 4.3.0 source that builds
On Thu, Mar 22, 2007 at 08:23:46AM -0700, Brian Dessent wrote:
>Charles Wilson wrote:
>
>> I'm sorry, but the concerns expressed in the messages above are rank
>> paranoia. *Microsoft* has nothing to do with the lack of operable
>> modern gcc's on windows, and there is no conspiracy to break gcc o
On Thu, 22 Mar 2007, Brian Dessent wrote:
> Charles Wilson wrote:
>
> [snip]
> > (2) the java runtime library is huge, and to even attempt to link it
> > as a DLL requires massive (>1GB) amounts of RAM. I seem to recall
> > that this is due to inefficiencies in the way ld creates import
> > libra
Charles Wilson wrote:
> I'm sorry, but the concerns expressed in the messages above are rank
> paranoia. *Microsoft* has nothing to do with the lack of operable
> modern gcc's on windows, and there is no conspiracy to break gcc on cygwin.
Yes, that's pure FUD.
> But having an active maintainer
Angelo Graziosi wrote:
> checking for i686-pc-cygwin-gcc... /tmp/gcc/.build/./prev-gcc/xgcc
> -B/tmp/gcc/.build/./prev-gcc/ -B/usr/local/gfortran/i686-pc-cygwin/bin/
> checking for C compiler default output file name... configure: error: C
> compiler cannot create executables
> See `config.log' f
Angelo Graziosi wrote:
It is almost a month that the build og gcc-core 4.3.0 on Cygwin is broken:
The last 4.3.0 source that builds fine is GCC-4.3.0-20070224-trunk-122292.
The strange thing is not that a development version of GCC is broken, but
that there is NOT much will to solve it for CY
15 matches
Mail list logo
