public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Andrew Dunstan <andrew@dunslane.net>
To: marco atzeri <marco.atzeri@gmail.com>
Cc: cygwin@cygwin.com
Subject: Re: Binutils objcopy bug (was Re: rebase segfault)
Date: Mon, 04 Mar 2013 22:32:00 -0000	[thread overview]
Message-ID: <51352109.9040300@dunslane.net> (raw)
In-Reply-To: <5135127D.3050607@gmail.com>


On 03/04/2013 04:30 PM, marco atzeri wrote:
> On 3/4/2013 9:00 PM, Andrew Dunstan wrote:
>>
>> I have not heard a word on this in the 5 weeks or so since it was sent.
>> Are you guys interested in fixing this or not?
>
> yes Andrew,
> I am working on it, unfortunately this Makefile spaghetti
> is not nice to handle
>
> probably 90% is working now, but I just found
> that postgres.exe is incomplete
>
> attached current patch for my trial
>
> src/backend/Makefile needs some works for
> postgres.exe and libpostgres.a
>
> that I hope is the only missing bit
>


Incidentally, there is no need to change the test schedules, and such a 
patch would not be accepted. There is an option to restrict the number 
of concurrent connections the regression tests will run (designed 
specifically with Cygwin in mind, in fact, many years ago.) The way to 
do this is:

     make MAX_CONNECTIONS=10 check


cheers

andrew


--
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

  parent reply	other threads:[~2013-03-04 22:32 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-15  8:44 rebase segfault marco atzeri
2013-01-15 10:08 ` Corinna Vinschen
2013-01-15 10:36   ` marco atzeri
2013-01-15 11:24     ` Corinna Vinschen
2013-01-15 22:04       ` marco atzeri
2013-01-16  7:16         ` marco atzeri
2013-01-16 12:35           ` Binutils objcopy bug (was Re: rebase segfault) Corinna Vinschen
2013-01-16 13:38             ` marco atzeri
2013-01-16 14:42               ` Corinna Vinschen
2013-01-16 15:12                 ` marco atzeri
2013-01-16 16:26                   ` Corinna Vinschen
2013-01-24  9:02               ` Yaakov
2013-01-24  9:28                 ` Corinna Vinschen
2013-01-24  9:49                   ` marco atzeri
2013-01-24 10:01                     ` Corinna Vinschen
2013-01-24 10:16                       ` marco atzeri
2013-01-24 12:09                         ` Corinna Vinschen
2013-01-24 12:35                           ` marco atzeri
2013-01-24 14:12                             ` Corinna Vinschen
2013-01-25 12:34                       ` marco atzeri
2013-01-25 13:20                         ` Kai Tietz
2013-01-25 15:01                           ` Corinna Vinschen
2013-01-25 15:12                             ` marco atzeri
2013-01-26  6:32                               ` Reini Urban
2013-01-26  7:53                                 ` marco atzeri
2013-01-29 22:30                                   ` Reini Urban
2013-01-30 16:46                                     ` Andrew Dunstan
2013-01-30 17:03                                       ` marco atzeri
2013-03-04 20:01                                       ` Andrew Dunstan
2013-03-04 21:30                                         ` marco atzeri
2013-03-04 21:41                                           ` Andrew Dunstan
2013-03-04 22:32                                           ` Andrew Dunstan [this message]
2013-03-05  5:42                                             ` marco atzeri
2013-03-05 15:39                                               ` Andrew Dunstan
2013-01-25 13:22                         ` Kai Tietz
2013-01-24 15:56                     ` Christopher Faylor
2013-01-24 16:17                       ` marco atzeri
2013-01-18 15:34             ` marco atzeri
2013-01-18 15:44               ` Christopher Faylor
2013-01-19  8:56             ` marco atzeri
2013-01-19 15:23               ` Corinna Vinschen

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=51352109.9040300@dunslane.net \
    --to=andrew@dunslane.net \
    --cc=cygwin@cygwin.com \
    --cc=marco.atzeri@gmail.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).