From: ludo@gnu.org (Ludovic Courtès)
To: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
Cc: 32382-done@debbugs.gnu.org
Subject: bug#32382: libchop has build failures
Date: Sun, 19 Aug 2018 18:30:01 +0200 [thread overview]
Message-ID: <87efeugvzq.fsf@gnu.org> (raw)
In-Reply-To: <20180807014944.21341234@alma-ubu> ("Björn Höfling"'s message of "Tue, 7 Aug 2018 01:49:44 +0200")
Hello,
Björn Höfling <bjoern.hoefling@bjoernhoefling.de> skribis:
> Build log at failure:
>
> libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../include/chop -I../include -I../i
> nclude -I../lib -I../lib -DGCRYPT_NO_MPI_MACROS -DGCRYPT_NO_DEPRECATED -I/gnu/st
> ore/dysmb6hz7rr5rvcb05p23dazc5hz26qm-libgcrypt-1.8.2/include -I/gnu/store/a5rd4s
> qyljb9gs58z9hq4kswqmxa45nr-libgpg-error-1.28/include -Wcast-align -Wall -Wmissin
> g-prototypes -Wpointer-arith -fno-strict-aliasing -g -O2 -MT libchop_la-chopper-
> anchor-based.lo -MD -MP -MF .deps/libchop_la-chopper-anchor-based.Tpo -c chopper
> -anchor-based.c -fPIC -DPIC -o .libs/libchop_la-chopper-anchor-based.o
> chopper-anchor-based.c:120:3: warning: #warning "Not compiling the Lightning cod
> e" [-Wcpp]
> # warning "Not compiling the Lightning code"
> ^
> In file included from chop.c:545:0:
> class-lookup.c:115:1: error: conflicting types for 'chop_lookup_class_entry'
> chop_lookup_class_entry (register const char *str, register size_t len)
> ^
> chop.c:542:1: note: previous declaration of 'chop_lookup_class_entry' was here
> chop_lookup_class_entry (const char *str, unsigned int len);
> ^
> make[2]: *** [Makefile:1253: libchop_la-chop.lo] Error 1
Fixed in c9f898cd313db2f0bd320357c7571e155feffc4c, with additional fixes
in 6d1a7ce8ea52613963684e6545f6fb3e32d84181.
Note that the thing is unmaintained though…
Thanks,
Ludo’.
prev parent reply other threads:[~2018-08-19 16:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-06 23:49 bug#32382: libchop has build failures Björn Höfling
2018-08-19 16:30 ` Ludovic Courtès [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=87efeugvzq.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=32382-done@debbugs.gnu.org \
--cc=bjoern.hoefling@bjoernhoefling.de \
/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).