Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't strip *.go and ELF files with "no maschine" #1780

Merged
merged 2 commits into from Sep 28, 2021

Conversation

ffesti
Copy link
Contributor

@ffesti ffesti commented Sep 21, 2021

Not 100% sure if this "no machine" business is 100% correct. But it looks like a better defense against strip failing than relying on the file name alone.

as those may be Guile object files. Those are ELF files but cannot be
stripped. This may also exclude other files (like Golang sources) but
that should not be an issue.

Resolves: rpm-software-management#1765
as strip fails on them (if they are Guile object files).
This adds another layer of protection as *.go files are already filtered
out.

Resolves:  rpm-software-management#1765
Copy link
Member

@pmatilai pmatilai left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've no idea about Go peculiarities. If it fixes the thing...

This method of excluding bits and pieces does not scale, but inventing something for that is obviously beyond scope.

@ffesti
Copy link
Contributor Author

ffesti commented Sep 28, 2021

I talked to mjw about this. eu-strip would probably be able to strip even these Guile files. I don't really know whether they should be stripped or not, though. Excluding the Golang (source) files should really not matter but this is to be on the save side.

And yes this whole brp business screams for a better solution but I just want this error to go away for now.

@ffesti ffesti merged commit 3161ce3 into rpm-software-management:master Sep 28, 2021
@ffesti ffesti deleted the 1765 branch October 14, 2021 11:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants