public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Svein E. Seldal" <Svein.Seldal@solidas.com>
To: gcc <gcc@gcc.gnu.org>
Subject: Problems compiling gcc 3.3 on cygwin
Date: Sat, 05 Apr 2003 02:07:00 -0000	[thread overview]
Message-ID: <3E8E1A99.5030907@solidas.com> (raw)

Hello,

I am trying to compile the gcc-3_3-branch under cygwin (for the tic4x
target), but it fails.  To verify the bug I have also checked out an old
gcc from the date 20030315 (because I did successfully compile gcc at
that date). But both compilation did fail. I have also tried to compile
gcc as a native compiler, but it still fails. Compilation of any other 
cross compiler also fails.

I am running Windows XP, cygwin 1.3.22-1, gcc 3.2-3 (20020927) and
binutils 20030307-1. I fear that this bug is present on my system only.
Can anyone else running cygwin please confirm or reject the problems I'm
having? Any suggestions to fix the problem would be very welcome...

I think its very strange, because I did not have that problem when I
compiled gcc 3.3 in the 15th march, but now I do -- using the very same
code.


Thanks,
Svein


Snapshot from "make":

gcc -DIN_GCC -DHAVE_CONFIG_H -O2 -DIN_GCC -DCROSS_COMPILE -W -Wall
-Wwrite-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/fixinc
-I../../../gcc/fixinc/.. -I../../../gcc/fixinc/../config
-I../../../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):gnu-regex.c: undefined reference to `___mempcpy'
collect2: ld returned 1 exit status
make[2]: *** [full-stamp] Error 1
make[2]: Leaving directory
`/cygdrive/d/Prosjekt/gnu/gcc-3.3-branch/build.inst.tic4x/gcc/fixinc'
make[1]: *** [fixinc.sh] Error 2
make[1]: Leaving directory
`/cygdrive/d/Prosjekt/gnu/gcc-3.3-branch/build.inst.tic4x/gcc'
make: *** [all-gcc] Error 2


... but if I grep the configure output, the following is printed:

checking for getgid... yes
checking for getuid... yes
checking for mempcpy... yes
checking for munmap... yes
checking for putenv... (cached) yes
checking for setenv... (cached) yes


             reply	other threads:[~2003-04-04 23:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-05  2:07 Svein E. Seldal [this message]
     [not found] <3E8E1A99.5030907%40solidas.com>
2003-04-25 14:09 ` Øyvind Harboe
2003-04-25 17:01   ` Kaveh R. Ghazi
2003-04-25 20:32 Øyvind Harboe
2003-04-25 21:38 Øyvind Harboe

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=3E8E1A99.5030907@solidas.com \
    --to=svein.seldal@solidas.com \
    --cc=gcc@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).