Package Details: wiggle 1.3-1

Git Clone URL: (read-only, click to copy)
Package Base: wiggle
Description: A program for applying patches that patch cannot apply because of conflicting changes
Upstream URL:
Licenses: GPL2
Submitter: simon04
Maintainer: simon04
Last Packager: simon04
Votes: 4
Popularity: 0.000002
First Submitted: 2012-08-03 10:24
Last Updated: 2020-10-07 04:27

Dependencies (1)

Required by (0)

Sources (1)

Latest Comments

richq commented on 2017-10-25 11:35

The latest 1.1 gave me a build failure, though wiggle 1.0 is also affected if I go back and build that. Missing "keypad" symbol:

cc wiggle.o load.o parse.o split.o extract.o diff.o bestmatch.o ReadMe.o merge2.o vpatch.o ccan/hash/hash.o -lncurses -o wiggle
/usr/sbin/ld: vpatch.o: undefined reference to symbol 'keypad'
/usr/lib/ error adding symbols: DSO missing from command line
collect2: error: ld returned 1 exit status
make: *** [<builtin>: wiggle] Error 1

I changed the Makefile to have -lncurses -ltinfo like the error hints and it builds OK. Like this:

LDLIBS = -lncurses -ltinfo

No idea why it broke, maybe some core change in ncurses since the last update.

simon04 commented on 2015-04-13 21:52

@kei, bwidawsk: Sorry, my bad. I built with a very outdated /etc/makepkg.conf.
I got the same error with the latest /etc/makepkg.conf. I added the following line to the PKGBUILD – it respects the CFLAGS from /etc/makepkg.conf now:
> sed -i -r 's/^CFLAGS=.*/CFLAGS+=-I. /' Makefile

bwidawsk commented on 2015-04-09 01:57

On second look, I think kei was entirely correct. Latest gcc is producing warnings for me.

bwidawsk commented on 2015-04-09 01:53

Forgive me, I do not know how or even if it's possible to use tags. So this may look crappy.

simon04, I believe you are incorrect, and that kei is [mostly] right, though perhaps the message didn't come through clearly. I think the flagging was because the package doesn't build, and not that it's out of date...

Additionally, I enabled optimization as well (removes "#warning _FORTIFY_SOURCE requires compiling with optimization"):

sed -i -r 's/^OptDbg=.*$/OptDbg=-O2 -march=native/' Makefile

simon04, what glibc do you have installed?

The latest in Arch should have the following in /usr/include/features.h:
# if !defined __OPTIMIZE__ || __OPTIMIZE__ <= 0
# warning _FORTIFY_SOURCE requires compiling with optimization (-O)

That causes a warning. With -Werror, it's a compilation failure. You need to *either* drop -Werror, or add an -O[123] (kei incorrectly said you need both). I'm confused how you are not seeing this error as well. The package has not been buildable for me for quite some time, and when I went to complain myself, I saw kei had beaten me to it.

simon04 commented on 2015-03-27 07:58

Version 1.0 is still the newest one – unflagging.

The package builds nicely with `-Werror` set. Arch Linux generally tries to patch as little as necessary. Thus, optimization flags should be tuned by individual users if necessary. Otherwise an upstream patch should be submitted.

kei commented on 2015-02-06 09:52

I had to remove -Werror. Before "make":

sed -i -r 's/-Werror//' Makefile

Additionally, I enabled optimization as well (removes "#warning _FORTIFY_SOURCE requires compiling with optimization"):

sed -i -r 's/^OptDbg=.*$/OptDbg=-O2 -march=native/' Makefile

digitalfrost commented on 2014-01-05 06:19

I tried to compile this today and ran into two erros:

1. #warning _FORTIFY_SOURCE requires compiling with optimization (-O) [-Werror=cpp]

2. #warning _FORTIFY_SOURCE requires compiling with optimization (-O) [-Werror=cpp]

I fixed this by adding CPPFLAGS="$CPPFLAGS -O2 -Wno-error" to the PKGBUILD.