-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This bug also affects subsequent versions of this package,
libstdc++6-4.6-doc and libstdc++6-4.7-doc
Today I typed "man std::mutex" and my system told me there was no man
page for something that I know is part of the c++ standard library. So
I went
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/12/2012 10:13 AM, Matthias Klose wrote:
> On 11.07.2012 19:21, Ray Dillinger wrote:
>> This is the standard library. It's totally fundamental. We
>> can't allow Debian systems for programmers to NOT have man pages
>
Package: gcc
Version: 4:4.4.5-1
Severity: normal
Tags: l10n
In reply to your
Fwd: Message with no Package: tag cannot be processed!(...)
(reportbug fails on my system due to sendmail not being installed.
Like most sane people I use Qmail. should I file a bug against
reportbug?)
original me
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
> problematic).
>
> That's for ncu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
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 -Wall -Werror
-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
-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.
7 matches
Mail list logo
