From: Marco Atzeri <marco.atzeri@gmail.com>
To: "Alois Schlögl" <alois.schloegl@gmail.com>
Cc: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: newcomer issues when packaging biosig,stimfit, etc.
Date: Wed, 12 Jan 2022 06:47:25 +0100 [thread overview]
Message-ID: <8e1cdac3-b217-faa6-d0a0-8f8a61c6d2a3@gmail.com> (raw)
In-Reply-To: <a3f8e657-1e1d-c582-2a07-806c6c03be02@gmail.com>
On 11.01.2022 12:33, Alois Schlögl wrote:
>
> Dear Marco,
>
>
> Yesterday, I've tried to subscribe to the cygwin-apps mailinglist, but
> so far I did not get any confirmation email. When trying to send to the
> mailinglist, it fails with " Your message has been rejected, probably
> because you are not ...".
> Do you know how long it typically takes until the mailing list
> subscription is confirmed ?
sorry I don't.
I am subscripted by so long.
Jon,
could you check ?
> In the meantime, please find below the status for the libb64 and biosig
> packages.
> Thanks that was helpful. Attached is an updated version for biosig and
> libb64.
>
> cygport libb64.cygport all
> cygport biosig.cygport all
>
> runs now w/o error. How can I test whether result can be installed and
> used ?
One major problem.
Never build in the source directory, the final src.patch
must fit with you desired patch.
So only what you patched should come out.
For this package that does not respect the build in a
different directory than source, you shoud start
with something like:
src_compile() {
cd ${S}
lndirs
cd ${B}
cygautoreconf
cygconf
cygmake
}
unfortunately I have no time to dig further
short term
Regards
Marco
next prev parent reply other threads:[~2022-01-12 5:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <99eff890-3d7f-7fa9-1f42-d8d611b92ded@gmail.com>
2022-01-08 17:41 ` Marco Atzeri
2022-01-08 19:15 ` Marco Atzeri
2022-01-08 19:24 ` Marco Atzeri
[not found] ` <a3f8e657-1e1d-c582-2a07-806c6c03be02@gmail.com>
2022-01-12 5:47 ` Marco Atzeri [this message]
2022-01-12 6:16 ` Brian Inglis
2022-01-12 22:59 ` [ITP] biosig [was: Re: newcomer issues when packaging biosig, stimfit, etc.] Alois Schlögl
2022-01-14 10:09 ` Marco Atzeri
2022-01-14 21:48 ` Alois Schlögl
2022-01-15 18:01 ` Marco Atzeri
2022-01-15 20:44 ` Achim Gratz
2022-01-17 21:44 ` Alois Schlögl
2022-01-18 5:32 ` Brian Inglis
2022-01-18 21:50 ` Alois Schlögl
2022-01-18 22:56 ` Brian Inglis
2022-01-19 3:51 ` Brian Inglis
2022-01-20 20:48 ` Alois Schlögl
2022-01-21 12:53 ` Jon Turney
2022-01-16 22:13 ` Alois Schlögl
2022-01-22 17:52 ` Marco Atzeri
2022-01-25 23:50 ` Alois Schlögl
2022-01-26 4:52 ` Marco Atzeri
2022-01-26 22:47 ` Marco Atzeri
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=8e1cdac3-b217-faa6-d0a0-8f8a61c6d2a3@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=alois.schloegl@gmail.com \
--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).