Bug#634546: gnat-4.6: FTBFS: make[4]: *** No rule to make target `../gcc/ada/rts-shared-zcx/libgnat-.so', needed by `gnattools-native'. Stop.

2011-07-18 Thread Lucas Nussbaum
Source: gnat-4.6 Version: 4.6.1-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110718 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[5]: Enter

Bug#634200: marked as done (gcc -Wall -Werror -lncurses fails to link wide-character ncursesw functions.)

2011-07-18 Thread Debian Bug Tracking System
Your message dated Mon, 18 Jul 2011 19:14:25 +0200 with message-id <4e2469f1.8020...@debian.org> and subject line Re: Bug#634200: #634200 gcc -Wall -Werror -lncurses fails to link wide-character ncursesw functions. has caused the Debian Bug report #634200, regarding gcc -Wall -Werror -lncurses fai

Bug#634200: #634200 gcc -Wall -Werror -lncurses fails to link wide-character ncursesw functions.

2011-07-18 Thread Matthias Klose
On 07/18/2011 04:39 PM, Ray Dillinger wrote: >> plus, your example will fail when using -Wl,--as-needed. move the > library behind >> the objects. > > Okay... The synopsis of gcc in the man page says the file to be > compiled should come last in the compile line. That's the only thing > I can se

Bug#634200: gcc -Wall -Werror -lncurses fails to link wide-character ncursesw functions.

2011-07-18 Thread Ray Dillinger
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/18/2011 02:31 AM, Kalle Olavi Niemitalo wrote: > Ray Dillinger writes: > >> display.c starts with the lines: >> >> >> #define _X_OPEN_SOURCE_EXTENDED > > There is an extra underscore after the X. > Correcting that fixes the implicit-declaratio

Bug#634200: #634200 gcc -Wall -Werror -lncurses fails to link wide-character ncursesw functions.

2011-07-18 Thread Ray Dillinger
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 >> bear@janus:~/src/xxh$ make display.o >> gcc -D_XOPEN_SOURCE_EXTENDED -Wall -Werror -lncursesw -c -o display.o \ >> display.c >> bear@janus:~/src/xxh$ > > should't the ncursesw headers be used? Sorry, don't understand your message. The ncursesw head

Bug#634200: gcc -Wall -Werror -lncurses fails to link wide-character ncursesw functions.

2011-07-18 Thread Kalle Olavi Niemitalo
Ray Dillinger writes: > display.c starts with the lines: > > > #define _X_OPEN_SOURCE_EXTENDED There is an extra underscore after the X. Correcting that fixes the implicit-declaration error for me. Also, for consistency with other uses of this macro, it would be best to define it with the value

Bug#634200: #634200 gcc -Wall -Werror -lncurses fails to link wide-character ncursesw functions.

2011-07-18 Thread Thomas Dickey
On Mon, 18 Jul 2011, Matthias Klose wrote: On 07/18/2011 07:35 AM, Ray Dillinger wrote: On 07/17/2011 05:10 PM, Thomas Dickey wrote: You're seeing implicit for get_wch, since there's no _XOPEN_SOURCE_EXTENDED in the compile line. Okay, after checking: bear@janus:~/src/xxh$ make display.o g

Bug#634200: #634200 gcc -Wall -Werror -lncurses fails to link wide-character ncursesw functions.

2011-07-18 Thread Matthias Klose
On 07/18/2011 07:35 AM, Ray Dillinger wrote: > On 07/17/2011 05:10 PM, Thomas Dickey wrote: > >> You're seeing implicit for get_wch, since there's no _XOPEN_SOURCE_EXTENDED >> in the compile line. > > Okay, after checking: > > bear@janus:~/src/xxh$ make display.o > gcc -D_XOPEN_SOURCE_EXTENDED

Bug#634200: #634200 gcc -Wall -Werror -lncurses fails to link wide-character ncursesw functions.

2011-07-18 Thread Thomas Dickey
On Sun, 17 Jul 2011, Ray Dillinger wrote: On 07/17/2011 05:10 PM, Thomas Dickey wrote: fwiw, I routinely build with warnings enabled (and don't have a use for -Werror). For the rest - I'm typically seeing only extra warnings that you wouldn't see with -Wall (such as const mismatches, which are