From: Kilian Zinnecker via buildroot <buildroot@buildroot.org>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>, buildroot@buildroot.org
Cc: Robert Nelson <robertcnelson@gmail.com>,
Kilian Zinnecker via buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] Interested in board support for BeagleV-Ahead
Date: Fri, 18 Aug 2023 19:18:28 +0200 [thread overview]
Message-ID: <4850715.GXAFRqVoOG@kilian-aisec> (raw)
In-Reply-To: <CAOCHtYiuJimX-pF-hUhuK35X+63eE1GJbK=xAZOR73gb8iZkog@mail.gmail.com>
Hello Robert and Thomas,
I am making a bit of progress. However, I still have some issues.
[--SNIP--]
> Okay Kilian, these all build with
> x86_64-gcc-13.2.0-nolibc-riscv64-linux.tar.xz
>
> opensbi:
> https://git.beagleboard.org/beaglev-ahead/beaglev-ahead-opensbi/-/tree/0.9-> 1.1.2-ubuntu u-boot:
> https://git.beagleboard.org/beaglev-ahead/beaglev-ahead-u-boot/-/tree/beagl
> ev-v2020.01-1.1.2-ubuntu linux:
> https://git.beagleboard.org/beaglev-ahead/beaglev-ahead-linux/-/tree/beagle
> v-v5.10.113-1.1.2-ubuntu
>
> For bandwidth issues, please use the github mirrors directly in
> patches for buildroot, as these are push mirrored from
> git.beagleboard.org/ , at worst they lag by 10 minutes after a new
> commit
>
> opensbi:
> https://github.com/beagleboard/beaglev-ahead-opensbi/tree/0.9-1.1.2-ubuntu
> u-boot:
> https://github.com/beagleboard/beaglev-ahead-u-boot/tree/beaglev-v2020.01-1
> .1.2-ubuntu linux:
> https://github.com/beagleboard/linux/tree/beaglev-v5.10.113-1.1.2-ubuntu
When buildroot compiles opensbi, I get a lot of "undefined reference to
`__stack_chk_guard'" errors. I think that either the necessary "-fno-stack-
protector" flag is not active during build, or that the toolchain does not
provide the necessary functions. I tried adding something similar like this
https://gitlab.com/buildroot.org/buildroot/-/blob/master/boot/arm-trusted-firmware/arm-trusted-firmware.mk?ref_type=heads#L67-72
https://gitlab.com/buildroot.org/buildroot/-/blob/master/boot/arm-trusted-firmware/Config.in?ref_type=heads#L234-251
to the opensbi config and make files, but it did not help. I also checked and
the .config contains the following flags:
BR2_SSP_STRONG=y
BR2_SSP_OPTION="-fstack-protector-strong"
BR2_TARGET_OPENSBI_SSP=y
BR2_TARGET_OPENSBI_SSP_LEVEL="strong"
Does anyone have an idea? I can provide more info if needed.
Best regards,
Kilian
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-08-18 17:18 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 13:57 [Buildroot] Interested in board support for BeagleV-Ahead Kilian Zinnecker via buildroot
2023-08-09 17:38 ` Thomas Petazzoni via buildroot
2023-08-10 9:20 ` Kilian Zinnecker via buildroot
2023-08-10 11:02 ` Kilian Zinnecker via buildroot
2023-08-11 14:41 ` Thomas Petazzoni via buildroot
2023-08-11 21:30 ` Robert Nelson
2023-08-11 22:53 ` Robert Nelson
2023-08-12 9:51 ` Kilian Zinnecker via buildroot
2023-08-12 9:56 ` Thomas Petazzoni via buildroot
2023-08-18 17:18 ` Kilian Zinnecker via buildroot [this message]
2023-08-18 21:33 ` Robert Nelson
2023-08-18 21:35 ` Robert Nelson
2023-08-20 12:54 ` Kilian Zinnecker via buildroot
2023-08-21 21:43 ` Thomas Petazzoni via buildroot
2023-08-10 15:25 ` Kilian Zinnecker via buildroot
2023-08-11 14:48 ` Thomas Petazzoni via buildroot
2023-08-12 9:56 ` Kilian Zinnecker via buildroot
2023-08-12 10:19 ` Thomas Petazzoni via buildroot
2023-08-12 11:06 ` Kilian Zinnecker via buildroot
2023-08-11 14:40 ` Thomas Petazzoni via buildroot
2023-08-10 16:34 ` Robert Nelson
2023-08-10 17:03 ` Kilian Zinnecker via buildroot
2023-08-10 18:57 ` Robert Nelson
2023-08-10 19:05 ` Robert Nelson
2023-08-10 19:53 ` Kilian Zinnecker via buildroot
2023-08-10 20:45 ` Robert Nelson
2023-08-11 7:11 ` Kilian Zinnecker via buildroot
2023-08-10 20:38 ` Kilian Zinnecker via buildroot
2023-08-10 20:53 ` Robert Nelson
2023-08-11 7:07 ` Kilian Zinnecker via buildroot
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=4850715.GXAFRqVoOG@kilian-aisec \
--to=buildroot@buildroot.org \
--cc=kilian.zinnecker@mail.de \
--cc=robertcnelson@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
/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