Date: Sun, 9 Apr 2000 08:28:54 +0200 (IST) From: Eli Zaretskii X-Sender: eliz AT is To: Pierre Muller cc: djgpp-workers AT delorie DOT com Subject: Re: Compiling GDB for DJGPP In-Reply-To: <200004071115.NAA13840@cerbere.u-strasbg.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Reply-To: djgpp-workers AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp-workers AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Fri, 7 Apr 2000, Pierre Muller wrote: > I still got several warnings in gnu-regex.c compilation > configure has set > ENABLE_NLS and HAVE_GETTEXT to 1 Did you use the original configure script directly? That's not what you are supposed to do; see the file gdb/config/djgpp/README for instructions on how to configure and build GDB with DJGPP. The DJGPP-specific configure script sets things up so that NLS is disabled and gettext never gets linked in. > gnu-regex.c: In function `re_compile_pattern': > gnu-regex.c:5470: warning: return makes pointer from integer without a cast > gnu-regex.c: In function `re_comp': > gnu-regex.c:5500: warning: return makes pointer from integer without a cast > gnu-regex.c: In function `regerror': > gnu-regex.c:5824: warning: assignment makes pointer from integer without a > cast > > all lines have expressions of style : > > return gettext (re_error_msgid[(int) ret]); This usually means that the prototype of gettext is not visible to the compiler. But I never configured GDB with the NLS support (it won't work with DJGPP anyway, due to differences in how non-ASCII characters are encoded), so I don't think it's worth your time to debug this. Simply use the provided DJGPP-specific script to configure and build.