Thread View: gnu.g++.help
1 messages
1 total messages
Started by bryan d oakley
Fri, 13 Nov 1992 00:35
duh, help
Author: bryan d oakley
Date: Fri, 13 Nov 1992 00:35
Date: Fri, 13 Nov 1992 00:35
55 lines
3213 bytes
3213 bytes
Ok, I got gcc and g++ to compile on my machine no problemo.
Configuration: sun 386i, sunos 4.0.2. I have an (IMHO) impressive
string of successes with emacs, ghostscript, and other GNU stuff. I
just tried to build libg++ and it won't build. Similar problem with
GDB. Fresh out of the box the configure script can't seem to find my
gcc, not that it really matters. I manually edit the makefile but the
darn thing still won't compile. Any suggestions?
It appears that the auto configure script assumes everything is in the
same tree (that ${rootme}/../gcc/gcc stuff looks somewhat suspect to
me...). My gcc is in /opt/bin/sun386, with libraries in /opt/lib.
I'm installing from /opt/src/libg++-2.2 from which gcc is NOT
subordinate. What am I doing wrong?
For the record, here is what I get when I did the make:
<everything's ok for a while... then>
ranlib libiberty.a
rootme=`pwd` ; export rootme; CC="gcc `if [ -f ${rootme}/../gcc/gcc ] ; then echo -I${rootme}/../gcc/include ; else echo ; fi`"; export CC; \
./utils/gen-params >tmp-params.h
In file included from dummy.c:4:
/usr/include/stdio.h:25: warning: `NULL' redefined
/opt/lib/gcc-lib/sun386/2.2.2/include/stddef.h:137: warning: this is the location of the previous definition
mv tmp-params.h _G_config.h
gcc -g -nostdinc++ -I.. -I. -I./../iostream -I./../g++-include -c AllocRing.cc
In file included from ./std.h:26, from AllocRing.cc:22:
./../g++-include/string.h:28: declaration of `int strlen (const char *)'
<built-in>:0: conflicts with built-in declaration `long unsigned int strlen (const char *)'
*** Error code 1
make: Fatal error: Command failed for target `AllocRing.o'
Current working directory /opt/src/libg++-2.2/libg++/src
*** Error code 1
make: Fatal error: Command failed for target `in-src'
Current working directory /opt/src/libg++-2.2/libg++
*** Error code 1
make: Fatal error: Command failed for target `all-libg++'
Am I wrong in the assumption that if gcc and g++ compiled ok that it
should compile libg++ properly, or do I need to do something here?
For a long time I was really impressed by how 'easy' it was to port
the GNU software, until I got gdb and libg++ (the only two things I've
tried to compile with the automatic configure script).
Oh, when I did the configure I just entered './config sun386
-path=/opt'. I tried the -lang=gcc but got an illegal option error.
*SIGH* I would appreciate any help anyone can give. I'm havin' too
much fun to quit now...:-)
Thanks.
--
----------------------------------------------------------------------
Instrument Approach Procedures Automation DOT/FAA/AMI-230
----------------------------------------------------------------------
Bryan D. Oakley ctrbdo%iapa@mailhost.ecn.uoknor.edu
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads