Package Details: mingw-w64-libpng 1.6.43-1

Git Clone URL: (read-only, click to copy)
Package Base: mingw-w64-libpng
Description: A collection of routines used to create PNG format graphics (mingw-w64)
Upstream URL:
Licenses: custom
Submitter: ekpyron
Maintainer: xantares
Last Packager: xantares
Votes: 23
Popularity: 0.000000
First Submitted: 2012-03-22 22:58 (UTC)
Last Updated: 2024-02-24 11:47 (UTC)

Latest Comments

1 2 3 Next › Last »

drakkan commented on 2019-09-07 17:27 (UTC)

Can you please fix the PKGBUILD replacing

patch -p0 -i "${srcdir}/libpng-$_apngver-apng.patch"


zcat "${srcdir}/libpng-$_apngver-apng.patch" | patch -p0

as suggested before? thanks

donotdont commented on 2019-07-06 11:10 (UTC) (edited on 2019-07-06 11:11 (UTC) by donotdont)

i click download file on "Download snapshot" and run this commands:

makepkg -Acs

to fix error: extract file "src/libpng-1.6.37-apng.patch.gz" -> "libpng-1.6.37-apng.patch"

for me it's working.

luntik2012 commented on 2019-05-31 11:47 (UTC)

zcat "${srcdir}/libpng-$_apngver-apng.patch" | patch -p0

worked for me

pingplug commented on 2019-05-26 01:22 (UTC)

makepkg did not extract patch any more...

==> Extracting sources...
  -> Extracting libpng-1.6.37.tar.xz with bsdtar
==> Starting prepare()...
patch: **** Can't open patch file /tmp/makepkg/mingw-w64-libpng/src/libpng-1.6.37-apng.patch : No such file or directory
==> ERROR: A failure occurred in prepare().

gamezelda commented on 2019-05-23 19:07 (UTC)

Hello, the build (both yay and manual) is failing for me due to the 'patch' command in prepare() not finding the uncompressed patch file.

Not sure why the patch is not actually uncompressed, because I know makepkg uncompresses sources in some cases.

Anyway, I fixed the build by replacing the 'patch' command in prepare with:

zcat "${srcdir}/libpng-$_apngver-apng.patch" | patch -p0

xantares commented on 2014-11-14 14:03 (UTC)

and with regular packages archlinux sets its own flags too, hence the 'buildflags' option, as they're not compatible with mingw

ekpyron commented on 2014-11-14 13:09 (UTC)

Well, I do understand the flags - basically they are all about hardening security and as such are actually reasonable - I was just wondering where they were coming from and why one would set them automatically instead of letting users set them as they like, but I suppose Fedora is a reasonable reference, yes, so I'll start using them for my packages as well, thanks.

xantares commented on 2014-11-14 13:03 (UTC)

I don't know the significance of all "-g -O2" is obvious, FORTIFY_SOURCE adds security to basic libc function against overflow etc, ... Basically it's the ones of Fedora, and it's doesn't seem unreasonable flags. xan.

ekpyron commented on 2014-11-14 12:02 (UTC)

Although you put them there yourself... I'd still like to know what's the reasoning behind using these flags and especially why it makes sense to force users to set these flags...

ekpyron commented on 2014-11-14 11:48 (UTC)

OK, they are suggested in the MinGW package guidelines... well I suppose it can't hurt...