compiling source code!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

sibel karaasma schrieb:

Hi I'm a new postgresql user. I wrote ACO (ant colony optimazition) and
want to replace it with GEQO in postres/src/backend/optimizer but I
don't know how
to compile and run the source code :(

I installed postgresql-8.1.3 and cygwin but I can not use them to
compile the source code. I want to compare GEQO and ACO optimizers
performance using a small database

Can you help me???????

download the src package via cygwin.com/setup.exe
and check out the buildscript to see the used configure parameters and
get all the dependencies right.

--
Reini

On Wed, May 24, 2006 at 01:46:19AM -0700, sibel karaasma wrote:

Hi I'm a new postgresql user. I wrote ACO (ant colony optimazition) and
want to replace it with GEQO in postres/src/backend/optimizer but I don't know how
to compile and run the source code :(

I installed postgresql-8.1.3 and cygwin but I can not use them to
compile the source code. I want to compare GEQO and ACO optimizers performance using a small database

mingw is now the approved build method for windows, and I think there's
instructions on how to build PostgreSQL with it somewhere, though I
can't seem to find them now. Though to be honest, you'd probably find it
easier doing development on any kind of a unix box, including OS X.
--
Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461

Hi Sibel,

Here's the mail that I posted about 10 days ago about compiling
and debugging postgres on windows. I have used msys/mingw toolkit and
it is the recommended (by pg community) toolkit to compile postgres on
windows.

http://archives.postgresql.org/pgsql-hackers/2006-05/msg00396.php

Hope it helps. Do let me know if you face any problems.

Regards,
Gurjeet.

Also, I would recommend uninstalling cygwin before you install
mingw, because if the mingw doesn't behave properly (gcc won't compile
files etc...), you could be sure that there definitely is a conflict
between the cygwin and mingw.

If you don't wish to uninstall cygwin, at least rename the folder
to someting else (cygwin.before.mingw) so that you don't accidentally
use cygwin's binaries.

Regards,
Gurjeet.

Gurjeet Singh said:

Also, I would recommend uninstalling cygwin before you install
mingw, because if the mingw doesn't behave properly (gcc won't compile
files etc...), you could be sure that there definitely is a conflict
between the cygwin and mingw.

If you don't wish to uninstall cygwin, at least rename the folder
to someting else (cygwin.before.mingw) so that you don't accidentally
use cygwin's binaries.

This is complete nonsense. I have Cygwin and Mingw/Msys living quite happily
side by side on the same box. Each is largely ignorant of the other.

Of course, if you add Cygwin to the system path you can cause problems, so
don't do that. But there is no need at all that I know of to uninstall or
rename anything.

If you have problems with your setup please ask for help, instead of handing
out wrong advice.

cheers

andrew

I was just telling one of the ways to avoid the conflicts. It
generally happens that a newbie adds the cygwin paths to the env
variables and if he forgets to remove those, then, you know better,
which tools he'd be using!!! In such cases, a less experienced person
would just give up.

I remember that if I hadn't had that small peice of advice from
AumAum, I was on the verge of giving up on trying the mingw
installation aftar failing 3 times!!!

<quote>
It's crucial to crack the tarballs into /mingw (C:\msys\n.n\mingw),
because if you crack any of them into / (C:\msys\n.n), you'll cause
some subtle conflicts between MSYS and the MinGW tools which will
cause your compilations to fail.
</quote>
from http://www.mingw.org/MinGWiki/index.php/RealDumbQuickstart

So my suggestion was just to at least rename the folder
temporarily till sibel gets everything started.

Moreover, I dont think one would need cygwin after having mingw. I
might be wrong!

Yes, I agree your approach is more non-intrusive.

Sibel, just add the method of 'removing cygwin's paths from
environment variables (if they exist)' to the top of the
pre-requisites-list before you try installing mingw.

Sorry for uiintentionally misleading someone, if I did!

Regards,
Gurjeet