Re: This is a Cygwin failure yeah?
On 10/01/2009, Bernd Roesch wrote: > Hello Dave > >> Unix commad for stack increase(forget the name) > > > > 'ulimit' > > > ah yes i see, I update from time and time and now its more.my bash show this > now.Maybe Andy can do this test what his bash show. > > $ ulimit -a > core file size (blocks, -c) unlimited > data seg size (kbytes, -d) unlimited > file size (blocks, -f) unlimited > open files (-n) 256 > pipe size(512 bytes, -p) 8 > stack size (kbytes, -s) 2033 > cpu time (seconds, -t) unlimited > max user processes (-u) 63 > virtual memory (kbytes, -v) 2097152 > > For me I get: $ ulimit -a core file size (blocks, -c) unlimited data seg size (kbytes, -d) unlimited file size (blocks, -f) unlimited open files (-n) 256 pipe size(512 bytes, -p) 8 stack size (kbytes, -s) 2033 cpu time (seconds, -t) unlimited max user processes (-u) 63 virtual memory (kbytes, -v) 2097152 Thanks for the replies and sorry for my late answer - away from keyboard :-) I'm picking this back up now though. Andy -- Brain upgrade required: a working hypothalamus
Re: This is a Cygwin failure yeah?
Dave Korn wrote: > Andy Scott wrote: >> ../../../gcc/libiberty/strsignal.c -o strsignal.o >> ../../../gcc/libiberty/strsignal.c:408: error: conflicting types for >> 'strsignal' >> /usr/include/string.h:78: note: previous declaration of 'strsignal' was here >> make[2]: *** [strsignal.o] Error 1 >> make[2]: Leaving directory >> `/home/andy/live-gcc/my_gcc/i686-pc-cygwin/libiberty' >> make[1]: *** [all-target-libiberty] Error 2 >> make[1]: Leaving directory `/home/andy/live-gcc/my_gcc' >> make: *** [all] Error 2 >> >> Which seems like a possible setup/build issue. If this is so anyone >> seen it before and any helpful hints on how to get rid of it? > > Looks like newlib has a non-posix-compliant definition of strsignal. If > you take a look at the header file, it seems GDB has a problem with it too: > > /tmp/binutils/binutils-2.19/ld $ cat -n /usr/include/string.h | grep -C4 78 > 74 char*_EXFUN(strlwr,(char *)); > 75 char*_EXFUN(strupr,(char *)); > 76 #ifdef __CYGWIN__ > 77 #ifndef DEFS_H /* Kludge to work around problem compiling in gdb */ > 78 const char *_EXFUN(strsignal, (int __signo)); > 79 #endif > 80 int _EXFUN(strtosigno, (const char *__name)); > 81 #endif > 82 > /tmp/binutils/binutils-2.19/ld $ > > ... maybe just adding -DDEFS_H to your CFLAGS would be a work-around. Hmm, > given that Cygwin supports strsignal, this bit of libiberty shouldn't be being > compiled, because configure should have defined HAVE_STRSIGNAL. On my local > build of 4.3.2, this works correctly: "nm libiberty/strsignal.o" shows the > function isn't defined, and HAVE_STRSIGNAL is defined in config.h. Have a > look through libiberty/config.log and see if you can figure out why it isn't > defined; maybe it's even something to do with the earlier crash? I've now run into this locally and am debugging it. I think that the definition or possibly even existence of strsignal in cygwin may have shifted the ground slightly under libiberty's feet. cheers, DaveK
correct place for code.
Hi,
I need to make a test expanded from ASM_OUTPUT_LABEL_REF that is
language dependent (on objc/objcxx).
It's not clear where the best/proper place to put the code is.
if I put it in {stub,act}-objc.c that's fine for c, c++, objc and
objc++ ...
... but it means that stub-objc then needs to be linked with jc1 and
f951
... and anyway the test is target-specific so perhaps it belongs
better somewhere in config/...
if I put it in config/target.c then the c_dialect variable
(c_language) is not available from jc1 or f951 - although,
obviously, a dummy definition could be made to satisfy the reference.
Is there a "best practice" or "known way" to solve this?
cheers,
Iain
gcc binary download
Hi, I cannot find where to download gcc binary for Linux. Can you email me the link? It's so confusing in the http://gcc.gnu.org/ web site. Thanks, simon
Re: Installing GCC:Configuration (GCC-4.3.2)
On Tue, 2009-01-13 at 16:48 -0500, Franklyn Simon wrote: > I download gcc-g++4.3.2 and uncompressed it along with the > prerequisites tar files in directory (/opt). I am confused as to the > srcdir and objdir mentioned in Install GCC: Configuration. You should take this question to gcc-h...@gcc.gnu.org. This list is for discussing GCC development, not installing GCC. Thanks. Ben
Re: gcc binary download
> I cannot find where to download gcc binary for Linux. Can you email me > the link? It's so confusing in the http://gcc.gnu.org/ web site. You should install gcc from your Linux distribution. It will be far easier. Ben
gcc-4.2-20090114 is now available
Snapshot gcc-4.2-20090114 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/4.2-20090114/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 4.2 SVN branch with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-4_2-branch revision 143385 You'll find: gcc-4.2-20090114.tar.bz2 Complete GCC (includes all of below) gcc-core-4.2-20090114.tar.bz2 C front end and core compiler gcc-ada-4.2-20090114.tar.bz2 Ada front end and runtime gcc-fortran-4.2-20090114.tar.bz2 Fortran front end and runtime gcc-g++-4.2-20090114.tar.bz2 C++ front end and runtime gcc-java-4.2-20090114.tar.bz2 Java front end and runtime gcc-objc-4.2-20090114.tar.bz2 Objective-C front end and runtime gcc-testsuite-4.2-20090114.tar.bz2The GCC testsuite Diffs from 4.2-20090107 are available in the diffs/ subdirectory. When a particular snapshot is ready for public consumption the LATEST-4.2 link is updated and a message is sent to the gcc list. Please do not use a snapshot before it has been announced that way.
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 xgcc, but it shows the error "cannot compute suffix of object files: cannot compile". See below the complete message: 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-libs... no checking for a BSD-compatible install... /usr/bin/install -c checking for gawk... no checking for mawk... mawk checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking for i686-pc-linux-gnu-ar... ar checking for i686-pc-linux-gnu-lipo... lipo checking for i686-pc-linux-gnu-nm... /home/meu/gcc-4.4-20090109/host-i686-pc-linux-gnu/gcc/nm checking for i686-pc-linux-gnu-ranlib... ranlib checking for i686-pc-linux-gnu-strip... strip checking whether ln -s works... yes checking for i686-pc-linux-gnu-gcc... /home/meu/gcc-4.4-20090109/host-i686-pc-linux-gnu/gcc/xgcc -B/home/meu/gcc-4.4-20090109/host-i686-pc-linux-gnu/gcc/ -B/usr/local/i686-pc-linux-gnu/bin/ -B/usr/local/i686-pc-linux-gnu/lib/ -isystem /usr/local/i686-pc-linux-gnu/include -isystem /usr/local/i686-pc-linux-gnu/sys-include 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' for more details. make[2]: ** [configure-stage1-target-libgcc] Erro 1 make[2]: Leaving directory `/home/meu/gcc-4.4-20090109' make[1]: ** [stage1-bubble] Erro 2 make[1]: Leaving directory `/home/meu/gcc-4.4-20090109' make: ** [all] Erro 2 I had never got a configure error before. Does someone know what I could do? Both 20090109 and 20090102 snapshots show this error. Veja quais são os assuntos do momento no Yahoo! +Buscados http://br.maisbuscados.yahoo.com
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' for more details. > I had never got a configure error before. Does someone know what I could do? You need to take a look inside config.log; it will provide more details about by the compiler failed to build those target objects. Cheers, Ben
Re: correct place for code.
IainS writes:
> I need to make a test expanded from ASM_OUTPUT_LABEL_REF that is
> language dependent (on objc/objcxx).
>
> It's not clear where the best/proper place to put the code is.
>
> if I put it in {stub,act}-objc.c that's fine for c, c++, objc and
> objc++ ...
> ... but it means that stub-objc then needs to be linked with jc1 and
> f951
> ... and anyway the test is target-specific so perhaps it belongs
> better somewhere in config/...
>
> if I put it in config/target.c then the c_dialect variable
> (c_language) is not available from jc1 or f951 - although,
> obviously, a dummy definition could be made to satisfy the reference.
>
> Is there a "best practice" or "known way" to solve this?
In general this can not be done. gcc has a pretty strong split
between the frontend and the backend. You can't refer to frontend
structures in the backend.
It's pretty hard to think of any reason why something as low-level as
ASM_OUTPUT_LABEL_REF would want to look at anything in the frontend.
You are probably working at the wrong level.
Ian
