From: Austin Morton <austinpmorton@gmail.com>
To: "N. Ohkawa" <n.ohkawa@gmail.com>
Cc: Dan Wilder <Dan.Wilder@watchguard.com>,
crossgcc maillist <crossgcc@sourceware.org>
Subject: Re: Is crosstool-ng.org down ?
Date: Sat, 16 Dec 2017 00:13:00 -0000 [thread overview]
Message-ID: <CAPWKHJQd7Dxx1P8-B_W2ji-xdP1fYVDWnKxTF_K1auYNSabwgA@mail.gmail.com> (raw)
In-Reply-To: <CA+vbTX8eyEWiKNCLJdW+RKuymP8WYmZw-h-E5XEbiEJRwqXUtw@mail.gmail.com>
Assuming you have autoconf et all installed, you can simply run ./bootstrap
from the unpacked GitHub release directory.
On Dec 15, 2017 7:11 PM, "N. Ohkawa" <n.ohkawa@gmail.com> wrote:
> I know that and already try it.
>
>
> github release package is different from release package at
> crosstool-ng.org.
> github one doesn't include autoconfigured configure script.
>
>
> 2017-12-16 9:06 GMT+09:00 Austin Morton <austinpmorton@gmail.com>:
>
>> In the meantime, you can get the releases from GitHub.
>>
>> https://github.com/crosstool-ng/crosstool-ng/releases/tag/cr
>> osstool-ng-1.23.0
>>
>>
>> On Dec 15, 2017 7:00 PM, "N. Ohkawa" <n.ohkawa@gmail.com> wrote:
>>
>>> Yes I try it.
>>>
>>> Download link at http://crosstool-ng.github.io/download/ is
>>> http://crosstool-ng.org/download/crosstool-ng/crosstool-ng-1.23.0.tar.xz
>>>
>>> crosstool-ng.org don't response anything.
>>>
>>> 2017-12-16 8:55 GMT+09:00 Dan Wilder <Dan.Wilder@watchguard.com>:
>>>
>>> > Try crosstool-ng.github.io
>>> >
>>> >
>>> > --
>>> > Dan Wilder
>>> > ------------------------------
>>> > *From:* crossgcc-owner@sourceware.org <crossgcc-owner@sourceware.org>
>>> on
>>> > behalf of N. Ohkawa <n.ohkawa@gmail.com>
>>> > *Sent:* Friday, December 15, 2017 3:50:46 PM
>>> > *To:* crossgcc@sourceware.org
>>> > *Subject:* Is crosstool-ng.org down ?
>>> >
>>> > Hi all.
>>> >
>>> >
>>> > I can't download packages from crosstool-ng.org.
>>> > Is server down ?
>>> >
>>> > Regards,
>>> >
>>>
>>
>
next prev parent reply other threads:[~2017-12-16 0:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-15 23:50 N. Ohkawa
2017-12-15 23:55 ` Dan Wilder
2017-12-16 0:00 ` N. Ohkawa
2017-12-16 0:03 ` Dan Wilder
2017-12-16 0:06 ` Austin Morton
2017-12-16 0:11 ` N. Ohkawa
2017-12-16 0:13 ` Austin Morton [this message]
2017-12-16 0:29 ` N. Ohkawa
2017-12-16 8:48 ` Bryan Hundven
2017-12-16 12:27 ` Geert Stappers
2017-12-16 22:54 ` Bryan Hundven
2017-12-16 23:43 ` Josh Branning
2017-12-17 9:04 ` N. Ohkawa
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=CAPWKHJQd7Dxx1P8-B_W2ji-xdP1fYVDWnKxTF_K1auYNSabwgA@mail.gmail.com \
--to=austinpmorton@gmail.com \
--cc=Dan.Wilder@watchguard.com \
--cc=crossgcc@sourceware.org \
--cc=n.ohkawa@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).