-
Notifications
You must be signed in to change notification settings - Fork 365
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Building a custom initrd
with the linux-image.sh
script of the docker image fails on powerpc64
#1399
Closed
4 of 11 tasks
Comments
Id be very interested in a pr with fixes to this! |
Ok :) I'm a little bit busy right now, but I'll start a pr the next days. |
gamma0987
added a commit
to gamma0987/cross
that referenced
this issue
Jan 7, 2024
gamma0987
added a commit
to gamma0987/cross
that referenced
this issue
Jan 7, 2024
gamma0987
added a commit
to gamma0987/cross
that referenced
this issue
Jan 7, 2024
gamma0987
added a commit
to gamma0987/cross
that referenced
this issue
Jan 8, 2024
github-merge-queue bot
pushed a commit
that referenced
this issue
Jan 8, 2024
As promised here's the fixed `linux-image.sh` script. As outlined in #1399 this pr fixes: * Missing gpg key 8D69674688B6CB36 (Debian Ports Archive Automatic Signing Key (2024) <ftpmaster@ports-master.debian.org>) * The binaries and busybox might also be installed into `/usr/bin/` instead of `/bin`. * The kernel modules might also installed into `/usr/lib/modules` instead of `/lib/modules`. * The kernel modules might be compressed with `xz` and end with `*.ko.xz` instead of just `*.ko` The first commit adds some vim special files to `.gitignore` and in the second commit the script was formatted with `shfmt` with standard settings and some minor issues from `shellcheck` were fixed. The third commit fixes the actual issues. Not sure if you wanna keep the first two commits but they made working on this file easier. Closes #1399
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Checklist
Describe your issue
I needed to run cross with
CROSS_RUNNER=qemu-system
with thepowerpc64-linux-unknown-gnu
target. I was missing the debug symbols forlibc6
within the initrd image which are provided by thelibc6-dbg
package, so I adjusted the/linux-image.sh
shell script within the docker image and ran it with/linux-image.sh powerpc64
. However, I wasn't able to build an initrd with the providedlinux-image.sh
script which actually boots. Long story short:There were some issues within this script which I finally fixed to be able to build a successfully booting
/qemu/initrd.gz
and/qemu/kernel
.Problems:
Debian Ports Archive Automatic Signing Key (2024) <ftpmaster@ports-master.debian.org>
)busybox
are installed into/usr/bin/
instead of/bin
./bin
is used in thelinux-image.sh
script. I think this happens due to the usage of theports
debian mirror. The ports binaries were installed into/usr/bin
./usr/lib/modules
instead of/lib/modules
./lib/modules
is used in thelinux-image.sh
.xz
and end with*.ko.xz
instead of*.ko
Unlike other targets
powerpc64
uses a pretty recent kernel (linux-image-6.6.8-powerpc64
) and I think3.
and4.
are related to that. None of these problems were particularly hard to fix. Are you interested in a pr with a fixedlinux-image.sh
script?What target(s) are you cross-compiling for?
powerpc64-unknown-linux-gnu
Which operating system is the host (e.g computer cross is on) running?
What architecture is the host?
What container engine is cross using?
cross version
cross 0.2.5
Example
No response
Additional information / notes
No response
The text was updated successfully, but these errors were encountered: