[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [ttylinux:123] Re: No log for kernel build failure.
> Nope, since everything seems to be continuously cleaned I had to
> remove the redirect in the script that was sending the output to a log
> that was not persistent after the failure. After removing the
> redirect, I was presented with some questions which probably are new
> and don't match a configuration you saved away. Once I answered the
> questions interactively the kernel build was successful. Not pretty
> but at least I can build.
> Two questions. I need to modify a few things and can't figure out yet
> where they are buried.
> 1. Want to change ( eth0 ) to be a fixed address but even if I loop
> mount the IMG file and make my changes to be DHCP=NO the nic always
> starts as DHCP when I boot the ISO.
Try these steps:
$ make mount
$ vi mnt/etc/sysconfig/network-scripts/ifcfg-eth0
$ make umount
$ make fsys
$ make boot
and then try that ISO.
> 2. Why does everything start from scratch, can't ( gnu make ) pick up a
> change say to one thing and only build a single time unless you clean.
> It seems this learning process is a continuous start from scratch
> every time you make even a simple change.
Because the ttylinux build process uses *make* as a user
interface; instead of having a bunch of different scripts
to invoke from the command line you use "make <thing-to-make>"
It is not the best use of make.
There is no good description, I think, of the various
make targets, but you can make individual packages and
then remake the file system image with "make fsys", so
as to not start all over. "make boot" remakes the ISO
from the kernel and file system image.
> On Dec 14, 7:03 pm, Douglas Jerome <[email protected]> wrote:
>> BruceFerjulian wrote:
>>> Missing is some useful information on why the build failed.
>>> x86_64 linux-188.8.131.52 ...... g.b.Kernel FAILED.
>>> make: *** [kernel] Error 1
>>> The kernel is not built.
>>> make: *** [var/run/kernel] Error 1
>>> This is it, no logfile, nothing. Where would one start?
>> Did you look for a log file in var/log ?