valgrind-devel 3.6.0-r11208_0 Wrong architecture

[vortexfive@…]

When running valgrind I get "Bad CPU type in executable". The command "file valgrind" gives "Mach-O 64-bit executable" I use a MacBook with CoreDuo processor (not 64-bit).

[raimue@…]

As I don't have access to a i386-only Mac, could you please provide the config.log for me to debug this?

sudo port clean valgrind-devel
sudo port configure valgrind-devel
cp $(port work valgrind-devel)/trunk/config.log ~/Desktop

[vortexfive@…]

Replying to raimue@…:

As I don't have access to a i386-only Mac, could you please provide the config.log for me to debug this?

Let me know if there's anything else I can do to help getting this to work again.

[raimue@…]

I found a ​upstream bug report and attached a reference back to this ticket.

[raimue@…]

Here is a proposed patch which could probably solve the problem:

sudo port -v clean valgrind-devel
cd $(port dir valgrind-devel)
curl -o patch-valgrind-only32bit.diff http://trac.macports.org/attachment/ticket/25684/patch-valgrind-only32bit.diff?format=raw
patch -p0 < patch-valgrind-only32bit.diff
sudo port -v install valgrind-devel

Please report back if this solves your problem.

[vortexfive@…]

I get this error:

Error: Unable to open port: invalid bareword "i386"
in expression "$build_arch == i386";
should be "$i386" or "{i386}" or "i386(...)" or ...

The option '--enable-only32bit' does indeed fix the problem.

[raimue@…]

Replying to vortexfive@…:

I get this error:

Error: Unable to open port: invalid bareword "i386"
in expression "$build_arch == i386";
should be "$i386" or "{i386}" or "i386(...)" or ...

Gah, forgot quotes around it.

The option '--enable-only32bit' does indeed fix the problem.

Alright, thanks.

Committed in r69942.