On Fri, May 2, 2008 at 10:41 AM, Guillaume Lelarge
<[EMAIL PROTECTED]> wrote:
> I have no problem patching the EDB branch (when I'm allowed :) ).
>
You're always allowed - it's no different from any other stable branch
in that sense. It's only really there to make my life easier as I
needed to pu
Dave Page a écrit :
On Fri, May 2, 2008 at 10:19 AM, Guillaume Lelarge
<[EMAIL PROTECTED]> wrote:
You're right, it works now. I commited it (1.8 "standard" and EDB branches).
Cool - thanks.
And I should repeat, for the record, feel free to ignore the EDB
branch if you like - I don't expect yo
On Fri, May 2, 2008 at 10:19 AM, Guillaume Lelarge
<[EMAIL PROTECTED]> wrote:
> You're right, it works now. I commited it (1.8 "standard" and EDB branches).
Cool - thanks.
And I should repeat, for the record, feel free to ignore the EDB
branch if you like - I don't expect you to patch there as we
Dave Page a écrit :
On Thu, May 1, 2008 at 9:54 PM, Guillaume Lelarge
<[EMAIL PROTECTED]> wrote:
I don't find any. Perhaps we can wait a bit. If nobody asks for it, there's
no urgent need. It'll give us time to test the dev release with my latest
commit.
Does -Wno-write-strings do it?
http:
On Thu, May 1, 2008 at 9:54 PM, Guillaume Lelarge
<[EMAIL PROTECTED]> wrote:
> I don't find any. Perhaps we can wait a bit. If nobody asks for it, there's
> no urgent need. It'll give us time to test the dev release with my latest
> commit.
Does -Wno-write-strings do it?
http://gcc.gnu.org/onli
Guillaume Lelarge a écrit :
Dave Page a écrit :
[...]
(FYI, it applies great on the 1.8 branch)
I'm more hesitant to apply it there in case it breaks something. Can
we just silence the compiler warning - or are you and others on the
list more confident than I? :-)
I'm not that much confide
Dave Page a écrit :
On Thu, May 1, 2008 at 4:25 PM, Guillaume Lelarge
<[EMAIL PROTECTED]> wrote:
Dave Page a écrit :
OK. Should I apply it ?
Yes please, to trunk.
Done, thanks.
(FYI, it applies great on the 1.8 branch)
I'm more hesitant to apply it there in case it breaks something.
On Thu, May 1, 2008 at 4:25 PM, Guillaume Lelarge
<[EMAIL PROTECTED]> wrote:
> Dave Page a écrit :
>
>
> OK. Should I apply it ?
Yes please, to trunk.
> (FYI, it applies great on the 1.8 branch)
I'm more hesitant to apply it there in case it breaks something. Can
we just silence the compiler w
Dave Page a écrit :
On Thu, May 1, 2008 at 4:03 PM, Guillaume Lelarge
<[EMAIL PROTECTED]> wrote:
Dave Page a écrit :
[...]
As I see it we have three choices:
- Try using extern c on them (a suggestion from Greg Stark, though we
think that only affects linkage).
- Silence the warning on the G
On Thu, May 1, 2008 at 4:03 PM, Guillaume Lelarge
<[EMAIL PROTECTED]> wrote:
> Dave Page a écrit :
>
> > [...]
> >
> > As I see it we have three choices:
> >
> > - Try using extern c on them (a suggestion from Greg Stark, though we
> > think that only affects linkage).
> > - Silence the warning on
Dave Page a écrit :
[...]
As I see it we have three choices:
- Try using extern c on them (a suggestion from Greg Stark, though we
think that only affects linkage).
- Silence the warning on the GCC command line.
- Fix them.
I'm leaning towards fixing them to be honest.
Fixing them seems bett
On Thu, May 1, 2008 at 2:10 PM, Guillaume Lelarge
<[EMAIL PROTECTED]> wrote:
> Hi,
>
> Subject is not really true :) With the latest Kubuntu, I got the latest gcc
> release. Now, when I compile pgAdmin3 from sources, I get a whole bunch of
> warning messages:
>
> ../pgadmin/include/images/splash.
Guillaume Lelarge a écrit :
[...]
So, I tried to get a look at it. Using "const char*" instead of "char*"
seems to fix the issue, but this is getting bigger and bigger. All "char
*" variables should be replaced, but also every functions/methods
declarations using char* should be replaced with
Hi,
Subject is not really true :) With the latest Kubuntu, I got the latest
gcc release. Now, when I compile pgAdmin3 from sources, I get a whole
bunch of warning messages:
../pgadmin/include/images/splash.xpm:603: warning : deprecated
conversion from string constant to "char*"
It seems th
14 matches
Mail list logo
