My apologies.
I finally decided to look for myself in binutils.. And found a way to fix
the issue.
I proposed a patch to the binutils folks.
--Ivan
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: h
>
> 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 sayi
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
>
> 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.. But it would
probably take me a month or so to just figure out the basics of how it
works... Not to mention I have but very little unde
On Sat, Sep 20, 2003 at 10:51:43PM +0200, Ivan Warren wrote:
>>Bingo. Apparently, no one knows the answer to your question and,
>>apparently, no one is interested in researching the problem for you.
>>Also, as you noted, it has a trivially easy workaround -- don't strip
>>import libraries.
>
>Righ
>
> Bingo. Apparently, no one knows the answer to your question
> and, apparently, no one is interested in researching the
> problem for you. Also, as you noted, it has a trivially easy
> workaround -- don't strip import libraries.
Right..
- No one is interrested in researching the problem f
On Sat, Sep 20, 2003 at 09:32:52PM +0200, Ivan Warren wrote:
>I know this is a community effort and that no-one is obliged to answer
>(no, I didn't go for the pay support.. I am working on an open source
>project, so I don't have the monetary resource to spend).
Bingo. Apparently, no one knows t
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Ivan Warren
> Sent: Saturday, September 20, 2003 2:43 AM
> To: [EMAIL PROTECTED]
> Subject: RE: getopt: ugly linker messages
>
>
> > And.. Hmmm..
> >
> > I
On Sat, 20 Sep 2003, Hannu E K Nevalainen (garbage mail) wrote:
> > From: Corinna Vinschen
>
>
> > The above case is imho somewhat borderline. It defines Biz with
> > dllimport, but it's missing an `extern'. What I mean is, having two
> > extern declarations, one with and the second without dll
> From: Corinna Vinschen
> The above case is imho somewhat borderline. It defines Biz with
> dllimport, but it's missing an `extern'. What I mean is, having two
> extern declarations, one with and the second without dllimport. The
> second should not touch the already existing declaration. I
On Sat, Sep 20, 2003 at 07:32:04AM +1000, Danny Smith wrote:
> > why is then the information about the __declspec removed? Shouldn't
> > that information be kept? AFAIK, the "extern" storage class shouldn't
> > change any information already known about the variable in question.
> > It should com
> And.. Hmmm..
>
> I *think* auto import of data variables may be somewhat broken
> (and declared
> import of data variables too) if
>
> 1) The import library is stripped with --strip-unneeded
>and/or
> 2) The import is from another DLL (.exe -> .dll[func] -> .dll[data])
>
> (See msg dated 9/17
Re: getopt: ugly linker messages
From: Corinna Vinschen
To: cygwin at cygwin dot com
Date: Fri, 19 Sep 2003 17:34:09 +0200
Subject: Re: getopt: ugly linker messages
References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
<
>
> I'm willing to do this but I have the same reservations that I think
> you're expressing above, Chuck. Also, the auto-import of
> data variables
> is slower than a normal dllimport so I don't feel real
> comfortable about
> making this the default.
>
> I don't feel really strongly about th
At 11:18 AM 9/19/2003, Christopher Faylor you wrote:
>On Fri, Sep 19, 2003 at 09:49:25AM -0400, Charles Wilson wrote:
>>Corinna Vinschen wrote:
>>
>>>Since that auto-import is working fine for a long while now and since
>>>this sort of auto-import is normal for any other platform... isn't there
>>>
On Fri, Sep 19, 2003 at 11:18:03AM -0400, Christopher Faylor wrote:
> On Fri, Sep 19, 2003 at 09:49:25AM -0400, Charles Wilson wrote:
> >Perhaps a cygwin-special (e.g. doesn't go back to binutils CVS) patch?
> >In that case, it's a one-liner -- just change the default value of
> >link_info.pei386
On Fri, Sep 19, 2003 at 09:49:25AM -0400, Charles Wilson wrote:
>Corinna Vinschen wrote:
>
>>Since that auto-import is working fine for a long while now and since
>>this sort of auto-import is normal for any other platform... isn't there
>>a time we can get rid of that message?
>
>auto-import is no
Corinna Vinschen wrote:
Since that auto-import is working fine for a long while now and since
this sort of auto-import is normal for any other platform... isn't there
a time we can get rid of that message?
auto-import is not the default for all pei386 versions of binutils,
particularly mingw.
An
On Thu, Sep 18, 2003 at 11:48:00PM -0400, Charles Wilson wrote:
> >On Thu, Sep 18, 2003 at 12:53:22PM -0700, Bryan Higgins wrote:
> >>Info: resolving _opterr by linking to __imp__opterr (auto-import)
>
> In general, these 'resolving blah by linking to __imp_blah' messages can
> be suppressed by u
Christopher Faylor wrote:
On Thu, Sep 18, 2003 at 12:53:22PM -0700, Bryan Higgins wrote:
How can I suppress the linker messages
Info: resolving _opterr by linking to __imp__opterr (auto-import)
Info: resolving _optarg by linking to __imp__optarg (auto-import)
Info: resolving _optopt by linking to
Bryan Higgins wrote:
Christopher Faylor wrote:
You can use unistd.h if you want. If you knew this already why were you
asking the question?
From the gnu getopt(3) man page (mysteriously missing in cygwin):
#include
int getopt(int argc, char * const argv[],
co
Christopher Faylor wrote:
>You can use unistd.h if you want. If you knew this already why were you
>asking the question?
>From the gnu getopt(3) man page (mysteriously missing in cygwin):
#include
int getopt(int argc, char * const argv[],
const char *optstring)
On Thu, Sep 18, 2003 at 01:08:14PM -0700, Bryan Higgins wrote:
>On Thu, 18 Sep 2003 15:56:07 -0400, Christopher Faylor wrote:
>>On Thu, Sep 18, 2003 at 12:53:22PM -0700, Bryan Higgins wrote:
>>>How can I suppress the linker messages
>>>
>>>Info: resolving _opterr by linking to __imp__opterr (auto-i
On Thu, 18 Sep 2003 15:56:07 -0400, Christopher Faylor wrote:
>On Thu, Sep 18, 2003 at 12:53:22PM -0700, Bryan Higgins wrote:
>>How can I suppress the linker messages
>>
>>Info: resolving _opterr by linking to __imp__opterr (auto-import)
>>Info: resolving _optarg by linking to __imp__optarg (auto-
On Thu, Sep 18, 2003 at 12:53:22PM -0700, Bryan Higgins wrote:
>How can I suppress the linker messages
>
>Info: resolving _opterr by linking to __imp__opterr (auto-import)
>Info: resolving _optarg by linking to __imp__optarg (auto-import)
>Info: resolving _optopt by linking to __imp__optopt (auto-i
How can I suppress the linker messages
Info: resolving _opterr by linking to __imp__opterr (auto-import)
Info: resolving _optarg by linking to __imp__optarg (auto-import)
Info: resolving _optopt by linking to __imp__optopt (auto-import)
Info: resolving _optind by linking to __imp__optind (auto-imp
26 matches
Mail list logo
