Has the FSF been asked to switch to plain GFDL so that we can move the
GCC docs to main? They did that for the autoconf documentation
recently.
--
bye,
pabs
http://wiki.debian.org/PaulWise
--
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble
Hi,
On 09/28/2012 01:05 AM, Игорь Пашев wrote:
> Why not just do GCC docs in a way similar to GNU Make?
> Separately build docs from separate source package, and upload to non-free?
> (with regular package names)
It's in a similar way to GNU Make indeed. The only difference is more
than one versi
Why not just do GCC docs in a way similar to GNU Make?
Separately build docs from separate source package, and upload to non-free?
(with regular package names)
2012/9/27 Guo Yixuan :
> Hi,
>
> On 02/15/2012 04:02 AM, Samuel Bronson wrote:
>> On Tue, Feb 7, 2012 at 2:59 PM, Samuel Bronson wrote:
>
Hi,
On 02/15/2012 04:02 AM, Samuel Bronson wrote:
> On Tue, Feb 7, 2012 at 2:59 PM, Samuel Bronson wrote:
>> On Sun, Feb 5, 2012 at 7:17 AM, Nikita V. Youshchenko
>> wrote:
>
>>> In good old days when I had time and motivation to maintain gcc-doc, I've
>>> used git repos to managed entire thin
Matthias Klose writes:
> On 27.09.2012 09:38, Olivier Sallou wrote:
>> The bug is not reproducible, so it is likely a hardware or OS problem.
>
> so what didn't you understand?
How GCC is so sure of that. I now see that it does literally try to
reproduce the error by re-running cc1plus. ncbi-b
Hello!
I have strange behaviour for this simple code (compiled with gcc test.cpp -
lpthread -o test):
#include
#include
#include
#include
#include
#include
#include
void *thread_proc(void *arg)
{
sigset_t sigs;
sigemptyset(&sigs);
sigaddset(&sigs, SIGTERM);
pthread_sigmask(SIG_BLOC
Le 9/27/12 3:37 PM, Matthias Klose a écrit :
> On 27.09.2012 09:38, Olivier Sallou wrote:
>> The bug is not reproducible, so it is likely a hardware or OS problem.
> so what didn't you understand?
This occurs on buildd servers, on Sparc only. I saw this bug faced the
same error, so I wonder if th
On 27.09.2012 09:38, Olivier Sallou wrote:
> The bug is not reproducible, so it is likely a hardware or OS problem.
so what didn't you understand?
--
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archiv
Hi,
we got a gcc crash during Sparc package build on buildd servers.
could be same kind of issue.
/usr/bin/g++ -c -Wall -Wno-format-y2k -pthread -O2 -fstack-protector
--param=ssp-buffer-size=4 -Wformat -Werror=format-security -fPIC-DNDEBUG
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_
9 matches
Mail list logo
