public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Angelo Graziosi <angelo.graziosi@alice.it>
To: Andrey Repin <cygwin@cygwin.com>
Cc: Andrey Repin <anrdaemon@freemail.ru>
Subject: Re: postgresql-devel package missing pg_config?
Date: Thu, 02 May 2013 21:25:00 -0000	[thread overview]
Message-ID: <5182D99C.7040300@alice.it> (raw)
In-Reply-To: <973335475.20130502213055@mtu-net.ru>

Il 02/05/2013 19.30, Andrey Repin ha scritto:
> Greetings, Angelo Graziosi!
>
>>      win32gcc             for Win32 with cygwin/gcc
>
> Cygwin gcc? Or mingw gcc? Or, ... ?
> In short, ... yeah, what Earnie Boyd said earlier. Just plain wrong.
>
>

The "Supported Architectures" cited in [*] are "configure" options:

$ PATH-TO/configure win32gcc [...]   # for the Cygwin build

$ PATH-TO/configure win32 [...]      # for the Windows native build 
(using VC++)


For some historical reason, "win32gcc" identifies Cygwin. Probably, 
these days, they should change the option to "cygwin"  (better: 
"cygwin32" or "cygwin64", in view of Cygwin development)

I am building ROOT on Cygwin since 2003. Usually the build on Cygwin 
results in these features:

$ root-config --features
asimage astiff builtin_afterimage builtin_ftgl builtin_glew builtin_zlib 
cintex explicitlink fftw3 gdml genvector ldap mathmore minuit2 mysql 
odbc opengl pgsql pythia6 python qt qtgsi reflex roofit ruby shared 
soversion ssl table tmva unuran x11 xft xml thread

The next generation of ROOT (ROOT 6) will use clang++ (possibly 
bootstrapping it if it isn't found...)

For what I know, they dont't use Mingw.


Ciao,
  Angelo.


---
[*] http://cygwin.com/ml/cygwin/2013-05/msg00013.html


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2013-05-02 21:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-01 14:44 Angelo Graziosi
2013-05-01 16:58 ` Earnie Boyd
2013-05-02 17:35 ` Andrey Repin
2013-05-02 21:25   ` Angelo Graziosi [this message]
2013-05-03  1:14     ` Christopher Faylor
  -- strict thread matches above, loose matches on Subject: below --
2013-05-03  8:09 Angelo Graziosi
2013-05-01 10:39 Angelo Graziosi
2013-05-01 12:37 ` marco atzeri
     [not found] <51803D26.2060806@alice.it>
2013-05-01  7:30 ` marco atzeri
2013-04-30 21:52 Jim Garrison
2013-04-30 23:36 ` Achim Gratz
2013-04-30 23:36   ` Jim Garrison

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5182D99C.7040300@alice.it \
    --to=angelo.graziosi@alice.it \
    --cc=anrdaemon@freemail.ru \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).