On Aug 3 10:02, Alexey Sokolov wrote:
03.08.2015 08:59, Corinna Vinschen пишет:
On Jul 30 23:34, Alexey Sokolov wrote:
- 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.
I thought if the package
On Jul 30 23:34, Alexey Sokolov wrote:
- 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.
I thought if the package exists in popular distros, no GTG needed?
Uhm, no. The *votes* are not required,
03.08.2015 08:59, Corinna Vinschen пишет:
On Jul 30 23:34, Alexey Sokolov wrote:
- 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.
I thought if the package exists in popular distros, no GTG needed?
Uhm,
- 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.
I thought if the package exists in popular distros, no GTG needed?
Uhm, no. The *votes* are not required, the GTG is.
Oops. Sorry then!
Hi,
Is
If you add ACLOCAL_FLAGS=-I m4 to znc.cygport, does it fix for you?
Yes. So why didn't your build require that?
I have a hypothesis, but can't prove it without digging autotools sources.
My guess is that you have AX_PTHREAD installed in /usr/share/aclocal (or
in some other directory which
22.07.2015 09:07, Corinna Vinschen пишет:
On Jul 22 00:32, Alexey Sokolov wrote:
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
23.07.2015 06:23, Achim Gratz пишет:
So, for protection against possible broken autoreconfs I'll add such
src_compile to znc.cygport.
As David said, please try to make autoreconf work or at least try to
understand why it doesn't. If you could add a cygcheck to the build
script we might be
On 7/22/2015 8:57 PM, Alexey Sokolov wrote:
23.07.2015 00:03, David Stacey :
cygport ./znc.cygport prep compile
Nothing out of the ordinary there. This gives the following error:
configure.ac:255: Something is trying to use the C compiler. Since
this is a C++ project, this should
23.07.2015 14:24, Ken Brown пишет:
On 7/22/2015 8:57 PM, Alexey Sokolov wrote:
23.07.2015 00:03, David Stacey :
cygport ./znc.cygport prep compile
Nothing out of the ordinary there. This gives the following error:
configure.ac:255: Something is trying to use the C compiler. Since
23.07.2015 21:49, Alexey Sokolov пишет:
23.07.2015 14:24, Ken Brown пишет:
On 7/22/2015 8:57 PM, Alexey Sokolov wrote:
23.07.2015 00:03, David Stacey :
cygport ./znc.cygport prep compile
Nothing out of the ordinary there. This gives the following error:
configure.ac:255:
On 7/23/2015 5:04 PM, Alexey Sokolov wrote:
23.07.2015 21:49, Alexey Sokolov пишет:
23.07.2015 14:24, Ken Brown пишет:
On 7/22/2015 8:57 PM, Alexey Sokolov wrote:
23.07.2015 00:03, David Stacey :
cygport ./znc.cygport prep compile
Nothing out of the ordinary there. This gives the
On Jul 22 00:32, Alexey Sokolov wrote:
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
Alexey Sokolov writes:
Hm, I'm not sure why autoreconf would do this (works for me though), but
autoreconf is not required for ZNC anyway, as release tarballs already
have ./configure script.
It's generally frowned upon to use this from the tarball if you can't
re-produce it at the build
22.07.2015 09:07, Corinna Vinschen:
On Jul 22 00:32, Alexey Sokolov wrote:
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
On 23/07/15 00:03, David Stacey wrote:
That's because there's no 'libznc-1.6.dll.a' to link against. You need
to add the following to your link command when producing the shared DLL:
-Wl,--out-implib=libznc-1.6.dll.a
Again, I'll leave it to you to get this into the Makefile in a nice
23.07.2015 00:03, David Stacey :
On 22/07/2015 00:53, Alexey Sokolov wrote:
David, how did you try to build it? What was the exact error message?
What do you change in Makefile.in to get it working?
Attempting to compile znc-1.6.0-3 with cygport under Cygwin x86. It's
worth saying that my
On 22/07/2015 00:53, Alexey Sokolov wrote:
David, how did you try to build it? What was the exact error message?
What do you change in Makefile.in to get it working?
Attempting to compile znc-1.6.0-3 with cygport under Cygwin x86. It's
worth saying that my Cygwin installation is about a month
21.07.2015 08:12, Corinna Vinschen пишет:
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.
Git master which will eventually become 1.7.0 already has
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
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
22.07.2015 00:32, Alexey Sokolov пишет:
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
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
On Jul 19 20:54, Alexey Sokolov wrote:
19.07.2015 20:10, Achim Gratz пишет:
Alexey Sokolov writes:
Is 1 some special number which should be used?
Just some number that gets bumped whenever the ABI changes
(i.e. applications that link against the library would need to be
recompiled).
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.
No, hang on. The reason for the version-independent number is to allow
keeping the number the same for multiple versions of the package, and
only bump it when an ABI breakage
You ahould ask Yaakov, but I seem to remember that the preferred way to
name new libraries is now without the hyphen.
Hm, ok...
Yaakov, what's the plan?
Dunno about Yaakov, but what counts in the first place is to keep track
of the ABI change and only bump the ABI version attached to the
For some reason the mailing list swallows my messages, so I'm trying to
remove cyrillic letters for wrote...
19.07.2015 00:07, Alexey Sokolov :
18.07.2015 22:05, Alexey Sokolov :
I've put files in the required directory structure to
http://people.znc.in/~darthgandalf/znc/znc-cygwin/
Hi Alexey,
On Jul 19 09:24, Alexey Sokolov wrote:
For some reason the mailing list swallows my messages, so I'm trying to
remove cyrillic letters for wrote...
19.07.2015 00:07, Alexey Sokolov :
18.07.2015 22:05, Alexey Sokolov :
I've put files in the required directory structure to
Hi Corinna,
19.07.2015 11:03, Corinna Vinschen :
I think libznc.dll should be called libzncX.dll or cygzncX.dll, with X
being a version number. If there will ever be backward-incompatible
changes in the DLL, the version number should be bumped. Also, is there
a native Windows version of
Alexey Sokolov writes:
Is 1 some special number which should be used?
Just some number that gets bumped whenever the ABI changes
(i.e. applications that link against the library would need to be
recompiled).
ZNC 1.6.0 is supposed to be ABI-compatible with ZNC 1.6.1 (when it will
be released),
On 7/19/2015 9:10 PM, Achim Gratz wrote:
Alexey Sokolov writes:
Is 1 some special number which should be used?
Just some number that gets bumped whenever the ABI changes
(i.e. applications that link against the library would need to be
recompiled).
ZNC 1.6.0 is supposed to be
+mailing list back, sorry...
19.07.2015 17:42, Achim Gratz :
Alexey Sokolov writes:
Thanks, renamed it to cygznc-1.6.dll.
You seem to have misunderstood. The name of the DLL should be something
like
cygznc1.dll
where the number indicates the API version.
Is 1 some special number which
19.07.2015 20:10, Achim Gratz пишет:
Alexey Sokolov writes:
Is 1 some special number which should be used?
Just some number that gets bumped whenever the ABI changes
(i.e. applications that link against the library would need to be
recompiled).
Well, in that case 1.6 works fine. When
Alexey Sokolov writes:
Thanks, renamed it to cygznc-1.6.dll.
You seem to have misunderstood. The name of the DLL should be something
like
cygznc1.dll
where the number indicates the API version.
Regards,
Achim.
--
+[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+
Samples
Marco Atzeri writes:
looking at fedora package,
it seems the ABI version in not used at all in ZNC
shared libs
These are modules, there is no shared ZNC library on these systems at
all.
so a cygznc.dll is in line with Fedora
I don't see a file that would correspond to it.
Regards,
Achim.
Hi!
I want to package ZNC.
Package in distros:
https://packages.gentoo.org/package/net-irc/znc
https://packages.debian.org/search?keywords=znc
http://packages.ubuntu.com/search?keywords=znc
https://admin.fedoraproject.org/pkgdb/package/znc/
Also I have several questions:
1) cygport chose to make
35 matches
Mail list logo
