Unix Technical Forum

Re: [PATCH] Buildfailure on OSX (10.3.9) + fix

This is a discussion on Re: [PATCH] Buildfailure on OSX (10.3.9) + fix within the pgsql Interfaces Pgadmin Hackers forums, part of the PostgreSQL category; --> Hi Florian-san. It was applied. Is the screen of OSX comfortable?:-) Thanks! Regards, Hiroshi Saito ----- Original Message ----- ...


Go Back   Unix Technical Forum > Database Server Software > PostgreSQL > pgsql Interfaces Pgadmin Hackers

FAQ Members List Calendar Search Today's Posts Mark Forums Read
  #1 (permalink)  
Old 04-17-2008, 07:47 PM
Hiroshi Saito
 
Posts: n/a
Default Re: [PATCH] Buildfailure on OSX (10.3.9) + fix

Hi Florian-san.

It was applied.
Is the screen of OSX comfortable?:-)
Thanks!

Regards,
Hiroshi Saito

----- Original Message -----
From: "Florian G. Pflug"


> Hi
>
> I've finally fixed my buildserver today, and discovered that
> the build of pgadmin3 trunk on OSX 10.3.9 (gcc 3.3) fails
> when compiling the debugger.
>
> Attached is a patch that fixes the problem, though I must admit
> that I soley found the fix through trial and error. I have
> absolutly no idea why gcc complains about
> wxString( wxString( PQsomething(result), wxConvUTF8 ))
> but has no problem with
> wxString( PQsomething(result), wxConvUTF8 )
>
> The error message is:
> wsDirectdbg.cpp: In member function `void
> wsDirectDbg::OnResultReady(wxCommandEvent&)':
> wsDirectdbg.cpp:608: error: parse error before `,' token
>
> Does someone have the slighest idea what gcc is unhappy about?
> Anyway, patch is attached.
>
> greetings, Florian Pflug
>



--------------------------------------------------------------------------------


> Index: debugger/wsDirectdbg.cpp
> ================================================== =================
> --- debugger/wsDirectdbg.cpp (revision 6146)
> +++ debugger/wsDirectdbg.cpp (working copy)
> @@ -605,7 +605,7 @@
>
> if(( PQresultStatus( result ) == PGRES_NONFATAL_ERROR ) || ( PQresultStatus( result ) == PGRES_FATAL_ERROR ))
> {
> - wxString message( wxString(PQresultErrorMessage( result ), wxConvUTF8));
> + wxString message( PQresultErrorMessage( result ), wxConvUTF8 ) ;
>
> message.Replace( wxT( "\r" ), wxT( "" ));
> message.Replace( wxT( "\n" ), wxT( " " ));
> @@ -615,7 +615,7 @@
> }
> else
> {
> - wxString message( wxString( PQcmdStatus( result ), wxConvUTF8 ));
> + wxString message( PQcmdStatus( result ), wxConvUTF8 );
>
> message.Replace( wxT( "\r" ), wxT( "" ));
> message.Replace( wxT( "\n" ), wxT( " " ));
> @@ -667,7 +667,7 @@
>
> if(( PQresultStatus( rawResult ) == PGRES_NONFATAL_ERROR ) || ( PQresultStatus( rawResult ) == PGRES_FATAL_ERROR ))
> {
> - wxString message( wxString( PQresultErrorMessage( rawResult ), wxConvUTF8 ));
> + wxString message( PQresultErrorMessage( rawResult ), wxConvUTF8 );
>
> message.Replace( wxT( "\r" ), wxT( "" ));
> message.Replace( wxT( "\n" ), wxT( " " ));
> @@ -677,7 +677,7 @@
> }
> else
> {
> - wxString message( wxString( PQcmdStatus( rawResult ), wxConvUTF8 ));
> + wxString message( PQcmdStatus( rawResult ), wxConvUTF8 );
>
> message.Replace( wxT( "\r" ), wxT( "" ));
> message.Replace( wxT( "\n" ), wxT( " " ));
> Index: debugger/wsQueryWindow.cpp
> ================================================== =================
> --- debugger/wsQueryWindow.cpp (revision 6146)
> +++ debugger/wsQueryWindow.cpp (working copy)
> @@ -176,7 +176,7 @@
>
> if(( PQresultStatus( result ) == PGRES_NONFATAL_ERROR ) || ( PQresultStatus( result ) == PGRES_FATAL_ERROR ))
> {
> - wxString message( wxString( PQresultErrorMessage( result ), wxConvUTF8 ));
> + wxString message( PQresultErrorMessage( result ), wxConvUTF8 );
>
> message.Replace( wxT( "\r" ), wxT( "" ));
> message.Replace( wxT( "\n" ), wxT( " " ));
>



--------------------------------------------------------------------------------


>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings
>


---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #2 (permalink)  
Old 04-17-2008, 07:47 PM
Florian G. Pflug
 
Posts: n/a
Default Re: [PATCH] Buildfailure on OSX (10.3.9) + fix

Hiroshi Saito wrote:
> Hi Florian-san.
>
> It was applied. Is the screen of OSX comfortable?:-)

Yeah, it builds now. Thanks for applying!

I'd still like to understand why this patch is needed, though -
to me it seems like a blatant bug in the gcc c++ parser,
but I somehow doubt this.

Any ideas?

greetings, Florian Pflug


---------------------------(end of broadcast)---------------------------
TIP 7: You can help support the PostgreSQL project by donating at

http://www.postgresql.org/about/donate

Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
Reply


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On
Forum Jump


All times are GMT. The time now is 01:21 AM.


Powered by vBulletin® Version 3.6.5
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
SEO by vBSEO 3.2.0
www.UnixAdminTalk.com