On 9/12/18 9:00 AM, ALeX Kazik wrote: > until now I used a about 4 your old installation inside a VM to build > my m68k kernel and it does work. > > Now I thought I can use Docker to make a few steps easier. > Attached is my current workflow including my .config.
Why though? You can just install the "gcc-m68k-linux-gnu" compiler package and maybe things like libncurses-dev:m68k with the help of Multi-Arch and you're set. > The same kernel (4.18.6) that I did build in the VM (about 4 year old > ubuntu, never updated) fails in the docker environment (current debian > sid & tools) with: > > m68k-linux-gnu-ld: drivers/rtc/rtc-proc.o: in function > `is_rtc_hctosys.isra.0': > rtc-proc.c:(.text+0x378): undefined reference to `strcmp' Whenever you run into kernel building issues, you should first check whether the kernel builds on the buildds: > https://buildd.debian.org/status/package.php?p=linux&suite=sid > https://buildd.debian.org/status/package.php?p=linux&suite=experimental We have seen this failure in 4.19 on experimental as well. So it's not a problem in your build environment. > If I disable "/proc/driver/rtc (procfs for rtcN)" > (CONFIG_RTC_INTF_PROC ) then it works. > > (Installing libc6-dev-m68k-cross makes no difference.) > > Any suggestions? For kernel-specific questions, please always ask on the linux-m68k LKML. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
