This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.

See crosstool-NG for lots more information.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Why not download into CT_LOCAL_TARBALLS_DIR?

From: Bryce Schober <bryce dot schober at gmail dot com>
To: crossgcc at sourceware dot org
Date: Mon, 16 Dec 2013 15:58:55 -0800
Subject: Re: Why not download into CT_LOCAL_TARBALLS_DIR?
Authentication-results: sourceware.org; auth=none
References: <CAJpxd07ND0CLuHG=pHi+995Z=e_RbgZxwzppLw91PgBkpOigqA at mail dot gmail dot 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

References:
- Why not download into CT_LOCAL_TARBALLS_DIR?
  - From: Bryce Schober

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]