Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10036] Buildroot builds Raspbian Jessie headless image presenting incorrect prompt
Date: Wed, 12 Jul 2017 07:51:47 +0000	[thread overview]
Message-ID: <bug-10036-163-QRI3MthBRU@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-10036-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=10036

--- Comment #4 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
Paul, I think you are very confused about what Buildroot and what Raspbian are.
Buildroot and Raspbian have nothing in common, and trying to "build" Raspbian
with Buildroot doesn't make any sense at all.

Buildroot is an embedded Linux build system, to build highly customized Linux
systems by cross-compilation. It does not build Linux distributions with binary
packages, but just a root filesystem image, with no package management system
at all.

Raspbian is based on Debian, and provides a full-featured Linux distribution,
with a package management system.

There is simply no way Buildroot can be used to "produce" Raspbian.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

      parent reply	other threads:[~2017-07-12  7:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-11 20:45 [Buildroot] [Bug 10036] New: Buildroot builds Raspbian Jessie headless image presenting incorrect prompt bugzilla at busybox.net
2017-07-11 21:29 ` [Buildroot] [Bug 10036] " bugzilla at busybox.net
2017-07-11 21:49 ` bugzilla at busybox.net
2017-07-11 22:48 ` bugzilla at busybox.net
2017-07-12  7:51 ` bugzilla at busybox.net [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=bug-10036-163-QRI3MthBRU@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox