From: Chris Faylor <cgf@cygnus.com>
To: Stan Shebs <shebs@shebs.cnchost.com>
Cc: overseers@sources.redhat.com
Subject: Re: Xconq Gnats needs a push?
Date: Tue, 05 Sep 2000 07:44:00 -0000 [thread overview]
Message-ID: <20000905104316.A2836@cygnus.com> (raw)
Message-ID: <20000905074400.sNj4zEaPJxMd_DAXmqVFfxVY-4hGUUW65Y5Eec-KHZQ@z> (raw)
In-Reply-To: <39B4874B.9AD463F1@shebs.cnchost.com>
On Mon, Sep 04, 2000 at 10:40:48PM -0700, Stan Shebs wrote:
>Chris Faylor wrote:
>>
>> On Sun, Sep 03, 2000 at 04:39:27PM -0700, Stan Shebs wrote:
>> >I tried submitting a test PR to the xconq database, and there's a
>> >file with the right data in gnats/xconq-db/gnats-queue, but it's
>> >just sitting there. There was an update to Java #337 since I
>> >submitted my test, so I know the system as a whole must be working.
>> >Perhaps a permission is missing somewhere?
>>
>> It looks like I skipped a "Add an entry to crontab" step when I
>> set this up. It should be fixed now.
>
>Thanks, that did the trick. And just by coincidence, a real
>PR showed up about ten minutes ago! Even more coincidentally,
>it's about difficulties building Xconq with cygwin, and you just
>might want to take a look at it... (It's xconq/2)
I did look at it. The person is apparently trying to build from a
version of the repository that was checked out a couple of weeks ago.
Or do you make snapshots?
In any event, this was a header file problem that was fixed by
this change to newlib:
2000-08-25 DJ Delorie <dj@redhat.com>
* libc/include/sys/unistd.h (environ): this one isn't from the
DLL, no __IMPORT
cgf
next prev parent reply other threads:[~2000-09-05 7:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-30 6:08 Stan Shebs
2000-09-03 16:38 ` Stan Shebs
2000-12-30 6:08 ` Chris Faylor
2000-09-04 22:23 ` Chris Faylor
2000-12-30 6:08 ` Stan Shebs
2000-09-04 22:40 ` Stan Shebs
2000-12-30 6:08 ` Chris Faylor [this message]
2000-09-05 7:44 ` Chris Faylor
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=20000905104316.A2836@cygnus.com \
--to=cgf@cygnus.com \
--cc=overseers@sources.redhat.com \
--cc=shebs@shebs.cnchost.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).