Hello,
On 3/8/23 01:42, Joel Sherrill wrote:
Subject:
Re: Help regarding Building x86_64 BSP
From:
Joel Sherrill <j...@rtems.org>
Date:
3/8/23, 01:42
To:
Karel Gardas <karel@functional.vision>
CC:
"rtems-de...@rtems.org" <devel@rtems.org>
Did you build the x86_64 tools and qemu using the RTEMS Source Builder?
The only information I can contribute to this discussion are the results
our Continuous Integration Server currently creates when building x86_64
tools with the RTEMS Source Builder:
almalinux 8.7: OK [gcc (GCC) 8.5.0]
debian 11: OK [gcc (Debian 10.2.1-6) 10.2.1]
fedora 37: Failure [gcc (GCC) 12.2.1]
opensuse-leap 15.4: Failure [gcc (SUSE Linux) 12.2.1]
ubuntu 22.04: Failure [gcc (Ubuntu 12.1.0-2ubuntu1~22.04) 12.1.0]
These builds were for RTEMS 6 and RSB
GIT_HEAD="bfed51462eafcb6a5102a2d6d80b233f3c6ef635".
The build failures all happen when `building:
grub2-2.06-x86_64-linux-gnu-1` which is the last build step. There are
several similar errors. These are two of them taken from the build log:
cc1: all warnings being treated as errors
util/mkimage.c: In function ‘grub_install_generate_image’:
util/mkimage.c:1386:41: error: dangling pointer to ‘tmp_’ may be used
[-Werror=d
angling-pointer=]
1386 | PE_OHDR (o32, o64, header_size) = grub_host_to_target32
(header_
size);
util/mkimage.c:857:28: note: ‘tmp_’ declared here
857 | __typeof__((o64)->field) tmp_; \
| ^~~~
util/mkimage.c:1386:9: note: in expansion of macro ‘PE_OHDR’
1386 | PE_OHDR (o32, o64, header_size) = grub_host_to_target32
(header_
size);
| ^~~~~~~
util/mkimage.c:1387:40: error: dangling pointer to ‘tmp_’ may be used
[-Werror=d
angling-pointer=]
1387 | PE_OHDR (o32, o64, entry_addr) = grub_host_to_target32
(layout.s
tart_address);
util/mkimage.c:857:28: note: ‘tmp_’ declared here
857 | __typeof__((o64)->field) tmp_; \
| ^~~~
util/mkimage.c:1387:9: note: in expansion of macro ‘PE_OHDR’
1387 | PE_OHDR (o32, o64, entry_addr) = grub_host_to_target32
(layout.s
tart_address);
| ^~~~~~~
Maybe one needs a new version of grub sources for gcc 12?
Greetings
Frank
On Tue, Mar 7, 2023, 11:39 AM Karel Gardas<karel@functional.vision> wrote:
On 3/7/23 19:24, Karel Gardas wrote:
On 3/7/23 15:05, Siddharth Khattar wrote:
Hello all,
So I was aiming to make a project to improve the amd64 BSP for RTEMS
(modify it according to ACPI standards along with other stuff) but
first I would need to build it. Unfortunately there was no way to
build it natively within RTEMS source. So, I needed to install QEMU
and had to build the UEFI firmware,OVMF by Tianocore in order to build
it.
Indeed, they still list Ubutnu 16.04 LTS as a build OS. Hmm, I would go
with VM for this. You need to build it just once...
Investigating more, it looks like qemu build those too, so there is no
need to deal with TianoCore alone anymore. My 7.2.0 install contains:
$ find qemu-7.2.0/share/qemu/ -name 'edk2*'
qemu-7.2.0/share/qemu/edk2-arm-code.fd
qemu-7.2.0/share/qemu/edk2-x86_64-code.fd
qemu-7.2.0/share/qemu/edk2-arm-vars.fd
qemu-7.2.0/share/qemu/edk2-i386-secure-code.fd
qemu-7.2.0/share/qemu/edk2-x86_64-secure-code.fd
qemu-7.2.0/share/qemu/edk2-aarch64-code.fd
qemu-7.2.0/share/qemu/edk2-i386-code.fd
qemu-7.2.0/share/qemu/edk2-i386-vars.fd
qemu-7.2.0/share/qemu/edk2-licenses.txt
Ditto for Qemu build by RSB. Will send you tarball of scripts I'm using
for building and running rtems.exe on those...
Karel
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
--
embedded brains GmbH
Herr Frank KÜHNDEL
Dornierstr. 4
82178 Puchheim
Germany
email: frank.kuehn...@embedded-brains.de
phone: +49-89-18 94 741 - 23
mobile: +49-176-15 22 06 - 11
fax: +49-89-18 94 741 - 08
Registergericht: Amtsgericht München
Registernummer: HRB 157899
Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler
Unsere Datenschutzerklärung finden Sie hier:
https://embedded-brains.de/datenschutzerklaerung/
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
