From: "Øyvind Harboe" <oyvind.harboe@zylin.com>
To: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
Cc: <Svein.Seldal@solidas.com>, <gcc@gcc.gnu.org>
Subject: RE: Problems compiling gcc 3.3 on cygwin
Date: Fri, 25 Apr 2003 21:38:00 -0000 [thread overview]
Message-ID: <41D1051F31A2674C99E41CA28EE734980A1FD0@isp-ex2k.intellimade.net> (raw)
> > gnu-regex.o(.text+0x6556):gnu-regex.c: undefined reference
> to `___mempcpy'
>
> I fixed this on 4/15 for 3.3 and trunk, try cvs from 4/16 or later.
>
> Nobody tested it for me on cygwin so it became too late to
> apply it for 3.2.x. However you can manually copy and apply
> the patch to your private 3.2.3 source tree from here:
>
>http://gcc.gnu.org/ml/gcc/2003-04/msg00538.html
The next stop was:
[stuff deleted]
/cygdrive/c/ssh/arm/build-gcc/gcc/xgcc -shared-libgcc -B/cygdrive/c/ssh/arm/buil
d-gcc/gcc/ -nostdinc++ -L/cygdrive/c/ssh/arm/build-gcc/arm-elf/thumb/libstdc++-v
3/src -L/cygdrive/c/ssh/arm/build-gcc/arm-elf/thumb/libstdc++-v3/src/.libs -B/cy
gdrive/c/ssh/arm/install/arm-elf/bin/ -B/cygdrive/c/ssh/arm/install/arm-elf/lib/
-isystem /cygdrive/c/ssh/arm/install/arm-elf/include -mthumb -I../../../../../g
cc-3.2.3/libstdc++-v3/../gcc -I../../../../../gcc-3.2.3/libstdc++-v3/../include
-I/cygdrive/c/ssh/arm/build-gcc/arm-elf/thumb/libstdc++-v3/include/arm-elf -I/cy
gdrive/c/ssh/arm/build-gcc/arm-elf/thumb/libstdc++-v3/include -I../../../../../g
cc-3.2.3/libstdc++-v3/libsupc++ -g -O2 -mthumb -fno-implicit-templates -Wall -Wn
o-format -W -Wwrite-strings -Winline -fdiagnostics-show-location=once -g -c ../.
./../../../gcc-3.2.3/libstdc++-v3/libsupc++/eh_alloc.cc -o eh_alloc.o
In file included from ../../../../../gcc-3.2.3/libstdc++-v3/libsupc++/eh_alloc.c
c:33:
/cygdrive/c/ssh/arm/build-gcc/arm-elf/thumb/libstdc++-v3/include/cstdlib:86: `
div_t' not declared
/cygdrive/c/ssh/arm/build-gcc/arm-elf/thumb/libstdc++-v3/include/cstdlib:87: `
ldiv_t' not declared
/cygdrive/c/ssh/arm/build-gcc/arm-elf/thumb/libstdc++-v3/include/cstdlib:97: `
div' not declared
/cygdrive/c/ssh/arm/build-gcc/arm-elf/thumb/libstdc++-v3/include/cstdlib:102: `
ldiv' not declared
/cygdrive/c/ssh/arm/build-gcc/arm-elf/thumb/libstdc++-v3/include/cstdlib:104: `
mblen' not declared
/cygdrive/c/ssh/arm/build-gcc/arm-elf/thumb/libstdc++-v3/include/cstdlib:105: `
mbstowcs' not declared
/cygdrive/c/ssh/arm/build-gcc/arm-elf/thumb/libstdc++-v3/include/cstdlib:106: `
mbtowc' not declared
/cygdrive/c/ssh/arm/build-gcc/arm-elf/thumb/libstdc++-v3/include/cstdlib:115: `
wcstombs' not declared
/cygdrive/c/ssh/arm/build-gcc/arm-elf/thumb/libstdc++-v3/include/cstdlib:116: `
wctomb' not declared
/cygdrive/c/ssh/arm/build-gcc/arm-elf/thumb/libstdc++-v3/include/cstdlib:122: sy
ntax
error before `(' token
make[6]: *** [eh_alloc.lo] Error 1
make[6]: Leaving directory `/cygdrive/c/ssh/arm/build-gcc/arm-elf/thumb/libstdc+
+-v3/libsupc++'
make[5]: *** [all-recursive] Error 1
make[5]: Leaving directory `/cygdrive/c/ssh/arm/build-gcc/arm-elf/thumb/libstdc+
+-v3'
make[4]: *** [all-recursive-am] Error 2
make[4]: Leaving directory `/cygdrive/c/ssh/arm/build-gcc/arm-elf/thumb/libstdc+
+-v3'
make[3]: *** [multi-do] Error 1
make[3]: Leaving directory `/cygdrive/c/ssh/arm/build-gcc/arm-elf/libstdc++-v3'
make[2]: *** [all-multi] Error 2
make[2]: Leaving directory `/cygdrive/c/ssh/arm/build-gcc/arm-elf/libstdc++-v3'
make[1]: *** [all-recursive-am] Error 2
make[1]: Leaving directory `/cygdrive/c/ssh/arm/build-gcc/arm-elf/libstdc++-v3'
make: *** [all-target-libstdc++-v3] Error 2
Øyvind Harboe
next reply other threads:[~2003-04-25 20:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-25 21:38 Øyvind Harboe [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-04-25 20:32 Øyvind Harboe
[not found] <3E8E1A99.5030907%40solidas.com>
2003-04-25 14:09 ` Øyvind Harboe
2003-04-25 17:01 ` Kaveh R. Ghazi
2003-04-05 2:07 Svein E. Seldal
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=41D1051F31A2674C99E41CA28EE734980A1FD0@isp-ex2k.intellimade.net \
--to=oyvind.harboe@zylin.com \
--cc=Svein.Seldal@solidas.com \
--cc=gcc@gcc.gnu.org \
--cc=ghazi@caip.rutgers.edu \
/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).