Re: [kbuild-devel] kbuild for linux 2.4.x

2002-01-29 Thread Brendan J Simon
Where can I find documentation on how to install/run/patch or whatever I have to do to get this working with the latest 2.4 kernel for a powerpc architecture. I've downloaded kbuild-2.5-2.4.17-1.bz. Is that all I need ??? Thanks, Brendan Simon. Keith Owens wrote: Anything from 2.4.16

Re: [kbuild-devel] Re: kbuild for linux 2.4.x

2002-01-29 Thread Brendan J Simon
Keith Owens wrote: On Wed, 30 Jan 2002 11:07:43 +1100, Brendan J Simon [EMAIL PROTECTED] wrote: Where can I find documentation on how to install/run/patch or whatever I have to do to get this working with the latest 2.4 kernel for a powerpc architecture. I've downloaded kbuild-2.5-2.4.17

[kbuild-devel] Problems applying kbuild-2.5 to linuxppc-2.4.18-pre8

2002-02-13 Thread Brendan J Simon
I am trying to apply the kbuild-2.5-2.4.18-pre1-ppc-1 patches to a linuxppc-2.4.18-pre8 tree. The patches apply perfectly but I'm getting errors when I do a make -f $KBUILD_SRCTREE_000/Makefile-25 xconfig. The tail of the errors are : Ignoring symbolic link

[kbuild-devel] Re: Problems applying kbuild-2.5 to linuxppc-2.4.18-pre8

2002-02-13 Thread Brendan J Simon
the function parse_makefile_in() which is called from the file pp_makefile1.c. I'm stuck and don't know how to get rid of this error. Thanks, Brendan Simon. Brendan J Simon wrote: I am trying to apply the kbuild-2.5-2.4.18-pre1-ppc-1 patches to a linuxppc-2.4.18-pre8 tree. The patches apply

Re: [kbuild-devel] building kernel

2002-02-24 Thread Brendan J Simon
I'm not an expert on what you ask but see my comments below. mithun vasant bommannavar wrote: When we get the Linux kernel source code is the XWindow system code is available with it. If yes where is it. X does not come with the linux kernel. There are various implementations of X. The

[kbuild-devel] kbuild with symbolic links

2002-03-24 Thread Brendan J Simon
Does kbuild-2.5 work with symbolic links ? The configuration management system I am using checks out all files as symbolic links to the original. When I do a make -f $KBUILD_SRC_000/Makefile-2.5 xconfig I get the following errors. Any clues or suggestions ? Using ARCH='ppc' AS='as'

Re: [kbuild-devel] kbuild with symbolic links

2002-03-26 Thread Brendan J Simon
Keith Owens wrote: On Mon, 25 Mar 2002 13:45:04 +1100, Brendan J Simon [EMAIL PROTECTED] wrote: Does kbuild-2.5 work with symbolic links ? Not at the moment. The tree walk code must not follow symlinks to directories, othereise it gets very confused about where all the input files

Re: [kbuild-devel] Re: Announce: Kernel Build for 2.5, Release 2.0 is available

2002-04-07 Thread Brendan J Simon
Keith Owens wrote: It takes time to do all the analysis to work out what has changed and what has been affected. You might know that you only changed one file but kernel build and make don't know that until they have checked everything. Changing one file or specifying a command override

[kbuild-devel] KBUILD: upgrading to release 2 from previous release

2002-04-08 Thread Brendan J Simon
Is it easy to patch from release 2 from the the previous release of kbuild-2.5 ? ie. is it as easy as untarring everyting in the Linux source directory that has the previous kbuild-2.5 patches applied ?? Maybe I have to remvoe the Makefile-2.5 directory and the entire scripts directory first

Re: [kbuild-devel] KBUILD: upgrading to release 2 from previous release

2002-04-08 Thread Brendan J Simon
done this before. I guess it's a good time to try it (when the PPC patches are available). For now I'll keep going with the current PPC release. Thanks, Brendan Simon. Keith Owens wrote: On Tue, 09 Apr 2002 12:45:18 +1000, Brendan J Simon [EMAIL PROTECTED] wrote: Is it easy to patch from

[kbuild-devel] upgrading to kbuild-2.5 release 2

2002-04-08 Thread Brendan J Simon
On Mon, 2002-04-08 at 19:45, Brendan J Simon wrote: Is it easy to patch from release 2 from the the previous release of kbuild-2.5 ? ie. is it as easy as untarring everyting in the Linux source directory that has the previous kbuild-2.5 patches applied ?? Maybe I have to remvoe

[kbuild-devel] permissions on scripts

2002-04-11 Thread Brendan J Simon
In kbuild-2.5-release-1.12, some of the script files are checked for the correct permissions (see below for scripts/Makefile-2.5 fragment). Instead of trying to change the permissions of the source tree (which might be owned by another user, eg. aegis), would it be possible to _copy_ these

[kbuild-devel] makefile rules request

2002-04-12 Thread Brendan J Simon
Keith, I'd like to request a minor change to the makefile rules to generate targets. Could each rule start with removing the target. Example: %.o : %.c $(CC) $(CFLAGS) -c -o $@ $ becomes: %.o : %.c $(RM) $@ $(CC) $(CFLAGS) -c -o $@ $ The main reason is to satisfy some

[kbuild-devel] ppc 2.4.18 port

2002-04-22 Thread Brendan J Simon
I want to have a go at porting kbuild to the 2.4.18 kernel for the PPC arch. Are there any documents or howtos ? What is the best way to go about this ? Cheers, Brendan Simon. ___ kbuild-devel mailing list [EMAIL PROTECTED]

