public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: areuwho@freenet.de
To: gcc-gnats@gcc.gnu.org
Subject: bootstrap/10140: Cross-compiling gcc 3.3 for sh-elf: gnu-regex.c:undefined reference to: ___mempcpy
Date: Tue, 18 Mar 2003 20:26:00 -0000	[thread overview]
Message-ID: <20030318202418.24876.qmail@sources.redhat.com> (raw)


>Number:         10140
>Category:       bootstrap
>Synopsis:       Cross-compiling gcc 3.3 for sh-elf: gnu-regex.c:undefined reference to: ___mempcpy
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Mar 18 20:26:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     areuwho@freenet.de
>Release:        gcc-3.3 (snapshot 20030317)
>Organization:
>Environment:
linux-2.4.19, host binutils 2.13.2.1, host gcc 2.95.2 (also tried with 3.3)
>Description:
I'm having trouble cross-compiling the newest gcc-snapshot for the sh-elf (dreamcast) target. Here's my configure:

In the BUILD-GCC directory:

../gcc-20030317/configure --target=sh-elf --prefix=/usr/local/dc --without-headers --with-newlib --enable-languages=c

after typing make all, it gives me this output after compiling various things:

make[2]: Entering directory `/gcc/build-gcc/gcc/fixinc'
gcc -DIN_GCC -DHAVE_CONFIG_H -g -O2 -DIN_GCC -DCROSS_COMPILE -W -Wall -Wwrit
e-strings -Wstrict-prototypes -Wmissing-prototypes -Wtraditional -pedantic -
Wno-long -long -DHAVE_CONFIG_H -DGENERATOR_FILE  -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wtraditional -pedantic -Wno-long-long  -I. -I.. -I../../../gcc-20030317/gcc/fixinc -I../../../gcc-20030317/gcc/fixinc/.. -I../../../gcc-20030317/gcc/fixinc/../config -I../../../gcc-2003031
7/gcc/fixinc/../../include  -o fixincl.exe fixincl.o fixtests.o fixfixes.o server.o procopen.o gnu-regex.o fixlib.o ../../libiberty/libiberty.a
gnu-regex.o(.text+0x6556): In function `regerror':
/gcc/build-gcc/gcc/fixinc/../../../gcc-20030317/gcc/fixinc/gnu-regex.c:5723:undefined reference to `___mempcpy'
collect2: ld returned 1 exit status
make[2]: *** [full-stamp] Error 1
make[2]: Leaving directory `/gcc/build-gcc/gcc/fixinc'
make[1]: *** [fixinc.sh] Error 2
make[1]: Leaving directory `/gcc/build-gcc/gcc'
make: *** [all-gcc] Error 2

I also successfully compiled the binutils (2.13.2.1) for the sh-elf target

I was following the tutorial on
http://www.hangar-eleven.de/en/devdc-index.html , except I replaced binutils-2.11.2 with version 2.13.2.1 and gcc-3.0.4 with gcc-3.3 (snapshot 20030317)
>How-To-Repeat:
reply to paras DOT rasmatazz AT gmx DOT net please
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2003-03-18 20:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-18 20:26 areuwho [this message]
2003-03-19 12:56 Paras Rasmatazz
2003-04-25 15:17 ghazi

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=20030318202418.24876.qmail@sources.redhat.com \
    --to=areuwho@freenet.de \
    --cc=gcc-gnats@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).