This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [RFA/commit 2/2] Import gnulib's errno module.


>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:

Joel> I though libiconv had its own mechanism for defining EILSEQ.
Joel> Do you think the two are going to interfere?

It seems possible to me.

Suppose you have a system without EILSEQ and where libiconv is used.

libiconv will be compiled with its definition of EILSEQ.  This will
often be ENOENT, though I didn't read m4/eilseq.m4 in detail.

gnulib defines it as:

# ifndef EILSEQ
#  define EILSEQ 2015
#  define GNULIB_defined_EILSEQ 1
# endif


Now, if libiconv ever returns EILSEQ (I didn't check this), gdb will
either interpret the libiconv result properly, or not, depending on
whether the gnulib errno.h or libiconv.h is included first.

Tom


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]