Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
* [Buildroot] [Bug 9366] New: no link rootfs.ext4 -> rootfs.ext2
@ 2016-10-17 21:40 bugzilla at busybox.net
  2016-10-18 13:51 ` [Buildroot] [Bug 9366] " bugzilla at busybox.net
  2016-10-18 14:13 ` bugzilla at busybox.net
  0 siblings, 2 replies; 3+ messages in thread
From: bugzilla at busybox.net @ 2016-10-17 21:40 UTC (permalink / raw)
  To: buildroot

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

            Bug ID: 9366
           Summary: no link rootfs.ext4 -> rootfs.ext2
           Product: buildroot
           Version: unspecified
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: mikhail_tchernychev at yahoo.com
                CC: buildroot at uclibc.org
  Target Milestone: ---

Created attachment 6766
  --> https://bugs.busybox.net/attachment.cgi?id=6766&action=edit
this is .config file which make this problem.

Hi, I have compiled raspberry pi 3 image with config file attached here. 
Unfortunately at the very last stage I had manually link 

ln -s rootfs.ext2 rootfs.ext4

in the images/ directory, then run make again and it assembled sdcard.img

When I used default rpi3 config it was not the case, so it is something in my 
custom config, which is default based.

It seems it is something minor.

Thank you
Mikhail

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2016-10-18 14:13 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-10-17 21:40 [Buildroot] [Bug 9366] New: no link rootfs.ext4 -> rootfs.ext2 bugzilla at busybox.net
2016-10-18 13:51 ` [Buildroot] [Bug 9366] " bugzilla at busybox.net
2016-10-18 14:13 ` bugzilla at busybox.net

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox