Re: gcc 13 Build error

, because it should build without errors. > On Sun, Apr 2, 2023 at 7:13 PM Damian Tometzki > wrote: > > > > Hello together, > > > > i have the following build error gcc 13 current git: > > > > /home/damian/data/gcc13built/./prev-gcc/xg++ > > -B/home/dam

Re: gcc 13 Build error

s conflict with \float extensions", arch); return subset_list; On Sun, Apr 2, 2023 at 7:13 PM Damian Tometzki wrote: > > Hello together, > > i have the following build error gcc 13 current git: > > /home/damian/data/gcc13built/./prev-gcc/xg++ > -B/home/damian/d

gcc 13 Build error

Hello together, i have the following build error gcc 13 current git: /home/damian/data/gcc13built/./prev-gcc/xg++ -B/home/damian/data/gcc13built/./prev-gcc/ -B/usr/riscv64-linux-gnu/bin/ -nostdinc++ -B/home/damian/data/gcc13built/prev-riscv64-linux-gnu/libstdc++-v3/src/.libs -B/home/damian/data

Re: [PATCH] analyzer: fix build error with clang (PR 93543)

On 04/02/2020 16:45, David Malcolm wrote: On Tue, 2020-02-04 at 16:26 +0100, Jakub Jelinek wrote: On Tue, Feb 04, 2020 at 09:00:37AM -0500, David Malcolm wrote: gcc/analyzer/ChangeLog: PR analyzer/93543 * engine.cc (pod_hash_traits::mark_empty): Eliminate reinterpret_ca

Re: [PATCH] analyzer: fix build error with clang (PR 93543)

On Tue, 2020-02-04 at 16:26 +0100, Jakub Jelinek wrote: > On Tue, Feb 04, 2020 at 09:00:37AM -0500, David Malcolm wrote: > > gcc/analyzer/ChangeLog: > > PR analyzer/93543 > > * engine.cc > > (pod_hash_traits::mark_empty): > > Eliminate reinterpret_cast. > > (pod_hash_traits::is_empt

Re: [PATCH] analyzer: fix build error with clang (PR 93543)

On Tue, Feb 04, 2020 at 09:00:37AM -0500, David Malcolm wrote: > gcc/analyzer/ChangeLog: > PR analyzer/93543 > * engine.cc (pod_hash_traits::mark_empty): > Eliminate reinterpret_cast. > (pod_hash_traits::is_empty): Likewise. This is ok for trunk. > gcc/analyzer/engine.cc

[PATCH] analyzer: fix build error with clang (PR 93543)

On Tue, 2020-02-04 at 14:53 +0100, Sebastian Huber wrote: > Hello, > > I tried to build a recent GCC master on FreeBSD 12.1 and it failed > with > a compile error: > > $ clang --version > FreeBSD clang version 8.0.1 (tags/RELEASE_801/final 366581) (based > on > LLVM 8.0.1) > Target: x86_64-unkn

Re: GCC build error on FreeBSD 12.1 with LLVM 8.0.1

On Tue, Feb 04, 2020 at 02:53:42PM +0100, Sebastian Huber wrote: > I tried to build a recent GCC master on FreeBSD 12.1 and it failed with a > compile error: That is http://gcc.gnu.org/PR93543 Jakub

GCC build error on FreeBSD 12.1 with LLVM 8.0.1

Hello, I tried to build a recent GCC master on FreeBSD 12.1 and it failed with a compile error: $ clang --version FreeBSD clang version 8.0.1 (tags/RELEASE_801/final 366581) (based on LLVM 8.0.1) Target: x86_64-unknown-freebsd12.1 Thread model: posix InstalledDir: /usr/bin ../../gnu-mirror-

Re: [PING][PATCH] gdb/x86: Fix `-Wstrict-overflow' build error in `i387_collect_xsave'

On 05/22/2018 12:14 PM, Maciej W. Rozycki wrote: > On Tue, 15 May 2018, Maciej W. Rozycki wrote: > >> gdb/ >> * i387-tdep.c (i387_collect_xsave): Make `i' unsigned. > > Ping for: . OK. Thanks, Pedro Alves

[PING][PATCH] gdb/x86: Fix `-Wstrict-overflow' build error in `i387_collect_xsave'

On Tue, 15 May 2018, Maciej W. Rozycki wrote: > gdb/ > * i387-tdep.c (i387_collect_xsave): Make `i' unsigned. Ping for: . Maciej

[PATCH] gdb/x86: Fix `-Wstrict-overflow' build error in `i387_collect_xsave'

Make `i' defined within `i387_collect_xsave' unsigned, removing a `-Werror=strict-overflow' compilation error: .../gdb/i387-tdep.c: In function 'void i387_collect_xsave(const regcache*, int, void*, int)': .../gdb/i387-tdep.c:1348:1: error: assuming signed overflow does not occur when assuming t

Re: profiledbootstrap build error

On Tue, Oct 28, 2014 at 3:45 PM, Rogelio Serrano wrote: > any hint debugging this? > > /home/rogelio/gcc-build/./prev-gcc/g++ > -B/home/rogelio/gcc-build/./prev-gcc/ -B/x86_64-unknown-linux-gnu/bin/ > -nostdinc++ > -B/home/rogelio/gcc-build/prev-x86_64-unknown-linux-gnu/libstdc++-v3/src/.libs > -

profiledbootstrap build error

any hint debugging this? /home/rogelio/gcc-build/./prev-gcc/g++ -B/home/rogelio/gcc-build/./prev-gcc/ -B/x86_64-unknown-linux-gnu/bin/ -nostdinc++ -B/home/rogelio/gcc-build/prev-x86_64-unknown-linux-gnu/libstdc++-v3/src/.libs -B/home/rogelio/gcc-build/prev-x86_64-unknown-linux-gnu/libstdc++-v3/li

Re: toolchain build error with eglibc on OpenWrt

On 17/07/2013, at 6:26 PM, lingw...@altaitechnologies.com wrote: > Hi developers, > > I'm encountered a problem when I build OpenWrt's toolchain for Cavium > Octeon,which is mips64 r2 architectural.the error message as follow: > My toolchain units version: > gcc: 4.7.x > binutils: 2.22 > eg

Re: build error in libgcc

2013/6/22 Ian Lance Taylor : > On Sat, Jun 22, 2013 at 12:17 AM, Chung-Ju Wu wrote: >> Like this? >> >> === >> --- libgcc/Makefile.in (revision 200306) >> +++ libgcc/Makefile.in (working copy) >> @@ -121,8 +121,8 @@ >> .PHONY: all

Re: build error in libgcc

On Sat, Jun 22, 2013 at 12:17 AM, Chung-Ju Wu wrote: > Like this? > > === > --- libgcc/Makefile.in (revision 200306) > +++ libgcc/Makefile.in (working copy) > @@ -121,8 +121,8 @@ > .PHONY: all clean > > clean: > - -rm -f aut

Re: build error in libgcc

2013/6/22 Andreas Schwab : > Chung-Ju Wu writes: > >> clean: >> - -rm -f auto-target.h libgcc_tm.h libgcc.map >> + -rm -f libgcc_tm.h libgcc.map >> -rm -f libgcc_tm.stamp stamp-h stmp-ldirs > > Same for stamp-h. > Like this? ==

Re: build error in libgcc

Chung-Ju Wu writes: > clean: > - -rm -f auto-target.h libgcc_tm.h libgcc.map > + -rm -f libgcc_tm.h libgcc.map > -rm -f libgcc_tm.stamp stamp-h stmp-ldirs Same for stamp-h. Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 0

Re: build error in libgcc

2013/6/22 Ian Lance Taylor : > On Thu, Jun 20, 2013 at 6:25 PM, Mike Stump wrote: >> A make clean followed by a make in the libgcc directory results in: >> >> ../../../../gcc/libgcc/config/i386/cpuinfo.c:23:25: fatal error: >> auto-target.h: No such file or directory >> #include "auto-target.h"

Re: build error in libgcc

On Thu, Jun 20, 2013 at 6:25 PM, Mike Stump wrote: > A make clean followed by a make in the libgcc directory results in: > > ../../../../gcc/libgcc/config/i386/cpuinfo.c:23:25: fatal error: > auto-target.h: No such file or directory > #include "auto-target.h" > > Oh, the the old days, we'd just

Re: build error in libgcc

Mike Stump writes: > A make clean followed by a make in the libgcc directory results in: > > ../../../../gcc/libgcc/config/i386/cpuinfo.c:23:25: fatal error: > auto-target.h: No such file or directory > #include "auto-target.h" > > Oh, the the old days, we'd just add a dependancy… If someone kn

build error in libgcc

A make clean followed by a make in the libgcc directory results in: ../../../../gcc/libgcc/config/i386/cpuinfo.c:23:25: fatal error: auto-target.h: No such file or directory #include "auto-target.h" Oh, the the old days, we'd just add a dependancy… If someone knows where to add just the right

Re: GCC build error

On Thu, May 09, 2013 at 08:19:45PM +, Iyer, Balaji V wrote: > Hello Everyone, > I am currently trying to build the GCC trunk (revision 198747) and it > is giving me the following error in make install for the java compiler. It > looks like it is not able to find a function. > > Thanks

GCC build error

Hello Everyone, I am currently trying to build the GCC trunk (revision 198747) and it is giving me the following error in make install for the java compiler. It looks like it is not able to find a function. Thanks, Balaji V. Iyer. libtool: link: /export/users/gcc-svn/b-trunk-gcc/./gc

RE: Build error in genconstants.c

Hi Marc, Please see my response below. > -Original Message- > From: Marc Glisse [mailto:marc.gli...@inria.fr] > Sent: Tuesday, January 08, 2013 6:20 PM > To: Iyer, Balaji V > Cc: 'gcc@gcc.gnu.org' > Subject: RE: Build error in genconstants.c > >

RE: Build error in genconstants.c

On Tue, 8 Jan 2013, Iyer, Balaji V wrote: Thanks for your response. I looked at config.log and I got the following information about sbrk. This error only occurs when I type "make." If I reconfigured the build directory and typed "make -j8" (or whatever the number of cores I have on my machin

RE: Build error in genconstants.c

std.h:1046:14: note: previous declaration of 'sbrk' was here extern void *sbrk (intptr_t __delta) __THROW; ../../trunk-gcc/gcc/system.h:446:14: error: conflicting types for 'sbrk' extern void *sbrk (int); /usr/include/unistd.h:1046:14: note: previous declaration of 'sbrk&#x

Re: Build error in genconstants.c

On Tue, 8 Jan 2013, Iyer, Balaji V wrote: Hello Everyone, I am getting the following error when I tried to build the trunk (revision 194999) on my SuSE machine (Linux 2.6.32.29-0.3-default x86_64). I just did the standard configure (../src_directory/configure --prefix=<>). It looks li

Build error in genconstants.c

Hello Everyone, I am getting the following error when I tried to build the trunk (revision 194999) on my SuSE machine (Linux 2.6.32.29-0.3-default x86_64). I just did the standard configure (../src_directory/configure --prefix=<>). It looks like some syscall functions on my machine see

Re: stupid build error

On Tue, 27 Nov 2012, Mike Stump wrote: > You failed to state a single case where a violation is caught. It's not about catching violations of law, it's about catching cases where the source tree is in an inconsistent state. And a not uncommon cause of that is that someone didn't know about the

Re: stupid build error

On Nov 27, 2012, at 4:50 PM, "Joseph S. Myers" wrote: > On Tue, 27 Nov 2012, Mike Stump wrote: > >> A review of the change and approval of the change should be enough to >> catch issues going into the FSF tree. The build should just copy the >> generated file to the source tree, if changed. T

Re: stupid build error

On Tue, 27 Nov 2012, Mike Stump wrote: > A review of the change and approval of the change should be enough to > catch issues going into the FSF tree. The build should just copy the > generated file to the source tree, if changed. The build failed for me, The rule from the FSF is that tm.tex

Re: stupid build error

On Nov 27, 2012, at 1:22 PM, Andrew Pinski wrote: > On Tue, Nov 27, 2012 at 12:55 PM, Mike Stump wrote: >> This: >> >> Verify that you have permission to grant a GFDL license for all >> new text in tm.texi, then copy it to ../../gcc/gcc/doc/tm.texi. >> make[3]: *** [s-tm-texi] Error 1 >> make[3]

Re: stupid build error

On Tue, Nov 27, 2012 at 12:55 PM, Mike Stump wrote: > This: > > Verify that you have permission to grant a GFDL license for all > new text in tm.texi, then copy it to ../../gcc/gcc/doc/tm.texi. > make[3]: *** [s-tm-texi] Error 1 > make[3]: *** Waiting for unfinished jobs…. > > is one of the stupid

stupid build error

This: Verify that you have permission to grant a GFDL license for all new text in tm.texi, then copy it to ../../gcc/gcc/doc/tm.texi. make[3]: *** [s-tm-texi] Error 1 make[3]: *** Waiting for unfinished jobs…. is one of the stupidest build errors I've seen all decade. Can someone fix it please?

Parallel build error

For the past couple of years I've simply ignored these problems by ritually adding 'echo .NOTPARALLEL: >> Makefile' to my top-level issue-the-long-configure-option scripts. But I suppose the reason why these never get fixed is no one reporting... This one happened shockingly early. $ make -j4 al

Re: revision r181278 gives me a bootstrap/build error on cygwin for gcc trunk: cc1: warning: unrecognized command line option "-Wno-narrowing"

Den 11 november 2011 16:30 skrev Jason Merrill: > On 11/11/2011 07:02 AM, Christian Jönsson wrote: >> >> revision r181278 gives me a bootstrap/build error on cygwin for gcc >> trunk like this > > I've now conditioned those functions on the macro being defined.  

Re: revision r181278 gives me a bootstrap/build error on cygwin for gcc trunk: cc1: warning: unrecognized command line option "-Wno-narrowing"

On 11/11/2011 07:02 AM, Christian Jönsson wrote: revision r181278 gives me a bootstrap/build error on cygwin for gcc trunk like this I've now conditioned those functions on the macro being defined. Does that fix it for you? Jason

Re: revision r181278 gives me a bootstrap/build error on cygwin for gcc trunk: cc1: warning: unrecognized command line option "-Wno-narrowing"

> Just to make sure nobody is midled by th subject of your message: > your bootstrap problem obviously has nothing to do with the warning itself. > The latter has been discussed already on these mailing lists, is absolutely > bening. I have open pr51094 for this bootstrap failure. Note that it is

Re: revision r181278 gives me a bootstrap/build error on cygwin for gcc trunk: cc1: warning: unrecognized command line option "-Wno-narrowing"

Hi, > revision r181278 gives me a bootstrap/build error on cygwin for gcc > trunk like this Just to make sure nobody is midled by th subject of your message: your bootstrap problem obviously has nothing to do with the warning itself. The latter has been discussed already on these mailing

revision r181278 gives me a bootstrap/build error on cygwin for gcc trunk: cc1: warning: unrecognized command line option "-Wno-narrowing"

revision r181278 gives me a bootstrap/build error on cygwin for gcc trunk like this gcc-4 -c -g -fkeep-inline-functions -DIN_GCC -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wstrict-prototypes -Wmissing-prototypes -Wmissing-format-attribute -pedantic -Wno-long-long -Wno-variadic

Re: gcc-trunk build error in OpenBSD on stage3

niXman writes: >> Why is this failing on your system? > Up to now, I've been building GCC on a different machine (the OS > wasn't installed by me). Now, I have installed OpenBSD-5.0 on the VM. > > >> Look for uses of RPATH_ENVVAR in the top level Makefile. > This line from Makefile: > RPATH_ENVVA

Re: gcc-trunk build error in OpenBSD on stage3

> Why is this failing on your system? Up to now, I've been building GCC on a different machine (the OS wasn't installed by me). Now, I have installed OpenBSD-5.0 on the VM. > Look for uses of RPATH_ENVVAR in the top level Makefile. This line from Makefile: RPATH_ENVVAR = LD_LIBRARY_PATH LD_LIBR

Re: gcc-trunk build error in OpenBSD on stage3

Diffs between stage2 and stage3. on configure libiberty for stage3 I see this warnings: configure:4962: checking for limits.hconfigure:4962: /home/root/gcc-build/build/gcc-trunk/./prev-gcc/xgcc-B/home/root/gcc-build/build/gcc-trunk/./prev-gcc/-B/usr/local/i686-pc-openbsd5.0/bin/-B/usr/local/i686-

Re: gcc-trunk build error in OpenBSD on stage3

niXman writes: > in libiberty/config.h macro HAVE_LIMITS_H is undefined. Look in libiberty/config.log to see why HAVE_LIMITS_H is not defined. Also why HAVE_STDLIB_H is not defined. Ian

gcc-trunk build error in OpenBSD on stage3

Hi list. On build gcc-trunk in OpenBSD-5.0 on staget 3 I get the following errors: if [ x"-fpic" != x ]; then \ /home/root/gcc-build/build/gcc-trunk/./prev-gcc/xgcc -B/home/root/gcc-build/build/gcc-trunk/./prev-gcc/ -B/usr/local/i686-pc-openbsd5.0/bin/ -B/usr/local/i686-pc-openbsd5.0/bin/ -B/usr

Re: Build error with USE_MD_CONSTRAINTS vs. CONST_OK_FOR_CONSTRAINT_P

Jeff Kuskin writes: > I'm trying to remove *all* single-letter constraints from my cpu.md > file and replace them with define_constraint entries that define > *multi-letter* constraint names. Example: (define_constraint "aFOO" > ...) > Am I *required* to define at least some of the single-lett

Build error with USE_MD_CONSTRAINTS vs. CONST_OK_FOR_CONSTRAINT_P

I've got a local port of GCC 4.5.0 to an in-house CPU. I'm trying to remove *all* single-letter constraints from my cpu.md file and replace them with define_constraint entries that define *multi-letter* constraint names. Example: (define_constraint "aFOO" ...) But I've found that when I remov

Re: Build Error

On 05/11/2010 02:00 PM, Diego Novillo wrote: checking libelf.h usability... yes checking libelf.h presence... yes checking for libelf.h... yes checking gelf.h usability... yes checking gelf.h presence... yes checking for gelf.h... yes checking libelf/libelf.h usability... yes checking libelf/li

Re: Build Error

On Tue, May 11, 2010 at 6:30 PM, Diego Novillo wrote: > [ Moved to gcc@gcc.gnu.org ] > Hmm, it did not detect elf_getshdrstrndx and yet it tried to use it > later on. I think that's the bug.  Yes, please file a bug.  I believe > it's going to be easy to fix, though.  There should be an unguarded >

Re: Build Error

[ Moved to gcc@gcc.gnu.org ] On Tue, May 11, 2010 at 08:46, Sandeep Soni wrote: > On Tue, May 11, 2010 at 4:53 PM, Diego Novillo wrote: >> On Tue, May 11, 2010 at 02:24, Sandeep Soni wrote: >> >>> I installed elfutils-libelf-devel-0.145-1 and that worked. >> >> Yes.  Older libelfs will not work

Re: Add new architechture in gcc build error

Thank you. I fixed the error. it caused by macro: #define ELIMINABLE_REGS \ {\ {ARG_POINTER_REGNUM,FRAME_POINTER_REGNUM}, \ {ARG_POINTER_REGNUM,STACK_POINTER_REGNUM}, \ {FRAME_POINTER_REGNUM, STACK_POINTER_REGNUM} \ } because everytime when gcc check the frame_pointer_need

Re: Add new architechture in gcc build error

daniel tian writes: >I have already finished CPU port named RICE. The previous version > I did is on gcc 4.0.2. it can be compiled. Now I wanna move it to > v4.3.0. I added the config script just as the CRX architechture. > configure:2379: $? = 1 > configure:2398: > /home/daniel.tian/gcc_

Re: Add new architechture in gcc build error

2009/9/21 Andrew Haley : > daniel tian wrote: >> 2009/9/21 sumanth : >>> Hi , >>>    Follow this wiki  " http://gcc.gnu.org/wiki/DebuggingGCC"; to know how to >>> debug gcc. >>>    As far as I know  compute_frame_pointer_to_fb_displacement is the >>> displacement between your >>>   frame pointer an

Re: Add new architechture in gcc build error

