Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_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#65481 - [vice] x64 executable missing

Attached to Project: Community Packages
Opened by Michal Cihelka (mcihelka) - Thursday, 13 February 2020, 09:32 GMT
Last edited by Alexander F. Rødseth (xyproto) - Monday, 17 February 2020, 12:33 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Alexander F. Rødseth (xyproto)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

vice 3.4-1 is missing the executable file "x64". Previous versions (3.3-3 and earlier) include it.

While it is possible to run x64sc as a workaround, this requires significantly more CPU resource compared to plain x64. In my case the workaround is not viable, because x64sc cannot run smoothly on my Celeron N3450 netbook. Yet x64 has always run perfectly. Also, even on stronger laptops, x64sc uses more power leading to shorter battery life. I expect for many people x64 is the best or only choice.

I may have found the source of the problem. As of version 3.4, the "--enable-x64" option must be configured in order for x64 to build. Refer to http://vice-emu.sourceforge.net/NEWS.

"skip building x64 unless --enable-x64 is passed to configure"

Since this seems like a configure/build issue, and not an upstream bug, I am reporting it here. It's my first bug report, I hope I've done it right.
This task depends upon

Closed by  Alexander F. Rødseth (xyproto)
Monday, 17 February 2020, 12:33 GMT
Reason for closing:  Fixed
Additional comments about closing:  Added --enable-x64
Comment by Alexander F. Rødseth (xyproto) - Sunday, 16 February 2020, 20:02 GMT
Thanks for reporting! The updated package will appear in [community] shortly.
Comment by Michal Cihelka (mcihelka) - Monday, 17 February 2020, 08:07 GMT
Welcome! And thank you for fixing so quickly, I noticed 3.4-2 is in [community] already so I upgraded. x64 executable is back, and all is good.

Loading...