From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: "'Richard Sandiford'" <richard.sandiford@linaro.org>
Cc: <binutils@sourceware.org>
Subject: Not in 2.21 sources... [OBV/RFA] Fix compilation of ld/emultempl/spuelf.em on systems where HAVE_MKSTEMP is not defined
Date: Thu, 09 Dec 2010 11:11:00 -0000 [thread overview]
Message-ID: <001c01cb9791$bc506ab0$34f14010$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <g48w17znxm.fsf@richards-desktop.stglab.manchester.uk.ibm.com>
Hi all,
I just tested compilation of 2.21 release for mingw
with --enable-targets=all option
and I noticed that the fix that I submitted and
which was applied by Richard is not in 2.21 sources.
I suppose it is because the 2.21 branch was created before November 5.
I don't know if 2.21.1 will ever exist, but
merging that commit to 2.21 branch can't hurt anyhow.
Pierre Muller
> -----Message d'origine-----
> De : binutils-owner@sourceware.org [mailto:binutils-
> owner@sourceware.org] De la part de Richard Sandiford
> Envoyé : vendredi 5 novembre 2010 18:21
> À : Pierre Muller
> Cc : binutils@sourceware.org
> Objet : Re: [OBV/RFA] Fix compilation of ld/emultempl/spuelf.em on
> systems where HAVE_MKSTEMP is not defined
>
> "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr> writes:
> > 2010-11-05 Pierre Muller <muller@ics.u-strasbg.fr>
> >
> > * emultempl/spuelf.em (new_tmp_file): Fix wrong first
> > parameter.
>
> Applied, thanks.
>
> Richard
next prev parent reply other threads:[~2010-12-09 11:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <48683.3413750448$1288971470@news.gmane.org>
2010-11-05 17:21 ` Richard Sandiford
2010-12-09 11:11 ` Pierre Muller [this message]
2010-12-09 11:20 ` Not in 2.21 sources... " Tristan Gingold
2010-12-09 12:26 ` Pierre Muller
2010-12-10 10:45 ` Tristan Gingold
2011-11-22 15:26 ` [RFC] 2.22 release: Compilation failure for mingw32 target with --enable-targets=all Pierre Muller
2011-11-25 16:40 ` nick clifton
2011-11-25 17:02 ` Pedro Alves
2011-11-29 12:43 ` nick clifton
2011-11-29 12:53 ` Alan Modra
2011-11-29 16:27 ` nick clifton
2011-11-30 11:52 ` Alan Modra
2011-12-01 11:39 ` nick clifton
2011-11-26 11:18 ` JonY
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='001c01cb9791$bc506ab0$34f14010$@muller@ics-cnrs.unistra.fr' \
--to=pierre.muller@ics-cnrs.unistra.fr \
--cc=binutils@sourceware.org \
--cc=richard.sandiford@linaro.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).