From: Danny Milosavljevic <dannym@scratchpost.org>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add optipng.
Date: Mon, 26 Sep 2016 21:34:25 +0200 [thread overview]
Message-ID: <20160926213425.2d7fcfe8@scratchpost.org> (raw)
In-Reply-To: <20160926175958.GA5857@jasmine>
Hi Leo,
On Mon, 26 Sep 2016 13:59:58 -0400
Leo Famulari <leo@famulari.name> wrote:
> gcc -s -o optipng optipng.o optim.o bitset.o ratio.o osys.o wildargs.o ../opngreduc/libopngreduc.a ../pngxtern/libpngxtern.a ../libpng/libpng.a ../zlib/libz.a ../gifread/libgifread.a ../pnmio/libpnmio.a ../minitiff/libminitiff.a -lm
> ../libpng/libpng.a(pngrutil.o): In function `png_read_filter_row':
> pngrutil.c:(.text+0x13bc): undefined reference to `png_init_filter_functions_neon'
> collect2: error: ld returned 1 exit status
> make[1]: *** [Makefile:99: optipng] Error 1
> make[1]: Leaving directory '/tmp/nix-build-optipng-0.7.6.drv-0/optipng-0.7.6/src/optipng'
> make: *** [Makefile:2: all] Error 2
Looks like a problem internal to libpng.
There's a configure option '--enable-arm-neon=api' in libpng. If we supported only ARM with NEON SIMD extension then we could build libpng with it. Do we?
Debian says on their https://wiki.debian.org/ArmHardFloatPort#NEON that one shouldn't require NEON since Marvell Dove and NVidia Tegra2 (?!?!?!) don't implement it.
There's also a configure option '--enable-arm-neon=check' which would check whether NEON works at runtime - but according to configure, it's not well-supported. What does this mean?
prev parent reply other threads:[~2016-09-26 19:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-25 1:58 [PATCH] gnu: Add optipng Arun Isaac
2016-09-25 7:25 ` Arun Isaac
2016-09-25 16:20 ` Kei Kebreau
2016-09-25 16:52 ` Leo Famulari
2016-09-25 20:28 ` Arun Isaac
2016-09-25 20:28 ` Arun Isaac
2016-09-25 21:03 ` Kei Kebreau
2016-09-26 17:59 ` Leo Famulari
2016-09-26 19:21 ` Arun Isaac
2016-09-26 21:22 ` Leo Famulari
2016-09-26 19:34 ` Danny Milosavljevic [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160926213425.2d7fcfe8@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).