This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Make sure symbol version script is writeable


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]