[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: gnulib woes & run-octave fails, suggestions?
From: |
Jarno Rajahalme |
Subject: |
Re: gnulib woes & run-octave fails, suggestions? |
Date: |
Wed, 7 Apr 2010 10:01:57 -0700 |
This quote from build-aux/warn-on-use.h:
"this implies that _GL_WARN_ON_USE is only safe to
use if FUNCTION is known to already have a declaration."
Jarno
On Apr 7, 2010, at 9:29 AM, ext Jarno Rajahalme wrote:
>
> It seems to me that the_GL_CXXALIASWARN should be compiled only if the system
> has the function in question, like this:
>
> # if @HAVE_FCHOWNAT@
> _GL_CXXALIASWARN (fchownat);
> # endif
>
>
> Also, it seems that the __warning__ in GCC 4.4.3 (or 4.4.2, tried both) is
> not working properly, as I get over a hundred of these warnigns, even when
> the source has the gnulib:: before the respective function name.
>
>
> Regards,
>
> Jarno
>
>
> On Apr 4, 2010, at 8:10 AM, ext John W. Eaton wrote:
>
>> On 2-Apr-2010, Jarno Rajahalme wrote:
>>
>> | I' trying to compile the development version of Octave, and have
>> | encountered some gnulib-related problems:
>> |
>> | 1. My system does not have fchownat, and compilation fails in misc/quit.cc:
>> |
>> | libtool: compile: /opt/local/bin/g++-mp-4.4 -DHAVE_CONFIG_H -I. -I..
>> -I/opt/local/include -I../libgnu -I../libgnu -I/opt/local/include -O0 -m64
>> -DHAVE_CONFIG_H -I/opt/local/include -I/opt/local/include/freetype2
>> -I/opt/local/include -I/opt/local/include -Wall -W -Wshadow -Wold-style-cast
>> -Wformat -O0 -m64 -D_THREAD_SAFE -pthread -O0 -m64 -MT
>> misc/libcruft_la-quit.lo -MD -MP -MF misc/.deps/libcruft_la-quit.Tpo -c
>> misc/quit.cc -fno-common -DPIC -o misc/.libs/libcruft_la-quit.o
>> | In file included from
>> /opt/local/include/gcc44/c++//x86_64-apple-darwin10/bits/gthr-default.h:42,
>> | from
>> /opt/local/include/gcc44/c++//x86_64-apple-darwin10/bits/gthr.h:162,
>>
>> So this is an OS X system?
>>
>> Precisely what "development version" are you trying to compile?
>>
>> Is the your copy of the gnulib sources up to date? It changes
>> frequently.
>>
>> jwe
>
>
- gnulib woes & run-octave fails, suggestions?, Jarno Rajahalme, 2010/04/02
- Re: gnulib woes & run-octave fails, suggestions?, Jarno Rajahalme, 2010/04/02
- Re: gnulib woes & run-octave fails, suggestions?, Jarno Rajahalme, 2010/04/02
- gnulib woes & run-octave fails, suggestions?, John W. Eaton, 2010/04/04
- Re: gnulib woes & run-octave fails, suggestions?,
Jarno Rajahalme <=