This is the mail archive of the
cygwin-apps
mailing list for the Cygwin project.
Re: [ADOPT] iperf 2.0.8
- From: Marco Atzeri <marco dot atzeri at gmail dot com>
- To: Joel Johnson <mrjoel at lixil dot net>
- Cc: cygwin-apps at cygwin dot com
- Date: Wed, 15 Jul 2015 07:13:16 +0200
- Subject: Re: [ADOPT] iperf 2.0.8
- Authentication-results: sourceware.org; auth=none
- References: <5518580c020d188244da3f0626fe05b8 at lixil dot net> <c1482789b2b3a4b3435f4ef04827b0ce at lixil dot net> <55A4F3BC dot 4070309 at gmail dot com> <c0b1ce9761c56d6390d5d505671c6d5a at lixil dot net>
On 7/14/2015 7:17 PM, Joel Johnson wrote:
On 2015-07-14 05:34, Marco Atzeri wrote:
build fine. Have you tested it?
on 64 bit I see
$ iperf -s -D
$ 1 [main] iperf 5396 fork: child -1 - forked process 9264 died
unexpectedly, retry 0, exit code 0xC0000005, errno 11
error
and 32bit strace...
--- Process 8552, exception 80000001 at 73006661
I did test both the 32 and 64 bit version, but not with the -D flag,
just interactively. Thanks for pointing out that gap. I only had a
chance to look briefly at the failure, but it occurs on 2.0.5 32 and
64-bit builds, as well as the existing 2.0.4 32-bit package. Since it's
strictly not a regression, I'd push for it not holding up the update if
everything else work, but is still be a nice to have that I'll look at.
Ok,
fair enough, just highlight the problem in the announcement.
You are the new maintainer
Congratulation.
please follow:
https://sourceware.org/cygwin-apps/package-upload.html
As another packaging question, I get that cygport is a build helper not
package management, but is there an easy way to install a resulting
binary package on a local system that ties in with the setup.exe
packaging tracking? I'd like to be able to actually test packages in
deployed state with and without the debug information present, and be
able to subsequently remove it as well, for which tar xfJ doesn't do
such a hot job.
build a local site and use genini to build the setup.ini
https://sourceware.org/viewvc/cygwin-apps/genini/
For example I use a structure like
http%3a%2f%2fmatzeri.altervista.org%2f/x86/setup.bz2
http%3a%2f%2fmatzeri.altervista.org%2f/x86/setup.ini
http%3a%2f%2fmatzeri.altervista.org%2f/x86/iperf/iperf-2.0.5-1-src.tar.xz
http%3a%2f%2fmatzeri.altervista.org%2f/x86/iperf/iperf-2.0.5-1.tar.xz
http%3a%2f%2fmatzeri.altervista.org%2f/x86/iperf/iperf-debuginfo/iperf-debuginfo-2.0.5-1.tar.xz
http%3a%2f%2fmatzeri.altervista.org%2f/x86/iperf/iperf-debuginfo/setup.hint
http%3a%2f%2fmatzeri.altervista.org%2f/x86/iperf/setup.hint
http%3a%2f%2fmatzeri.altervista.org%2f/x86_64/setup.bz2
http%3a%2f%2fmatzeri.altervista.org%2f/x86_64/setup.ini
http%3a%2f%2fmatzeri.altervista.org%2f/x86_64/iperf/iperf-2.0.5-1-src.tar.xz
http%3a%2f%2fmatzeri.altervista.org%2f/x86_64/iperf/iperf-2.0.5-1.tar.xz
http%3a%2f%2fmatzeri.altervista.org%2f/x86_64/iperf/iperf-debuginfo/iperf-debuginfo-2.0.5-1.tar.xz
http%3a%2f%2fmatzeri.altervista.org%2f/x86_64/iperf/iperf-debuginfo/setup.hint
http%3a%2f%2fmatzeri.altervista.org%2f/x86_64/iperf/setup.hint
and a script like
-----------------------------------------
rm x86/setup.ini x86_64/setup.ini
genini --recursive x86_64 > x86_64/setup.ini
bzip2 -k -c x86_64/setup.ini > x86_64/setup.bz2
genini --recursive x86 > x86/setup.ini
bzip2 -k -c x86/setup.ini > x86/setup.bz2
-----------------------------------------
see "setup-x86.exe --help"
how to install locally from your local site.
Joel
Regards
Marco