From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: FX <fxcoudert@gmail.com>
Cc: gcc-patches@gcc.gnu.org, gfortran List <fortran@gcc.gnu.org>
Subject: Re: [patch] Separate {OS,CPU}_CPP_BUILTINS macros into C-family and language-independent macros
Date: Thu, 07 Oct 2010 11:14:00 -0000 [thread overview]
Message-ID: <yddtykyqmq4.fsf@manam.CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <4D88077B-3233-4D15-94E6-13BE58D29AD5@gmail.com> (FX's message of "Thu, 7 Oct 2010 12:49:34 +0200")
FX <fxcoudert@gmail.com> writes:
> I also tried to build cross-compilers for the following i386-pc-interix3 and alpha-dec-osf5.1, but they failed to build even without my patch:
>
> -- i386-pc-interix3 fails to build winnt.c over use of undeclared use_pe_aligned_common()
> -- alpha-dec-osf5.1 fails to build mips-tfile.o
>
> Rainer (as osf maintainer) is CC'ed to this mail. Interix hasn't seen a specific patch for it (not part of mechanical changes) since 2003, and I don't know whom to forward this information to.
I'll have a look, but the mips-tfile.o failure (known problem, cf. PR
target/3746) shouldn't matter: mips-tfile is only used to introduce
debug info into object files (not possible with the native as, and gas
doesn't currently work on Tru64 UNIX). Simpy build cc1 and test that.
Thanks.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
next prev parent reply other threads:[~2010-10-07 11:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-07 10:49 FX
2010-10-07 11:14 ` Rainer Orth [this message]
2010-10-07 12:31 ` FX
2010-10-07 12:46 ` FX
2010-10-08 8:56 ` Tobias Burnus
2010-10-08 20:29 ` Rainer Orth
2010-10-16 19:44 ` Tobias Burnus
2010-10-20 22:34 ` FX
2010-11-03 21:29 FX
2010-11-03 22:34 ` Weddington, Eric
2010-11-03 22:35 ` FX
2010-11-04 17:05 ` Rainer Orth
2010-11-06 0:06 ` Jerry DeLisle
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=yddtykyqmq4.fsf@manam.CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--cc=fortran@gcc.gnu.org \
--cc=fxcoudert@gmail.com \
--cc=gcc-patches@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).