unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: c4droid <c4droid@foxmail.com>
To: Joshua Branson <jbranso@dismail.de>
Cc: busybox@busybox.net, help-guix@gnu.org
Subject: Re: Pack busybox using guix, but make check have fail tests
Date: Mon, 24 May 2021 15:45:29 +0800	[thread overview]
Message-ID: <tencent_316C258D7ED281A4C89D956838F6FA004905@qq.com> (raw)
Message-ID: <87zgwky3qe.fsf@foxmail.com> (raw)
In-Reply-To: <87a6ok8z2y.fsf@dismail.de>

Hi, Joshua!

Joshua Branson writes:

> c4droid <c4droid@foxmail.com> writes:
>
>> Hi,
>>
>> I'm working on the using busybox to provide the guix bootstrap recipes
>> for my building Linux From Scratch system using GNU Guix projects. when
>> I pack the busybox using guix, I copy the original package definitions
>> from gnu/packages/busybox.scm, I add enable-static-link build phases to
>> make busybox static linked. At building test, guix can build busybox
>> perfectly, but at running test suites, I got test failed about mdev
>> components, I check guix original package definitions for busybox, build
>> it, mdev test suites is skipped, I don't know how to skip the mdev test
>> suites, hope get some guidence for skip the mdev test suites, thanks. :)
>>
>> My busybox package definitions is at https://github.com/c4dr01d/guix-lfs-bootstrap/blob/master/lfs/packages/busybox.scm
>
> AWESOME!  Thanks for working on this!  Best of luck!
>
> I am commenting just because.  I'm a guix contributor not a developer,
> so please take my words with a grain of salt.  :)
>
> I believe that busybox has a more permissive license than coreutils?  Is
> that true?   I think I heard rms suggest that one should develop for
> coreutils more than busybox.  Someone please correct me if I am mistaken
> in some way.
>

Busybox takes the GPL 2 license, coreutils takes GPL3+

You may right, in other hands, my learning linux kernel development lab
need static linked busybox too, for create initramfs in test the kernel
modules proposes. Maybe have a better options, other solutions are
welcome.

And, I want my bootstrap recipes even smaller, by busybox with mescc
combinations. I think for a while, the busybox take many UNIX utililies
in one single executables, even the coreutils, that fits my expects.

But the way, thanks for your words and the grains of salt and thank you
for affirming my work. :)

> Anyway, great job!  And best of luck!


  reply	other threads:[~2021-05-24 19:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87lf8adazj.fsf@foxmail.com>
2021-05-19 15:00 ` Pack busybox using guix, but make check have fail tests c4droid
2021-05-24  5:45   ` Joshua Branson
     [not found]     ` <87zgwky3qe.fsf@foxmail.com>
2021-05-24  7:45       ` c4droid [this message]
2021-05-24 14:11     ` Bone Baboon
2021-05-24 22:15       ` Joshua Branson

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=tencent_316C258D7ED281A4C89D956838F6FA004905@qq.com \
    --to=c4droid@foxmail.com \
    --cc=busybox@busybox.net \
    --cc=help-guix@gnu.org \
    --cc=jbranso@dismail.de \
    /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).