From: Ralf Baechle <ralf@oss.sgi.com>
To: Jun Sun <jsun@mvista.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: gcc : ... is greater than maximum object file alignment
Date: Wed, 25 Oct 2000 02:41:56 +0200 [thread overview]
Message-ID: <20001025024156.B10792@bacchus.dhis.org> (raw)
In-Reply-To: <39F626C9.96146652@mvista.com>; from jsun@mvista.com on Tue, Oct 24, 2000 at 05:18:17PM -0700
On Tue, Oct 24, 2000 at 05:18:17PM -0700, Jun Sun wrote:
> I looked carefully again at the output for building glibc, and I found
> the following warnings. If I remembered correctly, Ralf has already
> fixed a similar problem a while back. Maybe it is not in the patch
> file? I am using egcs-1.0.3a-2.diff.gz on oss.sgi.com site.
>
> pthread.c:31: warning: alignment of `__pthread_initial_thread' is
> greater than maximum object file alignment
> pthread.c:62: warning: alignment of `__pthread_manager_thread' is
> greater than maximum object file alignment
The fix was only available as part of the cross-egcs-1.0.3a-2 package but
not us unbundled patch. It's now available there. Note that the
native compiler also isn't based on this latest patch.
Ralf
prev parent reply other threads:[~2000-10-25 0:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-25 0:18 gcc : ... is greater than maximum object file alignment Jun Sun
2000-10-25 0:41 ` Ralf Baechle [this message]
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=20001025024156.B10792@bacchus.dhis.org \
--to=ralf@oss.sgi.com \
--cc=jsun@mvista.com \
--cc=linux-mips@oss.sgi.com \
/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