From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin-apps@cygwin.com
Subject: Re: [ITA] wget
Date: Sat, 14 Nov 2020 15:15:04 -0700 [thread overview]
Message-ID: <648ab3eb-4f71-b3a2-b90b-b0713d82ad07@SystematicSw.ab.ca> (raw)
In-Reply-To: <87d00garud.fsf@Rainer.invalid>
On 2020-11-14 08:19, Achim Gratz wrote:
> Brian Inglis writes:
>>> Yes, my time for cygwin has greatly diminished, so you are welcome to
>>> take over wget.
>>
>> Thanks Eric, good to know you're keeping so busy, expected under the circumstances!
>>
>> Not a great effort as there should be no to few more wget releases.
>
> Your latest wget release is configured differently for 32bit and 64bit,
> most likely due to missing dependencies / development packages. Since
> the BUILD_REQUIRES are completely missing it doesn't build at all on the
> CI.
I rebuilt with the original cygport updated minimally.
This is one of those packages that advertises minimal dependencies and documents
none AFAICT.
Is there a way of determining desirable, useful, or additional dependencies?
I found cygcares-2.dll was missing(!) from cygwin 32, so reinstalled it, and
libnpth-devel was not installed in either arch, so installed those, added all
the lib...-devel and tools dependencies to BUILD_REQUIRES, and all the relevant
configure --with/out-... options, so now both arches build with only minor
--version output differences.
Is it sufficiently worth while to resolve with a release -2 package, as there
may be no further upstream releases of the package, other than replacement by
wget2?
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
next prev parent reply other threads:[~2020-11-14 22:15 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-08 20:05 [ITP] wget2 - modern fast parallel file and recursive website downloader Brian Inglis
2020-07-08 20:28 ` Brian Inglis
2020-07-09 18:27 ` Marco Atzeri
2020-07-09 18:50 ` Yaakov Selkowitz
2020-07-10 1:38 ` Brian Inglis
2020-07-10 5:27 ` Marco Atzeri
2020-10-30 21:30 ` Brian Inglis
2020-10-30 21:34 ` Eric Blake
2020-10-30 21:57 ` [ITA] wget Brian Inglis
2020-10-31 12:50 ` Marco Atzeri
2020-11-14 15:19 ` Achim Gratz
2020-11-14 22:15 ` Brian Inglis [this message]
2020-11-15 7:36 ` ASSI
2020-11-15 17:32 ` Brian Inglis
2020-11-16 17:23 ` Achim Gratz
2020-11-16 21:35 ` Brian Inglis
2020-11-17 19:10 ` Achim Gratz
2020-11-17 23:23 ` Brian Inglis
2020-11-18 14:23 ` ASSI
2020-11-10 5:29 ` [ITP] wget2 - please review if anyone has time Brian Inglis
2020-11-24 21:06 ` [ITP] wget2 Brian Inglis
2020-11-27 17:57 ` Hamish McIntyre-Bhatty
2020-11-27 18:28 ` Brian Inglis
2020-11-30 14:51 ` Hamish McIntyre-Bhatty
2020-11-30 18:29 ` Achim Gratz
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=648ab3eb-4f71-b3a2-b90b-b0713d82ad07@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).