From: "Nick England" <nickengland@gmail.com>
To: gcc-help@gcc.gnu.org
Subject: Compiling instructions unclear gcc-4.3.0
Date: Fri, 06 Jun 2008 14:51:00 -0000 [thread overview]
Message-ID: <de097d770806060750t53b46d8bh5a96f509420a4147@mail.gmail.com> (raw)
the instructions on http://gcc.gnu.org/install/configure.html
say:
To configure GCC:
% mkdir objdir
% cd objdir
% srcdir/configure [options] [target]
However, in the insctutions on building it only says to do a make.
If I do a make in objdir I get "make: *** No targets specified and no
makefile found. Stop."
If I do a make in the srcdir then I am building in the srcdir, which
the instructions advise against.
What is the correct command to run to build GCC in a non-src dir?
gcc-4.3.0:
(Incidently I get an error message when building in the src dir
Many similar lines saying functions are mulitpliy defined
....
libs/in_unpack_generic.o: In function `putc_unlocked':
/usr/include/bits/stdio.h:87: multiple definition of `putc_unlocked'
.libs/backtrace.o:/usr/include/bits/stdio.h:87: first defined here
.libs/in_unpack_generic.o: In function `fputc_unlocked':
/usr/include/bits/stdio.h:77: multiple definition of `fputc_unlocked'
.libs/backtrace.o:/usr/include/bits/stdio.h:77: first defined here
.libs/in_unpack_generic.o: In function `putchar':
/usr/include/bits/stdio.h:68: multiple definition of `putchar'
.libs/backtrace.o:/usr/include/bits/stdio.h:68: first defined here
.libs/in_unpack_generic.o: In function `getchar_unlocked':
/usr/include/bits/stdio.h:59: multiple definition of `getchar_unlocked'
.libs/backtrace.o:/usr/include/bits/stdio.h:59: first defined here
.libs/in_unpack_generic.o: In function `getc_unlocked':
/usr/include/bits/stdio.h:52: multiple definition of `getc_unlocked'
.libs/backtrace.o:/usr/include/bits/stdio.h:52: first defined here
.libs/in_unpack_generic.o: In function `getchar':
/usr/include/bits/stdio.h:43: multiple definition of `getchar'
.libs/backtrace.o:/usr/include/bits/stdio.h:43: first defined here
.libs/in_unpack_generic.o: In function `vprintf':
/usr/include/bits/stdio.h:36: multiple definition of `vprintf'
.libs/backtrace.o:/usr/include/bits/stdio.h:36: first defined here
collect2: ld returned 1 exit status
make[3]: *** [libgfortran.la] Error 1
)
Help would be apprechiated!
next reply other threads:[~2008-06-06 14:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-06 14:51 Nick England [this message]
2008-06-06 14:57 ` Andrew Haley
2008-06-06 15:04 ` Eljay Love-Jensen
2008-06-06 15:05 ` Nick England
2008-06-06 15:14 ` Eljay Love-Jensen
2008-06-06 15:24 ` Nick England
2008-06-06 19:44 ` Brian Dessent
2008-06-10 12:55 ` Nick England
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=de097d770806060750t53b46d8bh5a96f509420a4147@mail.gmail.com \
--to=nickengland@gmail.com \
--cc=gcc-help@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).