[Bug 262554] [armv7] [GENERICSD] release.sh fails

[email protected]
Newsgroups gmane.os.freebsd.devel.arm
Message-ID <[email protected]/bugzilla/>
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262554

            Bug ID: 262554
           Summary: [armv7] [GENERICSD] release.sh fails
           Product: Base System
           Version: CURRENT
          Hardware: arm
                OS: Any
            Status: New
          Keywords: regression
          Severity: Affects Only Me
          Priority: ---
         Component: arm
          Assignee: [email protected]
          Reporter: [email protected]

I am trying to build a vanilla -CURRENT image for my beaglebone enhanced. 

In release/arm/GENERICSD.conf, I added info about CHROOT_DIR, MAKE_CONF,
SRC_CONF (both with harmless contents, imho), and changed GENERIC to
GENERIC-NODEBUG. 

I run sh ./release.sh -c arm/GENERICSD.conf and got the following:

--------------------------------------------------------------
>>> Kernel(s)  GENERIC-NODEBUG built in 94 seconds, ncpu: 40, make -j20
--------------------------------------------------------------
md0 created
md0s1 added
active set on md0s1
/dev/md0s1: 102264 sectors in 12783 FAT16 clusters (4096 bytes/cluster)
BytesPerSec=512 SecPerClust=8 ResSectors=1 FATs=2 RootDirEnts=512 Media=0xf0
FATsecs=50 SecPerTrack=63 Heads=255 HiddenSecs=0 HugeSectors=102400
md0s2 added
md0s2 created
gpart: No partitioning scheme found on geom /dev/md0s2. Create one first using
'gpart create'.

The error is raised on line 80 of tools/arm.subr:

chroot ${CHROOTDIR} gpart add -t freebsd-ufs -a 64k /dev/${mddev}s2

It seems quite weird that it fails on this line, because there is a "gpart
create" command on line 79. The whole sequence of commands here looks correct
to me. Could it be a timing issue? 

The building host is an amd64 running -CURRENT (from yesterday)

By the way, if I change PART_SCHEME="GPT" and change the arm_install_uboot_*
functions in GENERICSD.conf,  to account for the different names of partitions
in GPT vs MBR, I can successfully build a GPT image (I haven't tried booting it
yet though).

-- 
You are receiving this mail because:
You are the assignee for the bug.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.