x86_64-pc-linux-gnu-gcc -std=gnu99 -DPKGDATADIR=\"/usr/share/mutt\" -DSYSCONFDIR=\"/etc/mutt\" -DBINDIR=\"/usr/bin\" -DMUTTLOCALEDIR=\"/usr/share/locale\" -DHAVE_CONFIG_H=1 -DPREFIX=\"/usr/..\" -I. -I. -I. -I./imap -Iintl -I./intl -Wall -pedantic -Wno-long-long -march=core-avx2 -O2 -pipe -Wl,-O1 -Wl,--as-needed -c -o filter.o filter.c init.c: In function ‘parse_tag_transforms’: init.c:3939:5: error: too many arguments to function ‘hash_insert’ hash_insert(TagTransforms, tag, transform, 0); ^ In file included from mutt.h:64:0, from init.c:23: hash.h:55:5: note: declared here int hash_insert (HASH * table, const char *key, void *data); ^ init.c: In function ‘parse_tag_formats’: init.c:3970:5: error: too many arguments to function ‘hash_insert’ hash_insert(TagFormats, format, tag, 0); ^ In file included from mutt.h:64:0, from init.c:23: hash.h:55:5: note: declared here int hash_insert (HASH * table, const char *key, void *data); ^ x86_64-pc-linux-gnu-gcc -std=gnu99 -DPKGDATADIR=\"/usr/share/mutt\" -DSYSCONFDIR=\"/etc/mutt\" -DBINDIR=\"/usr/bin\" -DMUTTLOCALEDIR=\"/usr/share/locale\" -DHAVE_CONFIG_H=1 -DPREFIX=\"/usr/..\" -I. -I. -I. -I./imap -Iintl -I./intl -Wall -pedantic -Wno-long-long -march=core-avx2 -O2 -pipe -Wl,-O1 -Wl,--as-needed -c -o from.o from.c Makefile:858: recipe for target 'init.o' failed make[2]: *** [init.o] Error 1 make[2]: *** Waiting for unfinished jobs.... make[2]: Leaving directory '/var/tmp/portage/mail-client/mutt-1.8.0/work/mutt-1.8.0' Makefile:888: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '/var/tmp/portage/mail-client/mutt-1.8.0/work/mutt-1.8.0' Makefile:557: recipe for target 'all' failed make: *** [all] Error 2 * ERROR: mail-client/mutt-1.8.0::gentoo failed (compile phase): * emake failed * * If you need support, post the output of `emerge --info '=mail-client/mutt-1.8.0::gentoo'`, * the complete build log and the output of `emerge -pqv '=mail-client/mutt-1.8.0::gentoo'`. * The complete build log is located at '/var/tmp/portage/mail-client/mutt-1.8.0/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/mail-client/mutt-1.8.0/temp/environment'. * Working directory: '/var/tmp/portage/mail-client/mutt-1.8.0/work/mutt-1.8.0' * S: '/var/tmp/portage/mail-client/mutt-1.8.0/work/mutt-1.8.0' [91.0.3@papaya /] Phase: >>> Failed to emerge mail-client/mutt-1.8.0, Log file: >>> '/var/tmp/portage/mail-client/mutt-1.8.0/temp/build.log' * Messages for package mail-client/mutt-1.8.0: * ERROR: mail-client/mutt-1.8.0::gentoo failed (compile phase): * emake failed * * If you need support, post the output of `emerge --info '=mail-client/mutt-1.8.0::gentoo'`, * the complete build log and the output of `emerge -pqv '=mail-client/mutt-1.8.0::gentoo'`. * The complete build log is located at '/var/tmp/portage/mail-client/mutt-1.8.0/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/mail-client/mutt-1.8.0/temp/environment'. * Working directory: '/var/tmp/portage/mail-client/mutt-1.8.0/work/mutt-1.8.0' * S: '/var/tmp/portage/mail-client/mutt-1.8.0/work/mutt-1.8.0'
Created attachment 465330 [details] build.log
On this commit https://github.com/neomutt/neomutt/commit/fc76e49251c0d1d1ea27cc4aa84c1fd58967925e was changed hash api. hash_insert no more require allow_dup argument.(In reply to Leho Kraav (:macmaN @lkraav) from comment #1)
Created attachment 465378 [details, diff] Patche resolves api change
What USE-flags were used here? I thought I fixed all of these.
(In reply to Fabian Groffen from comment #4) > What USE-flags were used here? I thought I fixed all of these. build.log has USE: abi_x86_64 amd64 crypt elibc_glibc gdbm hcache idn imap kernel_linux nls notmuch sidebar ssl userland_GNU
(In reply to Jiri Netolicky from comment #3) > Created attachment 465378 [details, diff] [details, diff] > Patche resolves api change Patch is fine, but I need to know what patch introduces it so I can fix the right patch. It happens to be the notmuch patch, applied it there now. I think upstream is going to push a patch today to fix some SSL cert issues, so I might wait a little bit before releasing this fix. You can use the user-patches support if you don't want to wait. Jiri's patch is the fix.
*** Bug 613198 has been marked as a duplicate of this bug. ***
Ok, this took somewhat longer than anticipated, sorry. Should be in -r1 now.