| Summary: | valgrind for x86_64 is built by default on i386 architecture on OS X | ||
|---|---|---|---|
| Product: | [Developer tools] valgrind | Reporter: | Yuri <yuri> |
| Component: | general | Assignee: | Rhys Kidd <rhyskidd> |
| Status: | RESOLVED UNMAINTAINED | ||
| Severity: | normal | CC: | pjfloyd, rhyskidd |
| Priority: | NOR | ||
| Version First Reported In: | 3.6.0 | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | macOS | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
I'm sure this is a dup of a bug filed some time back. Can't find the bug number though. Confirm with the current trunk rev.11496 Closing this as unmaintained. If "output on i386" means a machine booted to a 32bit i386 kernel, the last OS where that was possible was OS X 10.7 Lion back in 2012. Valgrind won't even build on something so old (at least not with XCode). |
configure produces this output on i386: Maximum build arch: amd64 Primary build arch: amd64 Secondary build arch: x86 Build OS: darwin Primary build target: AMD64_DARWIN Secondary build target: X86_DARWIN Default supp files: exp-ptrcheck.supp xfree-3.supp xfree-4.supp darwin10-drd.supp darwin10.supp Runing 'file' command on resulting executable gives this: /Users/yuri/valgrind-3.6.0/bin/valgrind: Mach-O 64-bit executable x86_64 Attempt to run it causes the message: Bad CPU type in executable. Option --enable-only32bit fixes the problem. configure should build working on the platform executable by default.