From: David Stacey <drstacey@tiscali.co.uk>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] znc 1.6.0
Date: Tue, 21 Jul 2015 23:25:00 -0000 [thread overview]
Message-ID: <55AED4D4.1040403@tiscali.co.uk> (raw)
In-Reply-To: <20150721071221.GZ3864@calimero.vinschen.de>
On 21/07/2015 08:12, Corinna Vinschen wrote:
> On Jul 20 19:58, Alexey Sokolov wrote:
>>>> Well, in that case 1.6 works fine. When 1.7.0 will be released, the
>>>> filename will be changed to cygznc-1.7.dll.
> Assuming 1.7 does not break the ABI. The problem here is that modules
> built for 1.6 won't run on 1.7, even if the ABI hasn't changed, because
> these modules won't find the DLL anymore. In this case your update
> to a newer package would break self-built modules for no good reason.
I've had a busy day and I'm a little tired, so I'm probably about to
make a fool of myself on a public mailing list. Never mind :-) Three
points on the znc package:
- Unless I've missed something, all this talk of DLL naming is a
little academic at the moment, as there is no 'dll.a' file to actually
link against.
- Has anyone tried building this in Cygwin? I tried rebuilding the
1.6.0-2 release, and couldn't get it to compile without hacking the
'Makefile.in' files. Even if you generate a 'dll.a', the linker
arguments are in the wrong order. This doesn't matter in Linux, but it
/does/ matter in Cygwin. Does this only build if cross-compiled out of
Fedora?
- Forgive me for being pedantic, but who gave this a GTG? I couldn't
find one on this thread, and yet the package is up on the mirrors.
Let's hope I've missed something really obvious - apologies for any
late-night stupidity.
Dave.
next prev parent reply other threads:[~2015-07-21 23:25 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-18 15:48 Alexey Sokolov
[not found] ` <55AABF89.7030306@asokolov.org>
[not found] ` <55AADC2C.1070802@asokolov.org>
2015-07-19 8:24 ` Alexey Sokolov
2015-07-19 10:03 ` Corinna Vinschen
2015-07-19 13:24 ` Alexey Sokolov
2015-07-19 16:42 ` Achim Gratz
[not found] ` <55ABEC90.3040106@asokolov.org>
2015-07-19 18:30 ` Alexey Sokolov
2015-07-19 19:11 ` Achim Gratz
2015-07-19 19:30 ` Marco Atzeri
2015-07-19 19:36 ` Achim Gratz
2015-07-19 19:54 ` Alexey Sokolov
2015-07-20 7:44 ` Corinna Vinschen
2015-07-20 18:58 ` Alexey Sokolov
2015-07-20 20:46 ` Alexey Sokolov
2015-07-21 7:12 ` Corinna Vinschen
2015-07-21 20:37 ` Alexey Sokolov
2015-07-21 23:25 ` David Stacey [this message]
2015-07-21 23:32 ` Alexey Sokolov
2015-07-21 23:53 ` Alexey Sokolov
2015-07-22 23:03 ` David Stacey
2015-07-22 23:29 ` David Stacey
2015-07-23 0:58 ` Alexey Sokolov
2015-07-23 5:23 ` Achim Gratz
2015-07-23 20:50 ` Alexey Sokolov
2015-07-23 13:24 ` Ken Brown
2015-07-23 20:50 ` Alexey Sokolov
2015-07-23 21:04 ` Alexey Sokolov
2015-07-23 21:28 ` Ken Brown
2015-07-24 6:42 ` Alexey Sokolov
2015-07-22 8:07 ` Corinna Vinschen
2015-07-22 21:40 ` Alexey Sokolov
2015-07-30 22:34 ` Alexey Sokolov
2015-08-03 7:59 ` Corinna Vinschen
2015-08-03 9:02 ` Alexey Sokolov
2015-08-03 9:20 ` Corinna Vinschen
2015-07-24 19:14 ` Alexey Sokolov
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=55AED4D4.1040403@tiscali.co.uk \
--to=drstacey@tiscali.co.uk \
--cc=cygwin-apps@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).