All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Is there any way for buildroot to test file	transfer access?
Date: Wed, 23 Jan 2008 18:41:49 +0100	[thread overview]
Message-ID: <20080123174149.GA21971@aon.at> (raw)
In-Reply-To: <1CD05B980C94AC408B37C82BBABAA3E609CEA2AE@mtsexchange.dc.multitech.prv>

On Wed, Jan 23, 2008 at 09:40:57AM -0600, Tim Barr wrote:
>Does buildroot have any command line function that goes through and
>checks all the locations it needs to download files from in order to
>verify that it has access to them? My IT blocks websites on the
>firewall, and I have had my make file fail twice because websites were
>blocked.
> 
>Or maybe you could publish a list on your website that shows all the
>urls that need to be accessed?

$ make help
Cleaning:
  clean                  - delete temporary files created by build
  distclean              - delete all non-source files (including .config)

Build:
  all                    - make world

Configuration:
  menuconfig             - interactive curses-based configurator
  oldconfig              - resolve any unresolved symbols in .config

Miscellaneous:
  source                 - download all sources needed for offline-build
  source-check           - check all packages for valid download URLs

See docs/README and docs/buildroot.html for further details

      reply	other threads:[~2008-01-23 17:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-23 15:40 [Buildroot] Is there any way for buildroot to test file transfer access? Tim Barr
2008-01-23 17:41 ` Bernhard Fischer [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=20080123174149.GA21971@aon.at \
    --to=rep.dot.nop@gmail.com \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.