daniel tian wrote: > 2009/9/21 sumanth : >> Hi , >>Follow this wiki " http://gcc.gnu.org/wiki/DebuggingGCC"; to know how to >> debug gcc. >>As far as I know compute_frame_pointer_to_fb_displacement is the >> displacement between your >> frame pointer and the frame base ( mostly stack po

Re: Add new architechture in gcc build error

2009/9/21 sumanth : > Hi , >    Follow this wiki  " http://gcc.gnu.org/wiki/DebuggingGCC"; to know how to > debug gcc. >    As far as I know  compute_frame_pointer_to_fb_displacement is the > displacement between your >   frame pointer and the frame base ( mostly stack pointer's location after > yo

Re: Add new architechture in gcc build error

Hi , Follow this wiki " http://gcc.gnu.org/wiki/DebuggingGCC"; to know how to debug gcc. As far as I know compute_frame_pointer_to_fb_displacement is the displacement between your frame pointer and the frame base ( mostly stack pointer's location after your prologue code - depend

Re: Add new architechture in gcc build error

> > You've got to get in there with gdb and find out why > compute_frame_pointer_to_fb_displacement() > is erroring.  There's no way to avoid this. > Thank you. But I don't know how. I mean which execute file, even I can't find the "conftest.c" file. Sorry for asking this simple question.

Re: Add new architechture in gcc build error

daniel tian wrote: > /home/daniel.tian/gcc_rice_dev/rice-binutils/build-gcc-debug/./gcc/xgcc > -B/home/daniel.tian/gcc_rice_dev/rice-binutils/build-gcc-debug/./gcc/ > -B/usr/local/cross/rice-elf/rice-elf/bin/ > -B/usr/local/cross/rice-elf/rice-elf/lib/ -isystem > /usr/local/cross/rice-elf/rice-elf

Add new architechture in gcc build error

Hi, I have already finished CPU port named RICE. The previous version I did is on gcc 4.0.2. it can be compiled. Now I wanna move it to v4.3.0. I added the config script just as the CRX architechture. But when run the configure, export TARGET=rice-elf export PREFIX=/usr/local/cross/$TARGE

Re: GCC 4.4 SNAPSHOT - BUILD ERROR

> Could someone help ? Sure, there is even a mailing list: gcc-h...@gcc.gnu.org. ;-) > checking for suffix of object files... configure: error: in > `/home/meu/gcc-4.4-20090109/i686-pc-linux-gnu/libgcc': > configure: error: cannot compute suffix of object files: cannot compile > See `config.log

GCC 4.4 SNAPSHOT - BUILD ERROR

Could someone help ? I am using an Intel 430 processor and the Insigne Linux operating system. I downloaded the 20090109 snapshot and tried to compile it using gcc 4.2.3 and the most recent GMP and mpfr libraries. Everything goes well, it creates cc1, cc1dummy, collect2, cpp, gcov, gcov-dump and xg

Re: gcc-4.3.2 native build error

Chandra Prakash Garg writes: > checking for > i686-pc-linux-gnu-gcc... > /home/abhijitd/gcc/gcc-4.3.2/host-i686-pc-linux-gnu/gcc/xgcc > -B/home/abhijitd/gcc/gcc-4.3.2/host-i686-pc-linux-gnu/gcc/ > -B/home/abhijitd/gcc/gcc-4.3.2/i686-pc-linux-gnu/bin/ > -B/home/abhijitd/gcc/gcc-4.3.2/i686-pc-linu

gcc-4.3.2 native build error

Dear All, I am getting build error while building gcc-4.3.2 for native target. Error message is: + Checking multilib configuration for libgcc... Configuring stage 1 in i686-pc-linux-gnu/libgcc configure: loading cache ./config.cache checking for --enable-version-specific-runtime

gcc-4.3.2 native build error

hi All, I am getting build error while building gcc-4.3.2 for native target. Error message is: + Checking multilib configuration for libgcc... Configuring stage 1 in i686-pc-linux-gnu/libgcc configure: loading cache ./config.cache checking for --enable-version-specific-runtime

gcc-4.3.2 cross build error

Hi, I am cross compiling the gcc-4.3.2 for arm based dsp target. while building, the following error occurs. Please help us how to proceed further. Checking multilib configuration for libgcc... Configuring in dsp/libgcc .. checking for suffix of object files... con

libstdc++ build error for powerpc-elf or powerpc-eabi

Building top-of-tree g++ fails in libstdc++ compiling ctype.cc: In file included from .../gcc/libstdc++-v3/src/ctype.cc:59: .../build/lin/bld_gcc/build/powerpc-eabi/libstdc++-v3/include/powerpc-eabi/bits/ctype_noninline.h: In static member function ‘static const char* std::ctype::classic_table()

Re: objc build error

On Tue, Sep 02, 2008 at 11:43:46AM +0200, Dominique Dhumieres wrote: > Mail sent by error to [EMAIL PROTECTED]: > > I get the same error on i686-apple-darwin9 revision 139884. > > Dominique No problem building libobjc in gcc trunk r139919 (with the fix for PR37293 applied) on i686-apple-darwin9.

Re: objc build error

Mail sent by error to [EMAIL PROTECTED]: I get the same error on i686-apple-darwin9 revision 139884. Dominique

objc build error

/home/dave/gnu/gcc-4.4/objdir/./prev-gcc/xgcc -B/home/dave/gnu/gcc-4.4/objdir/./prev-gcc/ -B/home/dave/opt/gnu/gcc/gcc-4.4.0/hppa-linux/bin/ -c -g -O2 -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wcast-qual -Wold-style-definition -Wc++-compat -Wmissing-format-att

Re: build error from trunk sources

Janus Weil wrote: Building trunk rev. 139857 on linux/x86_64, I get the following failure: ... cc1: warnings being treated as errors /home/local/jweil/gcc44/trunk/gcc/sel-sched-ir.c:946: error: 'cmp_v_in_regset_pool' defined but not used I will commit the following as obvious once bootstrap fini

Re: build error from trunk sources

Building trunk rev. 139857 on linux/x86_64, I get the following failure: ... cc1: warnings being treated as errors /home/local/jweil/gcc44/trunk/gcc/sel-sched-ir.c:946: error: 'cmp_v_in_regset_pool' defined but not used ... Cheers, Janus 2008/9/1 M R Swami Reddy <[EMAIL PROTECTED]>: > Hello, >

build error from trunk sources

Hello, I am trying the build the crx-elf target gcc compiler tools from gcc trunk sources, but the below error message displayed. Could any one suggest the reason for build fail? ===Error log In file included from /trunk/gcc/sel-sched-dump.c:37: /trunk/gcc/sel-sched-ir.h:93: error: ex

[mingw] arm-elf-gcc build error with fixincludes file error

Hi, I am compiling arm-elf-gcc using mingw on Windows XP through msys, and although the C compiler compiles there is output near the end, which includes a file error for fixincludes. The file doesn't exist after the build. ... sed: Couldn't open file C:\Temp\fxinc2; FS error 2 (No such file

build Error

i am trying to build gcc-3.4.6 for that i untar gcc-ada-3.4.6 and gcc-core-3.4.6 in directory "/source" and my build directory is not subdirectory of source directory i got error like this:- gcc -c -g -O2 -gnatpg -gnata -I- -I. -Iada -I../../source/gcc-3.4.6/gcc/ada ../../source/gcc-3.4.6/g

Re: Gcc-4.1.1: Build error for arm-target

Thomas Meyer schrieb: Thomas Meyer schrieb: Thomas Meyer schrieb: Hello. I try to build a cross compiler for this target: arm-uclinux-uclibc: First the build fails because of a wrong config entry in config.gcc: This should fix this: diff --git a/gcc/config.gcc b/gcc/config.gcc index 033cc3d

Re: Gcc-4.1.1: Build error for arm-target

Thomas Meyer schrieb: Thomas Meyer schrieb: Hello. I try to build a cross compiler for this target: arm-uclinux-uclibc: First the build fails because of a wrong config entry in config.gcc: This should fix this: diff --git a/gcc/config.gcc b/gcc/config.gcc index 033cc3d..378a92d 100644 --- a/

Re: Gcc-4.1.1: Build error for arm-target

Thomas Meyer schrieb: Hello. I try to build a cross compiler for this target: arm-uclinux-uclibc: First the build fails because of a wrong config entry in config.gcc: This should fix this: diff --git a/gcc/config.gcc b/gcc/config.gcc index 033cc3d..378a92d 100644 --- a/gcc/config.gcc +++ b/gc

Gcc-4.1.1: Build error for arm-target

Hello. I try to build a cross compiler for this target: arm-uclinux-uclibc: First the build fails because of a wrong config entry in config.gcc: This should fix this: diff --git a/gcc/config.gcc b/gcc/config.gcc index 033cc3d..378a92d 100644 --- a/gcc/config.gcc +++ b/gcc/config.gcc @@ -691,7

mingw build error

Hi, Every time I build a gcc for mingw, I get the same error as reported here, http://gcc.gnu.org/ml/gcc/2006-09/msg00044.html Basically, I have to edit the Makefile in gcc/Makefile like this, -ORIGINAL_LD_FOR_TARGET = ./C:/mingw/bin/../lib/gcc/mingw32/3.4.2/../../../../mingw32/bin/ld.exe +OR

Re: build error: gcc/gcc/gimplify.c:424: internal compiler error: Segmentation fault

Daniel Franke wrote: SVN revision: 118109 Try 118110 Andreas

build error: gcc/gcc/gimplify.c:424: internal compiler error: Segmentation fault

SVN revision: 118109 Configured as: --prefix=$(installdir) --enable-bootstrap --enable-threads=posix --enable-shared --with-system-zlib --disable-nls --program-suffix=-svn --enable-languages=c,fortran Command: make bootstrap-lean Host triplet: i686-pc-linux-gnu

Re: build error

Brian Dessent <[EMAIL PROTECTED]> wrote: > > Consider posting this kind of question to gcc-help@ instead. OK, I will. > [EMAIL PROTECTED] wrote: > > > I just ran these commands: > > > > svn -q checkout svn://gcc.gnu.org/svn/gcc/trunk gcc > > mkdir builddir > > cd builddir > > CFLAGS="-

Re: build error

Consider posting this kind of question to gcc-help@ instead. [EMAIL PROTECTED] wrote: > I just ran these commands: > > svn -q checkout svn://gcc.gnu.org/svn/gcc/trunk gcc > mkdir builddir > cd builddir > CFLAGS="-g" ../gcc/configure --enable-languages=c,c++ --enable-checking \ > --disable-boot

build error

Hi, I just ran these commands: svn -q checkout svn://gcc.gnu.org/svn/gcc/trunk gcc mkdir builddir cd builddir CFLAGS="-g" ../gcc/configure --enable-languages=c,c++ --enable-checking \ --disable-bootstrap --prefix=$PWD/../prefixdir make -s make install and I got the attached compile error. Is th

RE: Question about build error

On 12 April 2006 10:14, Eric Fisher wrote: > hi, > When I build gcc-3.2.2 for mips target, there's an error. What's the > problem? > > Thanks > Eirc > > ake[1]: Leaving directory `/home/cii/qwang_gcc/libiberty' > xgcc: specs file malformed after 4096 characters > xgcc: specs file malformed afte

Question about build error

hi, When I build gcc-3.2.2 for mips target, there's an error. What's the problem? Thanks Eirc ake[1]: Leaving directory `/home/cii/qwang_gcc/libiberty' xgcc: specs file malformed after 4096 characters xgcc: specs file malformed after 4096 characters xgcc: specs file malformed after 4096 character

Re: GCC 4.1.0 build error (as doesn't like code produced by xgcc)

Hi, On Wed, Mar 29, 2006 at 09:31:26AM -0500, Daniel Jacobowitz wrote: > On Tue, Mar 28, 2006 at 03:10:30PM +0200, Clifford Wolf wrote: > > /tmp/cc9Aywrx.s: Assembler messages: > > /tmp/cc9Aywrx.s:1256: Error: can't resolve `.text.unlikely' > > {.text.unlikely section} - `.LCFI70' {.text sect

Re: GCC 4.1.0 build error (as doesn't like code produced by xgcc)

On Tue, Mar 28, 2006 at 03:10:30PM +0200, Clifford Wolf wrote: > /tmp/cc9Aywrx.s: Assembler messages: > /tmp/cc9Aywrx.s:1256: Error: can't resolve `.text.unlikely' {.text.unlikely > section} - `.LCFI70' {.text section} The assembly is wrong. File a GCC bug. Two subtracted symbols should gen

GCC 4.1.0 build error (as doesn't like code produced by xgcc)

Hi, I have an interesting problem with compiling gcc 4.1.0 on i386-unknown-linux-gnu. Building xgcc (with gcc 3.4.3) works fine. But rebuilding the compiler with xgcc the 2nd time (with -fprofile-use) fails with an assembler error: $ stage1/xgcc -Bstage1/ -B/usr/i386-unknown-linux-gnu/bin/ -c

Re: Build error on trunk due to new ./configure

Andrew (and everybody else), I upgraded autoconf because the build crashed when I tried to regenerate the fortran library. There were already symbols present that were not recognised by my autoconf (I kept no record of which - it was the default with FC3). I upgraded to the version recommen

Re: Build error on trunk due to new ./configure

Andrew Pinski wrote: On Mar 14, 2006, at 8:54 AM, Jan-Benedict Glaw wrote: Among other differences, it decides that we're cross-building, which isn't true in this case. This results in vax-linux-uclibc-gcc being used to build libiberty for the build system (which is i686-linux-gnu). No wonder

Re: Build error on trunk due to new ./configure (was: r112028 - in /trunk: configure gcc/fortran/Chan...)

On Tue, 2006-03-14 08:56:38 -0500, Andrew Pinski <[EMAIL PROTECTED]> wrote: > On Mar 14, 2006, at 8:54 AM, Jan-Benedict Glaw wrote: > >Among other differences, it decides that we're cross-building, which > >isn't true in this case. This results in vax-linux-uclibc-gcc being > >used to build libiber

Re: Build error on trunk due to new ./configure (was: r112028 - in /trunk: configure gcc/fortran/Chan...)

On Mar 14, 2006, at 8:54 AM, Jan-Benedict Glaw wrote: Among other differences, it decides that we're cross-building, which isn't true in this case. This results in vax-linux-uclibc-gcc being used to build libiberty for the build system (which is i686-linux-gnu). No wonder that `genmode' cannot

Build error on trunk due to new ./configure (was: r112028 - in /trunk: configure gcc/fortran/Chan...)

On Tue, 2006-03-14 09:56:40 +0100, Jan-Benedict Glaw <[EMAIL PROTECTED]> wrote: > On Mon, 2006-03-13 22:49:57 -, [EMAIL PROTECTED] <[EMAIL PROTECTED]> > wrote: > # Guess values for system-dependent variables and create Makefiles. > -# Generated automatically using autoconf version 2.13 > -#

Re: 4.0-20050319 / 4-020050402 build error due to --enable-mapped location

René Rebe wrote: ../../gcc/tree-cfg.c: In function `remove_bb': ../../gcc/tree-cfg.c:2062: error: invalid type argument of `unary *' This was fixed on mainline on March 7. Is --enable-mapped-location considered to be a functional in 4.0 ? Apparently no. The fixes have not been backported to the gc

4.0-20050319 / 4-020050402 build error due to --enable-mapped location

Hi all, I tried --enable-mapped-location on recent snapshots and wonder if that is intended to build: ../configure --enable-languages="c,c++" --disable-checking --enable-__cxa_atexit --enable-mapped-location and a make yields: ../../gcc/tree-cfg.c: In function `remove_bb': ../../gcc/tree-cfg