U.Mutlu writes:
>> Thanks! I'm very grateful for your help. I succeeded in building
>> gcc-4.7.4 from almost no binary seeds[0] for GuixSD!
>
> Congrats! :-)
Thanks!
> Can you give us some info on your project? (mes?)
Mes[0] aims to help create full source bootstrapping for GNU/Linux
distrib
Jan Nieuwenhuizen wrote on 07/11/2018 07:01 PM:
U.Mutlu writes:
Just a tip: you can build the compiler much faster if you use
--disable-bootstrap
(here it reduces the compile time from 111 minutes down to 12 minutes).
After it's ok, then you can build w/o it to also test the
bootstrapping.
T
U.Mutlu writes:
> Just a tip: you can build the compiler much faster if you use
> --disable-bootstrap
> (here it reduces the compile time from 111 minutes down to 12 minutes).
> After it's ok, then you can build w/o it to also test the
> bootstrapping.
Thanks! I'm very grateful for your help.
On Tue, 10 Jul 2018 at 20:51, Jan Nieuwenhuizen wrote:
> However, now i get this error (I do not have pthreads/pthreads.h).
GNU/Linux targets are assumed to have Pthreads (because they should do).
Use --disable-threads or --enable-threads=single to override the default.
Jan Nieuwenhuizen writes:
> Gábor Boskovits writes:
>
>> It seems that the errors you were getting are related to 128 bit
>> floating point support. It also seems that 128 bit floating point
>> support is enabled on 64 bits. I'm not sure about the 32 bit case
>> though, do you get the same error t
Hi Janneke,
On Mon, 09 Jul 2018 18:57:16 +0200
Jan Nieuwenhuizen wrote:
> i386-unknown-linux-gcc
> --sysroot=/gnu/store/jdjpfzjr2zf3xbf7ssl11ljwpq7spid8-glibc-mesboot-2.3.6/include
>-g -O2 -O2 -g -O2 -DIN_GCC -W -Wall -Wwrite-strings -Wcast-qual
> -Wstrict-prototypes -Wmissing-prot
Gábor Boskovits writes:
> It seems that the errors you were getting are related to 128 bit
> floating point support. It also seems that 128 bit floating point
> support is enabled on 64 bits. I'm not sure about the 32 bit case
> though, do you get the same error there?
Ah! That makes me even m
U.Mutlu writes:
> You have attached config.h of 2 targets.
> Is just one of them failing, or both?
I hoped to just get one, but I get two; I configure using
../build/configure --host=i386-unknown-linux --target=i386-unknown-linux ...
> And of course: are they both using the same target arch
U.Mutlu ezt írta (időpont: 2018. júl. 10., K, 5:53):
> Jan Nieuwenhuizen wrote on 07/09/2018 09:40 PM:
> > U.Mutlu writes:
> >
> >> What do you get if you grep for "error: " in the xxx/libgcc/config.log
> >> under the builddir?
> >
> > janneke@guix-x86 /tmp/guix-build-gcc-mesboot-4.7.4.drv-0/gcc-
Jan Nieuwenhuizen wrote on 07/09/2018 09:40 PM:
U.Mutlu writes:
What do you get if you grep for "error: " in the xxx/libgcc/config.log
under the builddir?
janneke@guix-x86 /tmp/guix-build-gcc-mesboot-4.7.4.drv-0/gcc-4.7.4$ grep
'error: ' i386-unknown-linux/libgcc/config.log
conftest.c:9:28:
Jan Nieuwenhuizen wrote on 07/09/2018 06:57 PM:
Hi!
I'm working on a full source bootstrap for a GNU system, GuixSD in
particular. With the Mes 0.16 release I thought it was done, but now it
seems I'm stuck.
Using the MesCC C99 compiler written in Guile Scheme, I compiled tcc-0.9.26
and a tiny
U.Mutlu writes:
> What do you get if you grep for "error: " in the xxx/libgcc/config.log
> under the builddir?
janneke@guix-x86 /tmp/guix-build-gcc-mesboot-4.7.4.drv-0/gcc-4.7.4$ grep
'error: ' i386-unknown-linux/libgcc/config.log
conftest.c:9:28: error: ac_nonexistent.h: No such file or directo
Hi!
I'm working on a full source bootstrap for a GNU system, GuixSD in
particular. With the Mes 0.16 release I thought it was done, but now it
seems I'm stuck.
Using the MesCC C99 compiler written in Guile Scheme, I compiled tcc-0.9.26
and a tiny Mes C library, barely enough to build
binuti
13 matches
Mail list logo
