On Wed, Aug 22, 2012 at 1:33 PM, Oleg Pekar (olpekar) wrote:
>>On Wed, Aug 22, 2012 at 12:38 PM, Oleg Pekar (olpekar)
>>wrote:
>>> I'm using gcc 4.1.2, it supports -D_FORTIFY_SOURCE option for c files but
>>> not for c++. I'm looking for gcc version number where support for this
>>> option in
>On Wed, Aug 22, 2012 at 12:38 PM, Oleg Pekar (olpekar)
>wrote:
>> I'm using gcc 4.1.2, it supports -D_FORTIFY_SOURCE option for c files but
>> not for c++. I'm looking for gcc version number where support for this
>> option in c++ files was added.
>I'm not sure how to answer your question, be
On Wed, Aug 22, 2012 at 12:38 PM, Oleg Pekar (olpekar)
wrote:
>
> I'm using gcc 4.1.2, it supports -D_FORTIFY_SOURCE option for c files but not
> for c++. I'm looking for gcc version number where support for this option in
> c++ files was added.
I'm not sure how to answer your question, because
Hi,
I'm using gcc 4.1.2, it supports -D_FORTIFY_SOURCE option for c files but not
for c++. I'm looking for gcc version number where support for this option in
c++ files was added.
Thanks,
Oleg
On Thu, 23 Aug 2012, jojelino wrote:
> On 2012-08-20 AM 6:44, Ji?í Pale?ek wrote:
> > Hello,
> >
> > I tried to run "make check-c++" from the top directory of the source
> > code. During the run, all of the libgomp tests run by it failed. From
> > the log file, you can see that the gcc from the sys
On 2012-08-20 AM 6:44, Jiří Paleček wrote:
Hello,
I tried to run "make check-c++" from the top directory of the source
code. During the run, all of the libgomp tests run by it failed. From
the log file, you can see that the gcc from the system (rather than the
gcc currently built) was run:
Exec
