| Summary: | Squid will not start; exits immediately with message "Illegal Instruction" | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Guy Gallagher <guy.gallagher> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | cjw, guy.gallagher, luigiwalser |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | squid-3.4.9-1.mga5.src.rpm | CVE: | |
| Status comment: | |||
| Attachments: |
Output of cpuinfo --debug
Output of systemctl status squid.service -l > squid.errors |
||
|
Description
Guy Gallagher
2014-11-21 21:56:24 CET
There's no arch-native option in the SPEC file. I would be surprised if upstream was talking about an RPM option. Do you have a reference to this upstream "chatter"? Official packages are not built with rpmbuild such that we can pass options that way, if that actually does something, although I don't see anything like that documented in the rpmbuild manpage and usually --with options enable things that are in the SPEC file, and again, no such thing exists in ours. Maybe it was the simple act of rebuilding the squid package that fixed it for you, and the option didn't actually do anything. Can you try that? If so, we can rebuild it on the build system. CC:
(none) =>
luigiwalser I used rpmbuild to avoid compiling from source, it's just simpler. The option disable-arch-native belings in the config file as indicated here: http://wiki.squid-cache.org/KnowledgeBase/IllegalInstructionError I wasn't trying to encourage you to build from source or discourage you from using rpmbuild, in fact using rpmbuild again is what I wanted. I was just pointing out that in the build system we can't use a --with option to rpmbuild because that's now how the RPMs are built. Anyway, as I suspected, the --with option wasn't doing anything anyway, so it was the simple act of rebuilding that fixed it for you. A --with rpmbuild option won't add options to the configure call (which is what the Squid KB article was suggesting) unless the SPEC file is written to make it do that. I've submitted a rebuild to the build system. Please confirm that squid-3.4.9-2.mga5 fixes the issue. Thanks for the report. Thanks, that was quick! New version hasn't hit the mirrors yet, I'll confirm as soon as the updated version is available. And, apologies for misunderstanding your request. Created attachment 5629 [details]
Output of cpuinfo --debug
Created attachment 5630 [details]
Output of systemctl status squid.service -l > squid.errorsCC:
(none) =>
guy.gallagher Sad to say, squid-3.4.9-2.mga5 produces the same results on my workstation. Two files are attached; here is the version information: [root@MusicStudio ~]# rpm -qa|grep squid squid-cachemgr-3.4.9-2.mga5 The gcc option -march=native compiles for the specific CPU in the build machine which is not appropriate for OS vendors like Mageia. We decide what hardware we want to support and this is not simply the specific hardware we happen to use for building our packages. So we must indeed disable use of this option in the squid package. The problem should be fixed with squid-3.4.9-3.mga5 . CC:
(none) =>
cjw Confirmed, squid-3.4.9-3.mga5 resolves this issue. Thanks. Confirmed, squid-3.4.9-3.mga5 resolves this issue. [gallaghg@MusicStudio ~]$ ps -ef|grep squid root 3478 1 0 08:56 ? 00:00:00 squid squid 3481 3478 0 08:56 ? 00:00:00 (squid-1) squid 3573 3481 0 08:57 ? 00:00:00 (logfile-daemon) /var/log/squid/access.log squid 3574 3481 0 08:57 ? 00:00:00 (pinger) gallaghg 8177 8133 0 09:00 pts/1 00:00:00 grep --color squid [gallaghg@MusicStudio ~]$ rpm -qa|grep squid squid-cachemgr-3.4.9-3.mga5 Status:
NEW =>
RESOLVED |