Re: [kbuild-devel] Re: kbuild for ppc

2002-04-23 Thread Brendan J Simon
Tom Rini wrote: On Tue, Apr 23, 2002 at 03:40:19PM +1000, Brendan J Simon wrote: Does anyone know if kbuild-2.5-release-1.12 supports the embedded ppc boards ? I've managed to configure the 2.4.18-pre8 kernel for a custom board. make installable creates the vmlinux file but the embedded

Re: [kbuild-devel] ppc 2.4.18 port

2002-04-23 Thread Brendan J Simon
Keith Owens wrote: Documentation/kbuild/kbuild-2.5.txt describes all the commands and has a section on converting old Makefiles. Tom Rini had a ppc 2.4.16 patch, use that as a starting point and talk to Tom. OK. Doing a patch against 2.4.* is easier because the kernel actually builds,

[kbuild-devel] can't build head_8260.S

2002-04-24 Thread Brendan J Simon
I am getting further in the ppc port for 2.4.x kernels. I'm stuck trying to compile head_8260.S in the boot/mbx directory. The error message is: make[1]: *** No rule to make target `arch/ppc/boot/mbx/head_8260.o', needed by `arch/ppc/boot/mbx/zvmlinux'. Stop. I don't know why. Where are the

Re: [kbuild-devel] can't build head_8260.S

2002-04-24 Thread Brendan J Simon
Keith Owens wrote: On Wed, 24 Apr 2002 18:06:57 +1000, Brendan J Simon [EMAIL PROTECTED] wrote: I am getting further in the ppc port for 2.4.x kernels. I'm stuck trying to compile head_8260.S in the boot/mbx directory. The error message is: make[1]: *** No rule to make target `arch/ppc/boot

[kbuild-devel] problem with select()

2002-04-25 Thread Brendan J Simon
I'm trying to use select() after a base_target() statement. Does select() behave differently in this case ? I'm getting the following error message: ...local object names must not contain '/' at 'arch/ppc/boot/common/dummy.o' My Makefile.in looks like: base_target(zvmlinux) select(image.o)

[kbuild-devel] installing header files

2002-05-05 Thread Brendan J Simon
Is there a way to install header files with kbuild ? (eg. make headers_install). I'm using a Configuration Management System that is pointing to kernel 2.4.18 source header files but an application can not find autoconf.h which is included by config.h. It seems autoconf.h is not in the

Re: [kbuild-devel] Re: installing header files

2002-05-05 Thread Brendan J Simon
Keith Owens wrote: On Mon, 06 May 2002 12:10:09 +1000, Brendan J Simon [EMAIL PROTECTED] wrote: I'm using a Configuration Management System that is pointing to kernel 2.4.18 source header files but an application can not find autoconf.h which is included by config.h. That violates

Re: [kbuild-devel] Re: installing header files

2002-05-05 Thread Brendan J Simon
Keith Owens wrote: On Mon, 06 May 2002 13:28:59 +1000, Brendan J Simon [EMAIL PROTECTED] wrote: Is there a way to do this with kbuild ? make ... $KBUILD_OBJTREE/.tmp_src builds $KBUILD_OBJTREE/.tmp_src as a forest of 10,000+ symlinks pointing to the latest version of every source file

Re: [kbuild-devel] Re: installing header files

2002-05-05 Thread Brendan J Simon
Keith Owens wrote: Is there a way to do this with kbuild ? make ... $KBUILD_OBJTREE/.tmp_src builds $KBUILD_OBJTREE/.tmp_src as a forest of 10,000+ symlinks pointing to the latest version of every source file, taking into account any shadow trees. cp -aL on that tree or a subset will get the

Re: [kbuild-devel] RFC: kernel config: new dependency syntax

2002-08-15 Thread Brendan J Simon
Greg Banks wrote: [*] almost enough because I haven't implemented an 'else' directive. It would be trivial, but I'm not sure what to call it. 'else' itself is a shell primitive, so the shell-based parsers (Configure, Menuconfig) wouldn't like it. You will need to implement

[kbuild-devel] kbuild status

2002-10-06 Thread Brendan J Simon
Hi kbuild team, What is the status of kbuild with respect to getting into the kernel proper ? Is it going to get into the linus kernel source tree ?? The reason I ask is that I require a kernel build system for the 2.4 kernel on a embedded PowerPC architecture. It seems that only the i386

Re: [kbuild-devel] kbuild status

2002-10-06 Thread Brendan J Simon
Peter Samuelson wrote: [Brendan J Simon] What is the status of kbuild with respect to getting into the kernel proper ? Is it going to get into the linus kernel source tree ?? At this point it doesn't seem likely. Of the rich feature set Keith produced, Kai Germaschewski has managed

Re: [kbuild-devel] Re: RfC: Don't cd into subdirs during kbuild

2002-10-08 Thread Brendan J Simon
Kai Germaschewski wrote: You must be missing some of the changes (My first push to bkbits was incomplete, since I did inadvertently edit Makefile without checking it out, I do that mistake all the time...). It's fixed in the current repo. Can't bitkeeper be setup to have readonly files for

Re: [kbuild-devel] Re: linux kernel conf 0.8

2002-10-09 Thread Brendan J Simon
Roman Zippel wrote: Well, my basic preference is * something other than Config.new (the original name in your config system) * something other than Config.in I think it is a mistake to name a totally different format the same name as an older format... even config.in would be better than