Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#42410 - [evince] bashisms break compilation

Attached to Project: Arch Linux
Opened by Steven Honeyman (stevenhoneyman) - Thursday, 16 October 2014, 17:20 GMT
Last edited by Jan Alexander Steffens (heftig) - Sunday, 19 July 2015, 10:37 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Jan de Groot (JGC)
Jan Alexander Steffens (heftig)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

If /bin/sh is not bash (mine was symlinked to dash instead), then configure fails with:

./configure: 19987: ./configure: Syntax error: "(" unexpected (expecting "fi")

I swapped out the first line to #!/bin/bash intead, but then it fails a bit later in the compile with libtool errors (hundreds of lines).
Changing my symlink to point to /usr/bin/bash "fixed"/masked the problem and it compiled OK.


...should probably mention, I'm going by this advice from Allan:
https://bbs.archlinux.org/viewtopic.php?pid=1460350#p1460350
This task depends upon

Closed by  Jan Alexander Steffens (heftig)
Sunday, 19 July 2015, 10:37 GMT
Reason for closing:  Upstream
Comment by Doug Newgard (Scimmia) - Thursday, 16 October 2014, 17:57 GMT
All that really matters is that repo PKGBUILDs work in a clean chroot, so this really isn't a problem. This comes from upstream anyway, so if you can point the bashism out to them, that's where it needs fixed.
Comment by Doug Newgard (Scimmia) - Sunday, 19 July 2015, 04:38 GMT
Steven, did you ever report this upstream?
Comment by Steven Honeyman (stevenhoneyman) - Sunday, 19 July 2015, 10:36 GMT
No - it was right around the time they ruined the UI (in my opinion) and I switched to qpdfview instead.

Feel free to close even if this still isn't fixed.

Loading...