From: Maurice Bos <m-ou.se@m-ou.se>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] cloudabi-toolchain, cloudab-binutils-*
Date: Wed, 30 Mar 2016 12:52:00 -0000 [thread overview]
Message-ID: <CABbCQwuoNJ2bXKM7gc9u_WCEWBm6BghjhmSbC5_d7xRgXeatHg@mail.gmail.com> (raw)
In-Reply-To: <4089EBBF-8605-47CA-984B-527845F7CD27@etr-usa.com>
2016-03-29 21:53 GMT+02:00 Warren Young <wyml@etr-usa.com>:
> On Mar 29, 2016, at 12:35 PM, Maurice Bos <m-ou.se@m-ou.se> wrote:
>>
>> The setup.hint files:
>>
>> category: Devel
>> requires: clang cloudabi-binutils-aarch64 cloudabi-binutils-x86_64
>> sdesc: "Toolchain targetting CloudABI"
>> ldesc: "Toolchain targetting CloudABI”
>
> Why does this package depend on both architecture-specific packages? What if I only want to develop for x86_64, for example?
This is also how these packages are packaged for FreeBSD and Arch
Linux. But I can split them, I don't care much.
>> category: Devel
>> requires: cygwin
>> sdesc: "Binutils targetting aarch64 CloudABI"
>> ldesc: "Binutils targetting aarch64 CloudABI”
>
> I believe the need for an explicit dependency on cygwin was removed many years ago. A blank “requires” line is perfectly legal.
>
> (If I’m right about this, I believe Mr. Bos got this idea from the current setup.html page which still shows such examples.)
I used cygport to generate the packages. It did this automatically, it seems.
>
>> sdesc: "Binutils targetting x86_64 CloudABI”
>
> That’s an obsolete spelling of “targeting”.
Thanks, updated.
next prev parent reply other threads:[~2016-03-29 20:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-29 19:53 Maurice Bos
2016-03-29 20:01 ` Maurice Bos
2016-03-29 20:28 ` Warren Young
2016-03-30 12:52 ` Maurice Bos [this message]
2016-03-30 13:26 ` Jon Turney
2016-04-21 12:12 ` Maurice Bos
2016-04-21 16:30 ` Tony Kelman
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=CABbCQwuoNJ2bXKM7gc9u_WCEWBm6BghjhmSbC5_d7xRgXeatHg@mail.gmail.com \
--to=m-ou.se@m-ou.se \
--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).