uberXMHF build error

Discussions related to uberXMHF running on Raspberry PI 3 ARMv8 32-bit hardware platform
Post Reply
uberhappy
Posts: 4
Joined: Fri Nov 30, 2018 2:27 am

uberXMHF build error

Post by uberhappy » Fri Nov 30, 2018 3:11 am

Hi,

I am trying to set up uberpi on my raspberry pi. However, I am hitting an error when running step 3 under section "6 Build uberXMHF Raspbery PI 3 on development system" (https://uberxmhf.org/docs/rpi3-cortex_a ... build.html) as shown below:

ubuser@ubuser-VirtualBox:~/uberxmhf-4.1/uxmhf-rpi3$ ./configure --with-boot-partition-start=8192 --with-boot-partition-end=137215
configure: creating ./config.status
config.status: creating ./include/config.h
rm: cannot remove 'core': Is a directory
ubuser@ubuser-VirtualBox:~/uberxmhf-4.1/uxmhf-rpi3$ echo $?
0

fdisk -l gives:
Disk /dev/sdb: 29.8 GiB, 32026656768 bytes, 62552064 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x244b8248

Device Boot Start End Sectors Size Id Type
/dev/sdb1 8192 137215 129024 63M c W95 FAT32 (LBA)
/dev/sdb2 137216 2715647 2578432 1.2G 83 Linux


Development system is Ubuntu 18.04 running on VM.
rpi-4.4.y was used as linux source; and 2016-11-25-raspbian-jessie-lite.zip was the pi image used. I tried to check the logs but cant seem to figure out why the trap is called(?) which tries to remove core directory. I had the same issue with uberxmhf-4.0 as well.

It would be really great if you can take a look and advise on what is wrong here. Thanks.

I am unable to attach log file; so appending it here:
config.log:
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

It was created by uxmhf-rpi3 configure 1.0, which was
generated by GNU Autoconf 2.69. Invocation command line was

$ ./configure --with-boot-partition-start=8192 --with-boot-partition-end=137215

## --------- ##
## Platform. ##
## --------- ##

hostname = ubuser-VirtualBox
uname -m = x86_64
uname -r = 4.15.0-39-generic
uname -s = Linux
uname -v = #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018

/usr/bin/uname -p = unknown
/bin/uname -X = unknown

/bin/arch = unknown
/usr/bin/arch -k = unknown
/usr/convex/getsysinfo = unknown
/usr/bin/hostinfo = unknown
/bin/machine = unknown
/usr/bin/oslevel = unknown
/bin/universe = unknown

PATH: /usr/local/sbin
PATH: /usr/local/bin
PATH: /usr/sbin
PATH: /usr/bin
PATH: /sbin
PATH: /bin
PATH: /usr/games
PATH: /usr/local/games
PATH: /snap/bin
PATH: /home/ubuser/tools/arm-bcm2708/arm-rpi-4.9.3-linux-gnueabihf/bin/


## ----------- ##
## Core tests. ##
## ----------- ##

configure:1906: creating ./config.status

## ---------------------- ##
## Running config.status. ##
## ---------------------- ##

This file was extended by uxmhf-rpi3 config.status 1.0, which was
generated by GNU Autoconf 2.69. Invocation command line was

CONFIG_FILES =
CONFIG_HEADERS =
CONFIG_LINKS =
CONFIG_COMMANDS =
$ ./config.status

on ubuser-VirtualBox

config.status:717: creating ./include/config.h

## ---------------- ##
## Cache variables. ##
## ---------------- ##

ac_cv_env_build_alias_set=
ac_cv_env_build_alias_value=
ac_cv_env_host_alias_set=
ac_cv_env_host_alias_value=
ac_cv_env_target_alias_set=
ac_cv_env_target_alias_value=

## ----------------- ##
## Output variables. ##
## ----------------- ##

BOOT_PARTITION_END='137215'
BOOT_PARTITION_START='8192'
CORE_SIZE='0xC00000'
CORE_STARTADDR='0x1000000'
DEFS='-DPACKAGE_NAME=\"uxmhf-rpi3\" -DPACKAGE_TARNAME=\"uxmhf-rpi3\" -DPACKAGE_VERSION=\"1.0\" -DPACKAGE_STRING=\"uxmhf-rpi3\ 1.0\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\"'
ECHO_C=''
ECHO_N='-n'
ECHO_T=''
LIBOBJS=''
LIBS=''
LTLIBOBJS=''
PACKAGE_BUGREPORT=''
PACKAGE_NAME='uxmhf-rpi3'
PACKAGE_STRING='uxmhf-rpi3 1.0'
PACKAGE_TARNAME='uxmhf-rpi3'
PACKAGE_URL=''
PACKAGE_VERSION='1.0'
PATH_SEPARATOR=':'
SHELL='/bin/bash'
bindir='${exec_prefix}/bin'
build_alias=''
datadir='${datarootdir}'
datarootdir='${prefix}/share'
docdir='${datarootdir}/doc/${PACKAGE_TARNAME}'
dvidir='${docdir}'
exec_prefix='${prefix}'
host_alias=''
htmldir='${docdir}'
includedir='${prefix}/include'
infodir='${datarootdir}/info'
libdir='${exec_prefix}/lib'
libexecdir='${exec_prefix}/libexec'
localedir='${datarootdir}/locale'
localstatedir='${prefix}/var'
mandir='${datarootdir}/man'
oldincludedir='/usr/include'
pdfdir='${docdir}'
prefix='/usr/local'
program_transform_name='s,x,x,'
psdir='${docdir}'
runstatedir='${localstatedir}/run'
sbindir='${exec_prefix}/sbin'
sharedstatedir='${prefix}/com'
sysconfdir='${prefix}/etc'
target_alias=''

## ----------- ##
## confdefs.h. ##
## ----------- ##

/* confdefs.h */
#define PACKAGE_NAME "uxmhf-rpi3"
#define PACKAGE_TARNAME "uxmhf-rpi3"
#define PACKAGE_VERSION "1.0"
#define PACKAGE_STRING "uxmhf-rpi3 1.0"
#define PACKAGE_BUGREPORT ""
#define PACKAGE_URL ""

configure: exit 0

dv-prime
Site Admin
Posts: 4
Joined: Sat Aug 11, 2018 12:59 am

Re: uberXMHF build error

Post by dv-prime » Fri Nov 30, 2018 4:35 am

Moved post to parent where we discuss general issues w.r.t rpi3_cortex_a53-armv8_32 including build issues.
...Development system is Ubuntu 18.04 running on VM...
The currently supported development platform is Ubuntu 16.04.x LTS. However, we can take a stab with 18.04...
...I am hitting an error when running step 3 under section "6 Build uberXMHF Raspbery PI 3 on development system"...
rm: cannot remove 'core': Is a directory
Did you try to execute steps 6.4 through 6.7? Does it still produce the final binary after 6.5?

uberhappy
Posts: 4
Joined: Fri Nov 30, 2018 2:27 am

Re: uberXMHF build error

Post by uberhappy » Sat Dec 01, 2018 1:17 am

I went ahead repeated the steps on Ubuntu 16.04. However, I hit the same error. I went ahead and executed the rest of the steps as you mentioned on a 2018-11-13-raspbian-stretch-lite.zip guest OS. I had to increase the size of the boot partition to copy over all the files due to space limitation. When starting it up, it is stuck at the rainbow screen. Any thoughts?

dv-prime
Site Admin
Posts: 4
Joined: Sat Aug 11, 2018 12:59 am

Re: uberXMHF build error

Post by dv-prime » Sun Dec 02, 2018 4:18 am

It seems to me from your description that you might have not expanded the raspbian filesystem to fit the entire sd card. Can you try with a fresh install of raspbian jessie with filesystem expanded to fit the entire sd card? You will need to boot into vanilla raspbian without the micro-hypervisor and accomplish this via the raspi-config tool.

uberhappy
Posts: 4
Joined: Fri Nov 30, 2018 2:27 am

Re: uberXMHF build error

Post by uberhappy » Sun Dec 02, 2018 6:25 am

I will try that, thanks. I was under the impression that the guest OS must be freshly installed and not be run before the framework is added.
BTW is the framework known to work with raspbian stretch on 3B+?

dv-prime
Site Admin
Posts: 4
Joined: Sat Aug 11, 2018 12:59 am

Re: uberXMHF build error

Post by dv-prime » Sun Dec 02, 2018 6:19 pm

BTW is the framework known to work with raspbian stretch on 3B+?
As mentioned in the docs (https://uberxmhf.org/docs/rpi3-cortex_a ... build.html), we have tested the framework extensively with the following 32-bit raspbian jessie lite image:

https://downloads.raspberrypi.org/raspb ... e-lite.zip

However, in principle, raspbian stretch (32-bit) should work as well.

uberhappy
Posts: 4
Joined: Fri Nov 30, 2018 2:27 am

Re: uberXMHF build error

Post by uberhappy » Sun Dec 02, 2018 8:33 pm

Thanks, I was finally able to run it with Jessie on a borrowed pi 3b. Programs crash a lot but at least it boots now. Is that a known issue?

I had no luck trying it with Stretch though. It stays at the rainbow screen.

dv-prime
Site Admin
Posts: 4
Joined: Sat Aug 11, 2018 12:59 am

Re: uberXMHF build error

Post by dv-prime » Mon Dec 03, 2018 2:07 am

Programs crash a lot but at least it boots now. Is that a known issue?
Could you give an example of what you mean by programs crashing? We have not had programs crash per se in our tests.
I had no luck trying it with Stretch though.
Support for stretch is not on the critical path right now, but we can look into it if we have volunteers like yourself interested in contributing :)

Post Reply