Skip site navigation (1) Skip section navigation (2)

Re: pgAdmin3 1.4 stability issues on ubuntu/dapper

From: "Magnus Hagander" <mha(at)sollentuna(dot)net>
To: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>,"Florian G(dot) Pflug" <fgp(at)phlo(dot)org>
Cc: "pgadmin-hackers" <pgadmin-hackers(at)postgresql(dot)org>
Subject: Re: pgAdmin3 1.4 stability issues on ubuntu/dapper
Date: 2006-06-24 11:29:25
Message-ID: 6BCB9D8A16AC4241919521715F4D8BCEA0FA82@algol.sollentuna.se (view raw or flat)
Thread:
Lists: pgadmin-hackers
> > Hm, they are using gcc 4.0.3 by default. Since using that compiled 
> > lead to a pgadmin3 that wouldn't even start up, I'm now 
> using gcc 3.3. 
> > Of course, wx is compiled with 3.3 too, but gtk and friends are the 
> > ubuntu version, and therefore compiled with 4.0.3 I 
> believe. But for 
> > _C_ code, mixing compiler versions shouldn't hurt, should it?
> 
> It certainly can do (recent example; wx built with VC++ 6.0 
> won't work with pgAdmin built with VC++ 8.0 at all). Dunno if 
> there are any incompatible changes between the GCC versions though.

That's not because the *compilers* are different, that is because they
link to different versions of the runtime (libc/msvcrt versions). This
is documented as safe if and only if you don't pass CRT pointers between
the two modules. (for example, this kills gettext because of the
overriding of the *printf* functions)

As long as the lib is the same, the compiler *sohuldn't* matter. That's
not to say that it's so in reality, though ;-)


//Magnus

In response to

pgadmin-hackers by date

Next:From: svnDate: 2006-06-27 19:20:43
Subject: SVN Commit by dpage: r5238 - trunk/pgadmin3/src/frm
Previous:From: Dave PageDate: 2006-06-23 13:45:41
Subject: Re: pgAdmin3 1.4 stability issues on ubuntu/dapper

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group