On 29/03/2011 02:24, Daniel Jensen wrote:
Since Dave Korn was wondering how many people this would be bothering,
I'm just chiming in to say I was bitten by this too (since I both run
cygwin setup less often than others and use octave less often than
others, and since I'm not subscribed to the
Since Dave Korn was wondering how many people this would be bothering,
I'm just chiming in to say I was bitten by this too (since I both run
cygwin setup less often than others and use octave less often than
others, and since I'm not subscribed to the list, I'm late to the
party). It was kind
On 23/03/2011 15:02, marco atzeri wrote:
Dave,
the new cyggfortran-3.dll seems to provide less export than before.
This breaks octave.
Dependency walker check on octave highlight 3 functions in red
clogf, cexpf, csqrtf
Is the new fortran library broken, or should I release a new octave
On 23/03/2011 15:53, Dave Korn wrote:
On 23/03/2011 15:02, marco atzeri wrote:
Dave,
the new cyggfortran-3.dll seems to provide less export than before.
This breaks octave.
Dependency walker check on octave highlight 3 functions in red
clogf, cexpf, csqrtf
Is the new fortran library
On Wed, Mar 23, 2011 at 5:11 PM, Dave Korn wrote:
On 23/03/2011 15:53, Dave Korn wrote:
On 23/03/2011 15:02, marco atzeri wrote:
Dave,
the new cyggfortran-3.dll seems to provide less export than before.
This breaks octave.
Dependency walker check on octave highlight 3 functions in red
On 23/03/2011 16:19, marco atzeri wrote:
May be as they are now available from cygwin-1.7.8 ?
Yes indeed (and this is why I didn't see any errors during the compiler
testsuite), I just had a quick look at the libgfortran autoconfigury, it
provides replacements for those functions when the
On 3/23/2011 12:19 PM, marco atzeri wrote:
May be as they are now available from cygwin-1.7.8 ?
Oh, good point. Is there a way to add export forwarding to the new
cygfortran-3.dll (but not the implib)?
That way, the old apps will still get (think they are getting) the
functions from the
On Wed, Mar 23, 2011 at 5:27 PM, Dave Korn wrote:
On 23/03/2011 16:19, marco atzeri wrote:
May be as they are now available from cygwin-1.7.8 ?
Yes indeed (and this is why I didn't see any errors during the compiler
testsuite), I just had a quick look at the libgfortran autoconfigury, it
On Mar 23 16:27, Dave Korn wrote:
On 23/03/2011 16:19, marco atzeri wrote:
May be as they are now available from cygwin-1.7.8 ?
Yes indeed (and this is why I didn't see any errors during the compiler
testsuite), I just had a quick look at the libgfortran autoconfigury, it
provides
On 23/03/2011 16:36, Corinna Vinschen wrote:
Is there a way to add symbol forwarding in GCC? There's some method of
forwarding symbol references to other DLLs and it's used in Windows
itself to forward symbol references to other DLLs.
Yes, was using that just the other day myself, to
On 23/03/2011 16:35, Charles Wilson wrote:
I think it would just take a few statements in a .def file like
carg = CYGWIN1.carg
cargf = CYGWIN1.cargf
ccos = CYGWIN1.ccos
but I'm not sure...
Yes, that's basically it (or equivalent in a .directve section), but,
indeed, as you
marco atzeri wrote:
Sent: Wednesday, March 23, 2011 12:36 PM
Subject: Re: cyggfortran-3.dll broken ?
[snip...]
So I caused myself the problem as I added all those functions to
cygwin
But they were just in time to save me having to abandon my primary
application on Cygwin. Thank you
On 3/23/2011 12:57 PM, Dave Korn wrote:
On 23/03/2011 16:35, Charles Wilson wrote:
And if you DO it this way, I'm pretty sure ld will go ahead and
create import entries in the .dll.a for them.
Yes, that's what we'd want to happen isn't it? The import stub imports the
symbol from
On 23/03/2011 17:31, Charles Wilson wrote:
Err...no, I don't think so. Symbol forwarding is actually implemented
as part of the PE-I386 spec, so it resides in the forwardING dll itself,
not the import library, and is handled at runtime by the windows loader:
Yes yes yes, you're jumping too
On Wed, Mar 23, 2011 at 5:36 PM, marco atzeri wrote:
On Wed, Mar 23, 2011 at 5:27 PM, Dave Korn wrote:
On 23/03/2011 16:19, marco atzeri wrote:
Sorry, looks like you'll need to respin after all.
cheers,
DaveK
So I caused myself the problem as I added all those functions to
On 3/23/2011 1:49 PM, Dave Korn wrote:
On 23/03/2011 17:31, Charles Wilson wrote:
Err...no, I don't think so. Symbol forwarding is actually implemented
as part of the PE-I386 spec, so it resides in the forwardING dll itself,
not the import library, and is handled at runtime by the windows
On 23/03/2011 19:17, Charles Wilson wrote:
On 3/23/2011 1:49 PM, Dave Korn wrote:
Hmm, I should probably do this. And send it upstream too.
Well, yeah (but does upstream want to explicitly require cygwin-1.7.8 or
better? or would you conditionalize it on a configure test:
The latter,
On Wed, Mar 23, 2011 at 8:40 PM, Dave Korn wrote:
On 23/03/2011 19:17, Charles Wilson wrote:
On 3/23/2011 1:49 PM, Dave Korn wrote:
Hmm, I should probably do this. And send it upstream too.
Well, yeah (but does upstream want to explicitly require cygwin-1.7.8 or
better? or would you
18 matches
Mail list logo
