public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf-rcm@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: getopt: ugly linker messages
Date: Sun, 21 Sep 2003 00:04:00 -0000	[thread overview]
Message-ID: <20030921000222.GA17518@redhat.com> (raw)
In-Reply-To: <000401c37fd1$0d5ce4f0$0100000a@PCHOMEISW>

On Sun, Sep 21, 2003 at 01:43:54AM +0200, Ivan Warren wrote:
>>Sigh.  By "research", I meant dive into the binutils code and figure
>>out what is going wrong.
>
>Geez..  You kidding me ?  I mean, I wouldn't mind doing that..

Are you not a native English speaker or are you just trolling now?

This is what I said:

"Apparently, no one knows the answer to your question and, apparently,
no one is interested in researching the problem for you."

In this context, it is clear what I was saying.  I was saying that no
one *else* wanted to *debug* your problem.  I wasn't saying "You do it",
even though, realistically speaking, that is probably your best
alternative.

(and now here comes another round of "I've already worked so hard and I
don't know nothing about no binutils"...)

>>You already posted to the binutils mailing list, remember?
>
>Yeah..  Of course I do remember that..  (not senile yet ;-) )..  But
>unfortunatelly, I made the same mistake I did here : I told them I
>*DID* post in the other forum.  Thus leading to the effect that each
>list thinks it's a problem that is in the other group field of
>expertise.

You're assuming here.  This is obviously a binutils issue.  The fact
that no one responded to it, is very likely the same reason that no
one responded here.

>So my option is now to tell the binutils folks that the cygwin folks
>are declaring this issue to be a binutils core issue and that it has
>nothing to do with cygwin (although it does affect it)..  Am I correct
>?

I would assume that anyone in the binutils mailing list who saw errors
with import libraries would not assume "Aha! It's obviously a problem
with the Cygwin DLL! I don't have to worry about this one".  So, anyone
who was interested in this problem would already be clear on where the
fault lies from your original message.

Just to be clear: I do provide the binutils package to the cygwin
community but I don't have the time or inclination to track the problem
down.  There are a few people reading the binutils mailing list who are
more facile with the code than I.  They are, of course, also volunteers.

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

  reply	other threads:[~2003-09-21  0:02 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-18 19:56 Bryan Higgins
2003-09-18 19:57 ` Christopher Faylor
2003-09-19  3:54   ` Charles Wilson
2003-09-19  7:03     ` Corinna Vinschen
2003-09-19 14:22       ` Charles Wilson
2003-09-19 15:20         ` Christopher Faylor
2003-09-19 15:38           ` Corinna Vinschen
2003-09-19 18:03           ` Larry Hall
2003-09-19 18:57           ` Ivan Warren
2003-09-20  1:12             ` Ivan Warren
2003-09-20 19:40               ` Ivan Warren
2003-09-20 20:52                 ` Christopher Faylor
2003-09-20 20:58                   ` Ivan Warren
2003-09-20 23:31                     ` Christopher Faylor
2003-09-21  0:02                       ` Ivan Warren
2003-09-21  0:04                         ` Christopher Faylor [this message]
2003-09-21  2:32                           ` Ivan Warren
2003-09-21  8:18                           ` PE Linker and/or runtime error when importing data from DLL (was RE: getopt: ugly linker messages) - hopefully solved Ivan Warren
2003-09-18 20:13 getopt: ugly linker messages Bryan Higgins
2003-09-18 20:18 ` Christopher Faylor
2003-09-18 20:48 Bryan Higgins
2003-09-18 21:46 ` Rolf Campbell
2003-09-19 22:14 Danny Smith
2003-09-20  9:53 ` 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=20030921000222.GA17518@redhat.com \
    --to=cgf-rcm@cygwin.com \
    --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).