From: Ian Lance Taylor <iant@google.com>
To: cihan <cihan@enderunix.org>
Cc: gcc-help@gcc.gnu.org
Subject: Re: gcc 2.95.3 building problem
Date: Thu, 14 Aug 2008 04:05:00 -0000 [thread overview]
Message-ID: <m3r68sk6gx.fsf@google.com> (raw)
In-Reply-To: <48A32619.8060708@enderunix.org> (cihan@enderunix.org's message of "Wed\, 13 Aug 2008 21\:21\:13 +0300")
cihan <cihan@enderunix.org> writes:
> In file included from /usr/include/sys/types.h:270,
> from /usr/include/stdlib.h:320,
> from ./libgcc2.c:41:
> /usr/include/bits/pthreadtypes.h:69: warning: unnamed struct/union
> that defines no instances
This looks like gcc 2.95.3 can't compile your C library.
/usr/include/bits/pthreadtypes.h is not part of gcc.
> ./frame.c:55: extra brace group at end of initializer
> ./frame.c:55: (near initialization for `object_mutex.__data')
> ./frame.c:55: warning: excess elements in struct initializer
> ./frame.c:55: warning: (near initialization for `object_mutex.__data')
This is an attempt to use PTHREAD_MUTEX_INIT, and it looks like your C
library defines it in a way which gcc 2.95.3 can't handle.
In short, you are in a world of pain. Why do you want gcc 2.95.3
anyhow?
Ian
next prev parent reply other threads:[~2008-08-13 20:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-12 20:32 cihan
2008-08-12 20:54 ` Ian Lance Taylor
2008-08-13 19:47 ` cihan
2008-08-14 4:05 ` Ian Lance Taylor [this message]
2008-08-14 19:01 ` cihan
2008-08-14 21:42 ` Ian Lance Taylor
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=m3r68sk6gx.fsf@google.com \
--to=iant@google.com \
--cc=cihan@enderunix.org \
--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).