From: Roy Osherove <roy@osherove.com>
To: Joseph Bisch <joseph.bisch@gmail.com>
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Build: win64: Package 'mingw-w64-dev' has no installation candidate
Date: Mon, 28 Sep 2015 23:09:36 -0700 [thread overview]
Message-ID: <CAAMhxnxWckT-OAHJ=bQ=H0UxRehH0fHKV4T2tq2gNgAMzBUuKw@mail.gmail.com> (raw)
In-Reply-To: <CAO+PtjsaRf2Ur7nj0EwMG7maMfTGe0KG60qLGOnkTyiMwv_0tg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1058 bytes --]
Ah, I didn't notice, thanks!
On Mon, Sep 28, 2015 at 7:23 PM, Joseph Bisch <joseph.bisch@gmail.com>
wrote:
> Hi Roy,
>
> It looks like your TeamCity setup is using Ubuntu Trusty to perform
> the build. Travis CI is using Ubuntu Precise instead[0]. The
> mingw-w64-dev package is only available in Precise[1]. It looks like
> that package was split into mingw-w64-x86-64-dev and
> mingw-w64-i686-dev, so those are what have to be used with Ubuntu
> Trusty.
>
> [0] - http://docs.travis-ci.com/user/ci-environment/
> [1] - http://packages.ubuntu.com/precise/mingw-w64-dev
> [2] - http://packages.ubuntu.com/trusty/mingw-w64-x86-64-dev
> [3] - http://packages.ubuntu.com/trusty/mingw-w64-i686-dev
>
> Cheers,
> Joseph
>
--
Thanks,
Roy Osherove
- *@RoyOsherove* <https://twitter.com/RoyOsherove>
- Read my new book *Notes to a Software Team Leader
<http://TeamLeadSkills.com>*
- Or *my new course* about Beautiful Builds <http://courses.osherove.com>
and Continuous Delivery
- +1-201-256-5575
- Timezone: Eastern Standard Time (New York)
[-- Attachment #2: Type: text/html, Size: 2125 bytes --]
next parent reply other threads:[~2015-09-29 6:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAO+PtjsaRf2Ur7nj0EwMG7maMfTGe0KG60qLGOnkTyiMwv_0tg@mail.gmail.com>
2015-09-29 6:09 ` Roy Osherove [this message]
2015-09-27 8:37 [bitcoin-dev] Build: win64: Package 'mingw-w64-dev' has no installation candidate Roy Osherove
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='CAAMhxnxWckT-OAHJ=bQ=H0UxRehH0fHKV4T2tq2gNgAMzBUuKw@mail.gmail.com' \
--to=roy@osherove.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=joseph.bisch@gmail.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