Opened 14 years ago

Closed 13 years ago

#24893 closed defect (fixed)

x264: unrecognizable insn

Reported by: boydb@… Owned by: dbevans (David B. Evans)
Priority: Normal Milestone:
Component: ports Version: 1.8.2
Keywords: Cc: zm1213@…
Port: x264

Description

While upgrading x264 on a 10.4 Intel tower:

--->  Building x264
DEBUG: Executing org.macports.build (x264)
DEBUG: Environment: MACOSX_DEPLOYMENT_TARGET='10.4'
DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_x264/work/x264-snapshot-20100412-2245" && /usr/bin/make -j1 default'
/usr/bin/gcc-4.0 -O3 -ffast-math -O2 -I. -fno-common -read_only_relocs suppress -arch i386 -Wall -I. -falign-loops=16 -march=i686 -mfpmath=sse -msse -std=gnu99 -fPIC -s -fomit-frame-pointer   -c -o encoder/analyse.o encoder/analyse.c
encoder/analyse.c: In function 'x264_analyse_init_costs':
encoder/analyse.c:275: error: unrecognizable insn:
(insn:HI 88 87 89 6 (set (reg:V4SI 117)
        (ashift:V4SI (reg:V4SI 117)
            (const_int 31 [0x1f]))) -1 (insn_list:REG_DEP_TRUE 87 (nil))
    (nil))
encoder/analyse.c:275: internal compiler error: in extract_insn, at recog.c:2033
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://developer.apple.com/bugreporter> for instructions.
make: *** [encoder/analyse.o] Error 1
Error: Target org.macports.build returned: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_x264/work/x264-snapshot-20100412-2245" && /usr/bin/make -j1 default " returned error 2
DEBUG: Backtrace: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_x264/work/x264-snapshot-20100412-2245" && /usr/bin/make -j1 default " returned error 2
    while executing
"command_exec build"
    (procedure "portbuild::build_main" line 9)
    invoked from within
"$procedure $targetname"
Warning: the following items did not execute (for x264): org.macports.destroot org.macports.build
DEBUG: 
Error: Unable to upgrade port: 1
To report a bug, see <http://guide.macports.org/#project.tickets>

Full debug log is attached

Attachments (1)

debug.log (13.9 KB) - added by boydb@… 14 years ago.
Debug log

Download all attachments as: .zip

Change History (9)

Changed 14 years ago by boydb@…

Attachment: debug.log added

Debug log

comment:1 Changed 14 years ago by boydb@…

Cc: boydb@… added

Cc Me!

comment:2 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: boydb@… removed
Owner: changed from macports-tickets@… to devans@…

Please Cc the port maintainer, and note that you don't need to Cc yourself.

comment:3 Changed 14 years ago by jmroot (Joshua Root)

What version of Xcode are you using?

comment:4 in reply to:  3 ; Changed 14 years ago by boydb@…

Replying to ryandesign@…:

Please Cc the port maintainer, and note that you don't need to Cc yourself.

Thanks; how do I found out who the port maintainer is for each port?

Replying to jmr@…:

What version of Xcode are you using?

2.5. I just checked and see that 3.1.4 is the latest that is compatible with Leopard (10.4), so I'll see if that helps the situation.

comment:5 in reply to:  4 Changed 14 years ago by boydb@…

Replying to boydb@…:

2.5. I just checked and see that 3.1.4 is the latest that is compatible with Leopard (10.4), so I'll see if that helps the situation.

Whoops; "Leopard" is 10.5; "Tiger" is 10.4, which is what I've got. The latest version that works with what I've got is the 2.5 that I've already got installed.

comment:6 Changed 14 years ago by zm1213@…

It's a matter of adding -msse2 to CFLAGS, I don't think it's a macports issue though as it happens even if you try to checkout x264 and compile it yourself. Adding -msse2 to CFLAGS work well even in 10.4

comment:7 Changed 14 years ago by zm1213@…

Cc: zm1213@… added

Cc Me!

comment:8 Changed 13 years ago by jmroot (Joshua Root)

Resolution: fixed
Status: newclosed

I don't have a 10.4 install to test on, but if the info here is correct the problem should be fixed by r79084.

Note: See TracTickets for help on using tickets.