Hi,
On Sep 24, 2010, at 8:47 PM, Jan Rovins wrote:
>
> Ok, Everything looks good with the Mips64 build until the kernel.
>
> I was getting the following error with both the generic Mips64 kernel, and My
> board specific kernel when built via the T2 SDE.
>
> ===[main_lx:84 (last $?=0)> case "$lx_cpu" in
> ===[main_lx:98 (last $?=0)> cp -vf vmlinux.ecoff
> /opt/T2/t2-trunk/build/Mips64-orig-9.0-trunk-generic-mips64-EB-cross-linux/boot/vmlinux_2.6.35.5-dist.ecoff
> cp: cannot stat `vmlinux.ecoff': No such file or directory
> Due to previous errors, no 1-linux26.log file!
> (Try enabling xtrace in the config to track an error inside the build system.)
> --- BUILD ERROR ---
>
> Upon investigation, the linux.mips kernel folk have recently changed the
> location of the vmlinux.ecof file. They have moved it down into
> arch/mips/boot/vmlinux.ecof. it used to be up in the top dir with vmlinux.
>
> There is a dependency in the linux24.conf file that has the path of this file
> hard coded. that file is pulled in for the 2.6 kernel builds too.
>
> To build a 2.6.35.5 kernel, the following change is needed:
>
> -----------------------------------------------------------------------
> Index: package/base/linux24/linux24.conf
> ===================================================================
> --- package/base/linux24/linux24.conf (revision 37685)
> +++ package/base/linux24/linux24.conf (working copy)
> @@ -95,7 +95,7 @@
> gzip < vmlinux >
> $root/boot/vmlinux_${lx_kernelrelease}.gz
> ;;
> mips)
> - cp -vf vmlinux.ecoff
> $root/boot/vmlinux_${lx_kernelrelease}.ecoff
> + cp -vf arch/${lx_cpu}/boot/vmlinux.ecoff
> $root/boot/vmlinux_${lx_kernelrelease}.ecoff
> ;;
> ppc)
> for x in arch/ppc/boot/images/zImage.* ; do
I conditional-ized it to still work for the linux24 package:
Committed revision 37687.
> -----------------------------------------------------------------------------------------------------
> After that fix, if fails on the mkinitrd stage, since we don't have dietlibc,
> and therefore we don't have embutils which depends on it, and mkinitrd wants
> these, or fails, so the quick fix is to skip over mkinitrd for now, so we can
> continue with the build. need to find a better permanent solution...
> -----------------------------------------------------------------------------------------------------------
> Index: package/base/mkinitrd/mkinitrd.desc
> ===================================================================
> --- package/base/mkinitrd/mkinitrd.desc (revision 37686)
> +++ package/base/mkinitrd/mkinitrd.desc (working copy)
> @@ -21,6 +21,7 @@
>
> [C] base/system
> [F] CROSS
> +[R] -mips64
>
> [L] GPL
> [S] Stable
> ---------------------------------------------------------------------------------
> Now the linux26 builds, but some stage 1 packages after the kernel build are
> still failing, (like mpfr) will post further progress as it happens...
Now, that is a really generic package "just" copying some files together, in
theory (with one or another fix / tweak) it would even work with dynamically
linked binaries, ... It really should not be marked -mips64 in our tree.
René
--
René Rebe, ExactCODE GmbH, Jaegerstr. 67, DE-10117 Berlin
http://exactcode.com | http://t2-project.org | http://rene.rebe.de
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[email protected] with a subject of: unsubscribe t2
