On 8/14/2022 6:29 AM, Jarryd Lisher via devel wrote:
Hey,
I figured out that this is mainly caused by the configure script
containing multi-line definitions. So, the hacks only operate on the
first part and land up leaving random lines of nonsense in the file.
You can fix this by adding the following "unwrap" `sed` script just
before the `%{configure}` line:
```
%{__sed} -i -z -e 's/\\\n//g' configure
```
It's not perfect, but is a simple fix to remove those errors from the
configure.
That seems like a pretty big hammer with fair potential for changing
something we didn't really want to. Can we key it's behavior somehow on
lines we care about?
Thanks,
Jeff
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
