public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: NightStrike <nightstrike@gmail.com>
Cc: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>,
	Tobias Burnus <burnus@net-b.de>,
	       gcc-patches@gcc.gnu.org, fortran@gcc.gnu.org
Subject: Re: [fortran, build] Fix libquadmath build on Solaris 2
Date: Mon, 22 Nov 2010 19:39:00 -0000	[thread overview]
Message-ID: <yddr5ed5hp7.fsf@manam.CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <AANLkTi=+6dDTLpupM-y_Y35sc1ikvD-gjM-FMCdvqCmU@mail.gmail.com>	(nightstrike@gmail.com's message of "Mon, 22 Nov 2010 13:33:03 -0500")

NightStrike <nightstrike@gmail.com> writes:

>> Fully agreed.  It seems to me that the first step has to be to
>> generalize what is currently in GCC, try it on additional libraries (I
>> still plan to do libffi and libobjc at some point), and if this works
>> out, thing about moving it to Automake/Libtool instead.
>>
>> This is certainly 4.7 material, though.  I hope to get around to this in
>> that timeframe, provided libobjc stabilizes enough by than to make it
>> worthwhile.
>
> Can you file a PR so that it's not forgotten?  Untracked ideas tend to
> get forgotten.

No need: it's already on my agenda, and it seems quite unlikely that
anyone else plans to take this on.

	Rainer

-- 
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University

  reply	other threads:[~2010-11-22 18:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-19 13:53 Rainer Orth
2010-11-19 15:07 ` Tobias Burnus
2010-11-19 15:15   ` Rainer Orth
2010-11-19 20:44     ` Ralf Wildenhues
2010-11-22 18:26       ` Rainer Orth
2010-11-22 19:27         ` NightStrike
2010-11-22 19:39           ` Rainer Orth [this message]
2010-11-27 12:36         ` Ralf Wildenhues

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=yddr5ed5hp7.fsf@manam.CeBiTec.Uni-Bielefeld.DE \
    --to=ro@cebitec.uni-bielefeld.de \
    --cc=Ralf.Wildenhues@gmx.de \
    --cc=burnus@net-b.de \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=nightstrike@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).