From: Bryce Schober <bryce.schober@gmail.com>
To: crossgcc@sourceware.org
Subject: Re: Why not download into CT_LOCAL_TARBALLS_DIR?
Date: Mon, 16 Dec 2013 23:59:00 -0000 [thread overview]
Message-ID: <CAJpxd05W0bUpYmdLgTPR1gq6m8e0jgjku4GCL0wKBndpxAAoVg@mail.gmail.com> (raw)
In-Reply-To: <CAJpxd07ND0CLuHG=pHi+995Z=e_RbgZxwzppLw91PgBkpOigqA@mail.gmail.com>
Argh. Ignore this thread. My bug-submit reflex is tuned a bit too
tightly. Apparently I'd never built with quite the same config for
download location, and overreacted, not being familiar with the
download-to-working->copy-to-saved behavior...
My apologies.
<>< <>< <><
Bryce Schober
On Mon, Dec 16, 2013 at 3:37 PM, Bryce Schober <bryce.schober@gmail.com> wrote:
> Not having read the manual beforehand, I naively assumed that
> crosstool-ng would download saved tarballs into CT_LOCAL_TARBALLS_DIR,
> when specified.
>
> Is there a reason that it doesn't, other than nobody has yet submitted
> a patch for it to do so?
>
> This gets in the way of sharing tarballs (like the linux kernel) with
> other tools that need them (like buildroot).
> <>< <>< <><
> Bryce Schober
--
For unsubscribe information see http://sourceware.org/lists.html#faq
prev parent reply other threads:[~2013-12-16 23:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-16 23:37 Bryce Schober
2013-12-16 23:59 ` Bryce Schober [this message]
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=CAJpxd05W0bUpYmdLgTPR1gq6m8e0jgjku4GCL0wKBndpxAAoVg@mail.gmail.com \
--to=bryce.schober@gmail.com \
--cc=crossgcc@sourceware.org \
/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).