[Bug binutils/31250] Stripping Rust static libraries fails because of overly zealous illegal path check

[amy at amyspark dot me]

https://sourceware.org/bugzilla/show_bug.cgi?id=31250

--- Comment #5 from Amyspark <amy at amyspark dot me> ---
>   Is the library really valid if it contains absolute pathnames ?

Yes, all that MSVC cares about is a) the symbol b) the path inside the .lib
pointing to an existing object. I was able to extract all of them successfully
using LIB.EXE and repackage them.

>  Ie, wouldn't it be better to fix how Rust is creating the library, rather 
> than allowing strip to process it, only to have it rejected later on because 
> of the paths ?

While this would undoubtedly be a good approach, given that LIB.EXE doesn't
complain and Rust is using their own archiving capabilities (as opposed to
LIB.EXE or binutils ar), I went with reporting it here.

-- 
You are receiving this mail because:
You are on the CC list for the bug.