Opened 13 years ago
Last modified 12 years ago
#30488 closed defect
gavl fails to build — at Version 2
Reported by: | macports@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.0.0 |
Keywords: | Cc: | ||
Port: | gavl |
Description (last modified by jmroot (Joshua Root))
The build of the port gavl bails with an error. The end of the log is copied below.
:info:build libtool: compile: /Developer/usr/bin/llvm-gcc-4.2 -DHAVE_CONFIG_H -I. -I../include/gavl -I../include -I../include/gavl -I../include -I/usr/local/include -D__GAVL__ -pipe -O2 -arch x86_64 -O3 -funroll-all-loops -fomit-frame-pointer -ffast-math -Wall -Wmissing-declarations -Wdeclaration-after-statement -mfpmath=387 -fvisibility=hidden -MT frametable.lo -MD -MP -MF .deps/frametable.Tpo -c frametable.c -fno-common -DPIC -o .libs/frametable.o :info:build libtool: compile: /Developer/usr/bin/llvm-gcc-4.2 -DHAVE_CONFIG_H -I. -I../include/gavl -I../include -I../include/gavl -I../include -I/usr/local/include -D__GAVL__ -pipe -O2 -arch x86_64 -O3 -funroll-all-loops -fomit-frame-pointer -ffast-math -Wall -Wmissing-declarations -Wdeclaration-after-statement -mfpmath=387 -fvisibility=hidden -MT interleave.lo -MD -MP -MF .deps/interleave.Tpo -c interleave.c -fno-common -DPIC -o .libs/interleave.o :info:build mv -f .deps/interleave.Tpo .deps/interleave.Plo :info:build /bin/sh ../libtool --tag=CC --mode=compile /Developer/usr/bin/llvm-gcc-4.2 -DHAVE_CONFIG_H -I. -I../include/gavl -I../include -I../include/gavl -I../include -I/usr/local/include -D__GAVL__ -pipe -O2 -arch x86_64 -O3 -funroll-all-loops -fomit-frame-pointer -ffast-math -Wall -Wmissing-declarations -Wdeclaration-after-statement -mfpmath=387 -fvisibility=hidden -MT memcpy.lo -MD -MP -MF .deps/memcpy.Tpo -c -o memcpy.lo memcpy.c :info:build libtool: compile: /Developer/usr/bin/llvm-gcc-4.2 -DHAVE_CONFIG_H -I. -I../include/gavl -I../include -I../include/gavl -I../include -I/usr/local/include -D__GAVL__ -pipe -O2 -arch x86_64 -O3 -funroll-all-loops -fomit-frame-pointer -ffast-math -Wall -Wmissing-declarations -Wdeclaration-after-statement -mfpmath=387 -fvisibility=hidden -MT memcpy.lo -MD -MP -MF .deps/memcpy.Tpo -c memcpy.c -fno-common -DPIC -o .libs/memcpy.o :info:build mv -f .deps/frametable.Tpo .deps/frametable.Plo :info:build memcpy.c: In function ‘linux_kernel_memcpy_impl’: :info:build memcpy.c:167: error: unsupported inline asm: input constraint with a matching output constraint of incompatible type! :info:build /bin/sh ../libtool --tag=CC --mode=compile /Developer/usr/bin/llvm-gcc-4.2 -DHAVE_CONFIG_H -I. -I../include/gavl -I../include -I../include/gavl -I../include -I/usr/local/include -D__GAVL__ -pipe -O2 -arch x86_64 -O3 -funroll-all-loops -fomit-frame-pointer -ffast-math -Wall -Wmissing-declarations -Wdeclaration-after-statement -mfpmath=387 -fvisibility=hidden -MT mix.lo -MD -MP -MF .deps/mix.Tpo -c -o mix.lo mix.c :info:build make[2]: *** [memcpy.lo] Error 1 :info:build make[2]: *** Waiting for unfinished jobs.... :info:build libtool: compile: /Developer/usr/bin/llvm-gcc-4.2 -DHAVE_CONFIG_H -I. -I../include/gavl -I../include -I../include/gavl -I../include -I/usr/local/include -D__GAVL__ -pipe -O2 -arch x86_64 -O3 -funroll-all-loops -fomit-frame-pointer -ffast-math -Wall -Wmissing-declarations -Wdeclaration-after-statement -mfpmath=387 -fvisibility=hidden -MT mix.lo -MD -MP -MF .deps/mix.Tpo -c mix.c -fno-common -DPIC -o .libs/mix.o :info:build mv -f .deps/mix.Tpo .deps/mix.Plo :info:build make[2]: Leaving directory `/usr/local/var/macports/build/_usr_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_gavl/gavl/work/gavl-1.2.0/gavl' :info:build make[1]: *** [all-recursive] Error 1 :info:build make[1]: Leaving directory `/usr/local/var/macports/build/_usr_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_gavl/gavl/work/gavl-1.2.0/gavl' :info:build make: *** [all-recursive] Error 1 :info:build make: Leaving directory `/usr/local/var/macports/build/_usr_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_gavl/gavl/work/gavl-1.2.0' :info:build shell command " cd "/usr/local/var/macports/build/_usr_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_gavl/gavl/work/gavl-1.2.0" && /usr/bin/make -j2 -w all " returned error 2 :error:build Target org.macports.build returned: shell command failed (see log for details) :debug:build Backtrace: shell command failed (see log for details) while executing "command_exec build" (procedure "portbuild::build_main" line 8) invoked from within "$procedure $targetname" :info:build Warning: the following items did not execute (for gavl): org.macports.activate org.macports.build org.macports.destroot org.macports.install :error:build Failed to install gavl :notice:build Log for gavl is at: /usr/local/var/macports/logs/_usr_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_gavl/gavl/main.log
Seems odd to me that it brings its own memcpy, more odd that its blowing up on some inline assembler. However, there is a hint higher up in the log.
:info:configure checking for libpng... yes :info:configure /var/tmp//ccm1Wz71.s:18:suffix or operands invalid for `push' :info:configure /var/tmp//ccm1Wz71.s:18:suffix or operands invalid for `pop' :info:configure /var/tmp//ccm1Wz71.s:71:suffix or operands invalid for `push' :info:configure /var/tmp//ccm1Wz71.s:71:suffix or operands invalid for `pop' :info:configure /var/tmp//ccm1Wz71.s:80:suffix or operands invalid for `push' :info:configure /var/tmp//ccm1Wz71.s:80:suffix or operands invalid for `pop' :info:configure /var/tmp//ccm1Wz71.s:93:suffix or operands invalid for `push' :info:configure /var/tmp//ccm1Wz71.s:93:suffix or operands invalid for `pop' :info:configure /var/tmp//ccm1Wz71.s:143:suffix or operands invalid for `push' :info:configure /var/tmp//ccm1Wz71.s:143:suffix or operands invalid for `pop' :info:configure ./cpuinfo.sh: line 78: ./cpuinfo: No such file or directory :info:configure ./cpuinfo.sh: line 79: ./cpuinfo: No such file or directory :info:configure ./cpuinfo.sh: line 80: ./cpuinfo: No such file or directory :info:configure ./cpuinfo.sh: line 81: ./cpuinfo: No such file or directory :info:configure ./cpuinfo.sh: line 82: ./cpuinfo: No such file or directory :info:configure ./cpuinfo.sh: line 83: ./cpuinfo: No such file or directory :info:configure ./cpuinfo.sh: line 86: ./cpuinfo: No such file or directory :info:configure checking if /Developer/usr/bin/llvm-gcc-4.2 supports Your flags... no :info:configure checking if /Developer/usr/bin/llvm-gcc-4.2 supports does flags... no :info:configure checking if /Developer/usr/bin/llvm-gcc-4.2 supports not flags... no :info:configure checking if /Developer/usr/bin/llvm-gcc-4.2 supports even flags... no :info:configure checking if /Developer/usr/bin/llvm-gcc-4.2 supports support flags... no :info:configure checking if /Developer/usr/bin/llvm-gcc-4.2 supports "i386" flags... no :info:configure checking if /Developer/usr/bin/llvm-gcc-4.2 supports for flags... no :info:configure checking if /Developer/usr/bin/llvm-gcc-4.2 supports '-march' flags... no :info:configure checking if /Developer/usr/bin/llvm-gcc-4.2 supports and flags... no :info:configure checking if /Developer/usr/bin/llvm-gcc-4.2 supports -mtune. flags... no :info:configure checking if /Developer/usr/bin/llvm-gcc-4.2 supports -O3 flags... yes :info:configure checking if /Developer/usr/bin/llvm-gcc-4.2 supports -funroll-all-loops flags... yes :info:configure checking if /Developer/usr/bin/llvm-gcc-4.2 supports -fomit-frame-pointer flags... yes :info:configure checking if /Developer/usr/bin/llvm-gcc-4.2 supports -ffast-math flags... yes :info:configure checking Architecture... IA32
IA32, really? Interesting, since the build target arch is x86_64.
Change History (2)
comment:1 Changed 13 years ago by macports@…
comment:2 Changed 13 years ago by jmroot (Joshua Root)
Description: | modified (diff) |
---|
You should just use an attachment for the log.
Note: See
TracTickets for help on using
tickets.
And again, this stupid site strips the newlines from the pasted text while leaving those in the text I typed. How does it even manage suck a cock-up? At least its not as bad a couple weeks ago when it was stripping ALL newlines on submissions I made. Also, the log lines have a sufficiently consistent prefix to be able to quickly unwrap the text in a decent editor.