Opened 12 years ago

Closed 12 years ago

Last modified 12 years ago

#34144 closed defect (fixed)

povray: error: CPU you selected does not support x86-64 instruction set

Reported by: dershow Owned by: jeremyhu (Jeremy Huddleston Sequoia)
Priority: Normal Milestone:
Component: ports Version: 2.0.4
Keywords: Cc: jeremyhu (Jeremy Huddleston Sequoia)
Port: povray

Description

I have 3.6.1_5 and I just tried to upgrade to 3.6.1_6 and it fails.

I have attached the log file.

Thanks,

--Adam

Attachments (1)

povray_main.log (23.7 KB) - added by dershow 12 years ago.
main.log

Download all attachments as: .zip

Change History (9)

Changed 12 years ago by dershow

Attachment: povray_main.log added

main.log

comment:1 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)

Summary: povray upgrade failspovray: error: CPU you selected does not support x86-64 instruction set

The log says:

error: CPU you selected does not support x86-64 instruction set

I recall seeing this in some other ports before, but not what the solution was.

What CPU do you have?

comment:2 Changed 12 years ago by dershow

Intel Core 2 Duo 2.8 GHz. MacBook Pro.

3.6.1_5 installed fine, as well as a bunch of other 64 bit ports.

comment:3 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: jeremyhu@… added

comment:4 Changed 12 years ago by jeremyhu (Jeremy Huddleston Sequoia)

Owner: changed from macports-tickets@… to jeremyhu@…
Status: newassigned

comment:5 Changed 12 years ago by jeremyhu (Jeremy Huddleston Sequoia)

In the mean time, use clang as your compiler.

sudo port -v install povray configure.compiler=clang

I'll just wipe the -march -mtune options...

comment:6 Changed 12 years ago by dershow

Nope. I tried clang, and that didn't work either. I can post the new log if that might be helpful?

comment:7 Changed 12 years ago by jeremyhu (Jeremy Huddleston Sequoia)

Resolution: fixed
Status: assignedclosed

Weird, well it works here, but /shrug: r92166

comment:8 Changed 12 years ago by jeremyhu (Jeremy Huddleston Sequoia)

oh wait, I see this issue now. Still, the -march foo is good to get rid of.

Note: See TracTickets for help on using tickets.