From: Mark Mitchell <mark@codesourcery.com>
To: Jim Blandy <jimb@codesourcery.com>
Cc: Andreas Schwab <schwab@suse.de>,
gcc-patches@gcc.gnu.org, libstdc++@gcc.gnu.org
Subject: Re: Make sure symbol version script is writeable
Date: Sat, 23 Jun 2007 20:27:00 -0000 [thread overview]
Message-ID: <467D7D64.6020407@codesourcery.com> (raw)
In-Reply-To: <m31whsp1r1.fsf@codesourcery.com>
Jim Blandy wrote:
> Andreas Schwab <schwab@suse.de> writes:
>> Jim Blandy <jimb@codesourcery.com> writes:
>>
>>> If the source tree has been made read-only, the libstdc++-v3 build
>>> dies trying to construct src/libstdc++-symbols.ver.
>>>
>>> libstdc++-v3/ChangeLog:
>>> 2007-05-07 Jim Blandy <jimb@codesourcery.com>
>>>
>>> * libstdc++-v3/src/Makefile.am (libstdc++-symbol.ver): Make
>>> sure the build tree copy of libstdc++-symbol.ver is writeable.
>>> * libstdc++-v3/src/Makefile.in: Regenerated.
>>>
>>> Index: libstdc++-v3/src/Makefile.am
>>> ===================================================================
>>> --- libstdc++-v3/src/Makefile.am (revision 124502)
>>> +++ libstdc++-v3/src/Makefile.am (working copy)
>>> @@ -32,6 +32,7 @@
>>> libstdc++-symbols.ver: ${glibcxx_srcdir}/$(SYMVER_FILE) \
>>> $(port_specific_symbol_files)
>>> cp ${glibcxx_srcdir}/$(SYMVER_FILE) ./libstdc++-symbols.ver
>>> + chmod +w ./libstdc++-symbol.ver
>> You surely mean `symbols' here?
>
> Yes, I certainly do. Thanks for the close reading. (This is what I
> get for working with three branches at once, none of whose patches
> apply cleanly to the others.)
It doesn't look like this patch was ever applied. With the change
Andreas has suggested, this is OK after the lockdown.
Thanks,
--
Mark Mitchell
CodeSourcery
mark@codesourcery.com
(650) 331-3385 x713
next prev parent reply other threads:[~2007-06-23 20:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-07 21:11 Jim Blandy
2007-05-07 22:22 ` Andreas Schwab
2007-05-08 1:01 ` Jim Blandy
2007-06-23 20:27 ` Mark Mitchell [this message]
2007-06-25 18:50 ` Jim Blandy
2007-08-07 21:07 ` Jim Blandy
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=467D7D64.6020407@codesourcery.com \
--to=mark@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jimb@codesourcery.com \
--cc=libstdc++@gcc.gnu.org \
--cc=schwab@suse.de \
/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).