search

FLIF-hub / FLIF

Free Lossless Image Format
Other
3.72k stars 229 forks source link

FLIF won't build after 'ninja' #466

Open aajuarez opened 7 years ago

aajuarez commented 7 years ago

I'm trying to finish building FLIF on OS X. I took care of the dependencies, got past the make, and then did 'python configure.py'. I typed 'ninja', but I have this vague "x86_64" error... Any ideas what to do here?

[1/1] g++ -O2 -ftree-vectorize -DNDEBUG obj/src/comm...form/factory.o pkg-config --libs libpng -o src/flif FAILED: g++ -O2 -ftree-vectorize -DNDEBUG obj/src/common.o .... ld: symbol(s) not found for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation) ninja: build stopped: subcommand failed.

gaming-hacker commented 7 years ago

I just built it successfully on OSX, basically i just did ninja to create basic Makefiles, then went in and chopped and hacked src and got it to build and tests run successfully, even the exif tests.

i've built it for Macports NOT homebrew, i'll post the update repo when i finish testing it.

../tools/test-metadata.sh ./flif ../testFiles/sig05-014.png ../tmp-test/out-meta.flif ../tmp-test/out-meta.png
+ FLIF=./flif
+ IN=../testFiles/sig05-014.png
+ OUTF=../tmp-test/out-meta.flif
+ OUTP=../tmp-test/out-meta.png
+ EXIFIN=../tmp-test/in-exif.xmp
+ EXIFOUT=../tmp-test/out-exif.xmp
+ EXIFTOOL_OPTIONS='-XMP:*'
+ rm -f ../tmp-test/out-meta.flif ../tmp-test/out-meta.png ../tmp-test/in-exif.xmp ../tmp-test/out-exif.xmp
+ ./flif ../testFiles/sig05-014.png ../tmp-test/out-meta.flif
+ ./flif -d ../tmp-test/out-meta.flif ../tmp-test/out-meta.png
+ exiftool '-XMP:*' ../testFiles/sig05-014.png -o ../tmp-test/in-exif.xmp
    1 image files created
+ exiftool '-XMP:*' ../tmp-test/out-meta.png -o ../tmp-test/out-exif.xmp
    1 image files created
+ diff ../tmp-test/in-exif.xmp ../tmp-test/out-exif.xmp
comradekingu commented 6 years ago

@aajuarez Does it build now? https://github.com/FLIF-hub/FLIF/commit/d790731b4b0de0b57c28a6652f0e2131cdd70f37

aajuarez commented 6 years ago

@comradekingu no, it does not. I noticed that @jonsneyers made an update recently, but I'm still getting this error during build: "Undefined symbols for architecture x86_64:" @gaming-hacker have you made a clear resolution to this?