Bug 262443 - valgrind for x86_64 is built by default on i386 architecture on OS X
Summary: valgrind for x86_64 is built by default on i386 architecture on OS X
Status: RESOLVED UNMAINTAINED
Alias: None
Product: valgrind
Classification: Developer tools
Component: general (other bugs)
Version First Reported In: 3.6.0
Platform: Compiled Sources macOS
: NOR normal
Target Milestone: ---
Assignee: Rhys Kidd
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-07 19:18 UTC by Yuri
Modified: 2025-12-19 10:48 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Yuri 2011-01-07 19:18:31 UTC 
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.
Comment 1 Julian Seward 2011-01-11 00:50:21 UTC 
I'm sure this is a dup of a bug filed some time back.  Can't
find the bug number though.
Comment 2 Yuri 2011-01-11 22:20:24 UTC 
Confirm with the current trunk rev.11496
Comment 3 Paul Floyd 2025-12-19 10:48:28 UTC 
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).