Changes between Initial Version and Version 2 of Ticket #30488


Ignore:
Timestamp:
Jul 31, 2011, 10:24:45 AM (13 years ago)
Author:
jmroot (Joshua Root)
Comment:

You should just use an attachment for the log.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #30488 – Description

    initial v2  
    11The build of the port gavl bails with an error. The end of the log is copied below.
    2 
     2{{{
    33: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
    44: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
     
    3030:error:build Failed to install gavl
    3131: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
    32 
     32}}}
    3333Seems 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.
    34 
     34{{{
    3535:info:configure checking for libpng... yes
    3636:info:configure /var/tmp//ccm1Wz71.s:18:suffix or operands invalid for `push'
     
    6666:info:configure checking if /Developer/usr/bin/llvm-gcc-4.2 supports -ffast-math flags... yes
    6767:info:configure checking Architecture... IA32
    68 
     68}}}
    6969IA32, really? Interesting, since the build target arch is x86_64.
    70 
    71