Re: [Ltib] Error: No rule to make target uImage

[Stuart Hughes]

Hi Michel,

This platform had not been built for years and some updates broke it the
default target build changed from vmlinux to uImage, which is not
supported on the older kernel in that BSP.

I've made some fix-ups that allow this to build now however:

* You cannot use gcc4 as it won't build that kernel (it has
m68-linux-gcc hard-wired somewhere)

* I had to disable timezone, which won't build with the older gcc
compiler selected.

Aside from that, if you do:

cvs up -dP
./ltib

It should build for you now.

Regards, Stuart

Michel Helms wrote:
> Hi,
> 
> I am using Ltib to build for the SenTec Cobra5475 board. After executing
> "./ltib" (selected the board, then in configuration left all options to
> default) the build process started. It did stuff for a few minutes and
> then stopped with an error. The last few lines in my console:
> 
> + [ -n  ]
> + [ %{kernel_series} = 2.4 ]
> + make ARCH=m68k HOSTCC=ccache /usr/bin/gcc -B/usr/bin// uImage
> make: *** No rule to make target `uImage'.  Stop.
> error: Bad exit status from /home/mihelms/ltib/tmp/rpm-tmp.70560 (%build)
> 
> 
> RPM build errors:
>     Bad exit status from /home/mihelms/ltib/tmp/rpm-tmp.70560 (%build)
> Build time for kernel-2.6.10-COBRA5475: 37 seconds
> 
> Failed building kernel-2.6.10-COBRA5475
> 
> 
> f_buildrpms() returned an error, exiting
> traceback:
>  main:567
> 
> 
> Started: Tue Nov 30 14:21:31 2010
> Ended:   Tue Nov 30 15:29:24 2010
> Elapsed: 4073 seconds
> 
> VERSION          : 10.1.1
> CVS_VERSION      : $Revision: 1.71 $ (Savannah)
> PLATFORM         : cobra5475
> GNUTARCH         : m68k
> TOOLCHAIN        : freescale-coldfire-m68k-linux-gnu-4.1-14.i686.rpm
> TOOLCHAIN_CFLAGS : -mcfv4e -O2 -w
> 
> These packages failed to build:
> kernel-2.6.10-COBRA5475
> 
> Build Failed
> 
> Exiting on error or interrupt
> --------------------------------- End of console excerpt
> 
> 
> I searched the web but didn't really find an answer. Does anyone have an
> idea of what could have went wrong or how to get around that problem?
> 
> Thanks in advance,
> Michel
>