From: "Marc-François LUCCA-DANIAU" <mfld.fr@gmail.com>
To: ELKS <linux-8086@vger.kernel.org>
Subject: Re: Fwd: Error when running ./build.sh
Date: Mon, 27 Feb 2017 08:36:48 +0100 [thread overview]
Message-ID: <CACpuWUn18irsE39uhbZQsrc3SgUTWdK1xM79AyKpOR-BLz9yQw@mail.gmail.com> (raw)
In-Reply-To: <be712b02-e1bc-fd2c-36dd-e02462e8e687@jodybruchon.com>
Yes, probable, the flopy images were already at the limit, so we will
perform a little cleanup. Could you open an issue on Github, please,
for this problem to be tracked ?
MFLD
2017-02-27 7:42 GMT+01:00 Jody Bruchon <jody@jodybruchon.com>:
> On 2017-02-27 1:35 AM, Derek Johansen wrote:
>>
>> After pulling in the ethernet updates I try to run
>>
>> sudo ./build.sh
>>
>> and get the following error:
>>
>> for DEL in sbin/partype sbin/ramdisk bin/clock; do rm /mnt/elks/$DEL;
>> done || true
>> [ "yes" = "yes" ] && \
>> cp -p /home/djohanse/elk2/elks/elkscmd/ktcp/ktcp /mnt/elks/bin || true
>> mkdir -p /mnt/elks/boot
>> cp /home/djohanse/elk2/elks/elks/arch/i86/boot/Image /mnt/elks/boot/linux
>> cp: error writing ‘/mnt/elks/boot/linux’: No space left on device
>> cp: failed to extend ‘/mnt/elks/boot/linux’: No space left on device
>> make[1]: *** [_build_bootable_target] Error 1
>> make[1]: Leaving directory `/home/djohanse/elk2/elks/elkscmd'
>> make: *** [full5] Error 2
>> Build script has terminated with error 8
>
> full5 is the 1.2M floppy image. Chances are that something in elkscmd will
> need to be dropped from it to make it work in the default configuration.
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-8086" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2017-02-27 7:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAOv0vd=LuWeT39DP_vzqb-bNqsXyag-tuddQsjkSQbuJq4_qMQ@mail.gmail.com>
2017-02-27 6:35 ` Fwd: Error when running ./build.sh Derek Johansen
2017-02-27 6:42 ` Jody Bruchon
2017-02-27 7:17 ` Georg Potthast
2017-02-27 7:36 ` Marc-François LUCCA-DANIAU [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=CACpuWUn18irsE39uhbZQsrc3SgUTWdK1xM79AyKpOR-BLz9yQw@mail.gmail.com \
--to=mfld.fr@gmail.com \
--cc=linux-8086@vger.kernel.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).