Compilation error on Gentoo AMD64 #13

Closed
richardash1981 opened this Issue Sep 25, 2012 · 1 comment

Comments

Projects
None yet
2 participants
@richardash1981

As per comment on Gentoo bug 432914 (https://bugs.gentoo.org/show_bug.cgi?id=432914), it doesn't compile for me with -Werror in the CFLAGS

make -j 6 -l 4.0 SYSTEM=linux PBKDF_BACKEND=gcrypt program lib
x86_64-pc-linux-gnu-gcc -O2 -march=native -mtune=native -pipe -fomit-frame-pointer -Wsystem-headers -Werror -Wall -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wold-style-definition -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -D_GNU_SOURCE -o tcplay main.c tcplay.c crc32.c safe_mem.c io.c hdr.c humanize.c crypto.c generic_xts.c crypto-gcrypt.c pbkdf2-gcrypt.c -lgcrypt -ldevmapper -luuid -Wl,-O1 -Wl,--as-needed
cc1: warnings being treated as errors
io.c: In function ‘read_passphrase’:
io.c:388:3: error: signed and unsigned type in conditional expression
io.c:388:3: error: signed and unsigned type in conditional expression
make: *** [program] Error 1

I can't see immediately why this error occurs - I think the macro is getting in the way. Eliminating -Werror enables it to build (not surprisingly).

@bwalex

This comment has been minimized.

Show comment Hide comment
@bwalex

bwalex Sep 29, 2012

Owner

Hi, sorry for the delay.

This looks like a gentoo bug rather; as you mention in your gentoo bug report, the arguments to FD_SET are of the correct type. It could be a namespace issue, but I don't see anything regarding different namespace versions of FD_SET, either.

Owner

bwalex commented Sep 29, 2012

Hi, sorry for the delay.

This looks like a gentoo bug rather; as you mention in your gentoo bug report, the arguments to FD_SET are of the correct type. It could be a namespace issue, but I don't see anything regarding different namespace versions of FD_SET, either.

@bwalex bwalex closed this Feb 22, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment