Hi Rene,
I usually do cross builds because I am mostly building for embedded
projects, and have little need for a desktop build. I will still need to
corssbuild for x86_64 to get highly specific build options for a project.
I currently got through almost everything, except for the final kernel
build, where depmod is not behaving correctly in the cross build
context. I will post the detailed errors later, because I have to work
on other things today.
I also tried a native build, hoping that it would work better, but am
running into some regressions there too:
1. kmod at the stage 1 build want lzma. I added xz to build at stage 1,
and removed the confopts that disable the lzma options, and that seemed
to work.
2. meson broke next with this error:
running install
error: can't create or remove files in install directory
^1-meson
The following error occurred while trying to add or remove files in the
installation directory:
^1-meson
[Errno 2] No such file or directory:
'/opt/t2-trunk/build/GenMin-no-cross-9.0-svn-generic-x86-64-linux/usr/lib/python3.7/site-packages/test-easy-install-31694.write-test'
^1-meson
The installation directory you specified (via --install-dir, --prefix, or
the distutils default setting) was:
^1-meson
/opt/t2-trunk/build/GenMin-no-cross-9.0-svn-generic-x86-64-linux/usr/lib/python3.7/site-packages/
^1-meson
This directory does not currently exist. Please create it and try again, or
choose a different installation directory (using the -d or --install-dir
option).
Haven't looked into this yet, maybe a python dependency, (when I make
the chroot from the iso, there are a lot of fixups needed for python)
Will send more detailed information & maybe some patches for these on my
next T2 marathon session (probably on the weekend) if you or scsijon
does not beat me to it.
Regards,
Jan
On 3/3/20 3:15 AM, René Rebe wrote:
Hi Jan,
you do not really need a cross build for x86* on x86*, unless you want to for
quality control testing reasons. I usually don’t do this though.
Also some 36h ago I did some sed cleanup of removing the stray, superfluous
stuff in scripts/* I hope that did not cause any typo or regressions.
Will be test building more again this week.
Oh, and yes, the switch from the deprecated module-init-tools kmod and an
updated udev is not yet the most tested. I was considering updating dev even
further to the flavor inside systemd (sigh) before a do whole system dev
testing which as usually nowadays with the state of upstream changes might
cause a problem or regression, or two :-/
René
On 2. Mar 2020, at 23:46, Jan Rovins <[email protected]> wrote:
I am doing a cross build. But it’s x86-64 to x86-64
J
On Mar 2, 2020, at 7:52 AM, scsijon <[email protected]> wrote:
?strange, mine doesn't need libusb or usbutils for udev. Just a thought, how
are you building, ?maybe on a external hard drive or memory stick connected via
usb?
On 02/03/20 14:52, Jan Rovins wrote:
Several things missing for udev when cross building:
checking for USBUTILS... no
configure: error: Package requirements (usbutils >= 0.82) were not met:
No package 'usbutils' found
I added usbutils to target/generic/pkgsel/20-minimal.in
Then when trying to build usbutils I got:
checking for LIBUSB... no
configure: error: Package requirements (libusb-1.0 >= 1.0.0) were not met:
No package 'libusb-1.0' found
So I added libusb to target/generic/pkgsel/20-minimal.in
Then usbutils cross built OK, but udev failed again
checking for USBUTILS... yes
checking for USB database location... /usr/share/usb.ids
configure: error: pci.ids not found, try --with-pci-ids-path=
Due to previous errors, no 1-udev.log file!
(Try enabling xtrace in the config to track an error inside the build system.)
--- BUILD ERROR ---
So I added this to udev.conf:
atstage cross && var_append confopt " " " --with-pci-ids-path=$root/usr/share/"
Patches attached.
Note libusb is still in 50-minimal-desktop.in, probbably should be removed
since i think 20-minimal.in should cover it for everyone.
Jan
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[email protected] with a subject of: unsubscribe t2
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[email protected] with a subject of: unsubscribe t2
