Thread: Re: [HACKERS] looking for rh9 rpms for pgadmin
Well, I'm sorry to say I still can't get rid of the warning.
From: Dave Cramer [mailto:pg@fastcrypt.com]
Sent: 17 January 2005 21:50
To: Dave Page
Cc: Andreas Pflug; pgadmin-hackers
Subject: Re: [pgadmin-hackers] [HACKERS] looking for rh9 rpms for pgadmin
wx-windows complete rebuild without the enable-debug option
complete rebuild of pgadmin3
and still the window pops up :(
When you reconfigured, just you use --disable-debug ? Might be worth trying as configure can remember
previous options and silently reuse them in my experience - explictly countering them, or a completely clean
rebuild is the only safe way.
Regards, Dave.
Dave,
I completely deleted the wx directory and did a clean build. I will try disable-debug
FYI, the error has nothing to do with libpq. I debugged it and it happens when trying to read the mime-types.
dave
Dave Page wrote:
I completely deleted the wx directory and did a clean build. I will try disable-debug
FYI, the error has nothing to do with libpq. I debugged it and it happens when trying to read the mime-types.
dave
Dave Page wrote:
Well, I'm sorry to say I still can't get rid of the warning.
From: Dave Cramer [mailto:pg@fastcrypt.com]
Sent: 17 January 2005 21:50
To: Dave Page
Cc: Andreas Pflug; pgadmin-hackers
Subject: Re: [pgadmin-hackers] [HACKERS] looking for rh9 rpms for pgadmin
wx-windows complete rebuild without the enable-debug option
complete rebuild of pgadmin3
and still the window pops up :(
When you reconfigured, just you use --disable-debug ? Might be worth trying as configure can remember previous options and silently reuse them in my experience - explictly countering them, or a completely clean rebuild is the only safe way.
Regards, Dave.-- Dave Cramer http://www.postgresintl.com 519 939 0336 ICQ#14675561
Dave Cramer wrote: > Dave, > > I completely deleted the wx directory and did a clean build. I will try > disable-debug > > FYI, the error has nothing to do with libpq. I debugged it and it > happens when trying to read the mime-types. Disable it according to the readme! --enable-mimetype=no Regards, Andreas
Which README ? I've read the unix_compilation.html and that isn't there. Dave Andreas Pflug wrote: > Dave Cramer wrote: > >> Dave, >> >> I completely deleted the wx directory and did a clean build. I will >> try disable-debug >> >> FYI, the error has nothing to do with libpq. I debugged it and it >> happens when trying to read the mime-types. > > > Disable it according to the readme! > --enable-mimetype=no > > > Regards, > Andreas > > -- Dave Cramer http://www.postgresintl.com 519 939 0336 ICQ#14675561
Andreas, Is this done in wx? I did it and it still asserts while trying to load the mimetypes ??? This is getting frustrating. Dave Andreas Pflug wrote: > Dave Cramer wrote: > >> Dave, >> >> I completely deleted the wx directory and did a clean build. I will >> try disable-debug >> >> FYI, the error has nothing to do with libpq. I debugged it and it >> happens when trying to read the mime-types. > > > Disable it according to the readme! > --enable-mimetype=no > > > Regards, > Andreas > > -- Dave Cramer http://www.postgresintl.com 519 939 0336 ICQ#14675561
Dave Cramer wrote: > Andreas, > > Is this done in wx? I did it and it still asserts while trying to load > the mimetypes ??? Absolutely: if you get asserts, your wx is compiled with debug on. Find all wx libs, delete them and rebuild without debug. There's no more tip to give. Regards, Andreas