From: Andreas Schwab <schwab@suse.de>
To: Jim Blandy <jimb@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org, libstdc++@gcc.gnu.org
Subject: Re: Make sure symbol version script is writeable
Date: Mon, 07 May 2007 22:22:00 -0000 [thread overview]
Message-ID: <jetzuonuix.fsf@sykes.suse.de> (raw)
In-Reply-To: <m364741gqm.fsf@codesourcery.com> (Jim Blandy's message of "Mon\, 07 May 2007 14\:11\:29 -0700")
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?
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2007-05-07 22:22 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 [this message]
2007-05-08 1:01 ` Jim Blandy
2007-06-23 20:27 ` Mark Mitchell
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=jetzuonuix.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=jimb@codesourcery.com \
--cc=libstdc++@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).