Re: makefile bash2 typo (Re: We interrupt you regularly scheduled catfight for.. Linux 2.2.18pre13)

[Andreas Schwab]

Tim Waugh <[EMAIL PROTECTED]> writes:

|> On Mon, Oct 02, 2000 at 07:47:54AM -0700, Clayton Weaver wrote:
|> 
|> > What is the second "fi" for?
|> 
|> The first "if".

Btw, the Bourne language also has `elif':

  CONFIG_SHELL := $(shell if [ -x "$$BASH" ]; then echo $$BASH; \
elif [ -x /bin/bash ]; then echo /bin/bash; \
else echo sh; fi)

Andreas.

-- 
Andreas Schwab  "And now for something
SuSE Labscompletely different."
[EMAIL PROTECTED]
SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: We interrupt you regularly scheduled catfight for.. Linux 2.2.18pre13

[Christoph Hellwig]

On Mon, Oct 02, 2000 at 05:17:46PM +0200, Pavel Machek wrote:
> Actually there's another compiler (codepro or how is it called), made
> by SGI(?) for merced, available under gpl, and hving all gcc
> extensions, including __asm__().

SGI Pro64 - it's IA64 only and uses the gcc frontends.
But I doubt that it will compily a kernel correctly ...

Christoph

-- 
Always remember that you are unique.  Just like everyone else.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: makefile bash2 typo (Re: We interrupt you regularly scheduled catfight for.. Linux 2.2.18pre13)

[Tim Waugh]

On Mon, Oct 02, 2000 at 07:47:54AM -0700, Clayton Weaver wrote:

> What is the second "fi" for?

The first "if".

Tim.
*/

 PGP signature

Re: We interrupt you regularly scheduled catfight for.. Linux 2.2.18pre13

[Pavel Machek]

Hi!

> > Where does the idea that the kernel 'needs' a special compiler 
> > come from ?  I have been under the impression that that is just
> 
> Mostly from the sad fact that it does.
> 
> > what we were trying to get away from .  I am reminded of other
> > os's that required their propritary compiler in order to create
> > a os image .  Please let us not travel that road .  Tia ,  JimL
> 
> Patches are welcome. But keep in mind that we _are_ dependent on a
> particular compiler. gcc, that is. I would be glad to get rid of it - the
> codebase is extremely messy. However, removing gcc-isms is a huge
> work. You are welcome to do it, indeed, but so far nobody had done that.

Actually there's another compiler (codepro or how is it called), made
by SGI(?) for merced, available under gpl, and hving all gcc
extensions, including __asm__().
Pavel
-- 
The best software in life is free (not shareware)!  Pavel
GCM d? s-: !g p?:+ au- a--@ w+ v- C++@ UL+++ L++ N++ E++ W--- M- Y- R+
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

makefile bash2 typo (Re: We interrupt you regularly scheduled catfight for.. Linux 2.2.18pre13)

[Clayton Weaver]

   
> []   
> Another problem in Makefile. I guess this change between pre 12 and 13
> is a typo:

>  CONFIG_SHELL := $(shell if [ -x "$$BASH" ]; then echo $$BASH; \
>  - else if [ -x /bin/bash ]; then echo /bin/bash; \
>  + else if [ -x /bin/bash ]; then echo /bin/bash2; \
>else echo sh; fi ; fi)
> []   
   

What is the second "fi" for?

Regards,

Clayton Weaver

(Seattle)

"Everybody's ignorant, just in different subjects."  Will Rogers



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

makefile bash2 typo (Re: We interrupt you regularly scheduled catfight for.. Linux 2.2.18pre13)

[Clayton Weaver]

   
 []   
 Another problem in Makefile. I guess this change between pre 12 and 13
 is a typo:

  CONFIG_SHELL := $(shell if [ -x "$$BASH" ]; then echo $$BASH; \
  - else if [ -x /bin/bash ]; then echo /bin/bash; \
  + else if [ -x /bin/bash ]; then echo /bin/bash2; \
else echo sh; fi ; fi)
 []   
   

What is the second "fi" for?

Regards,

Clayton Weaver
mailto:[EMAIL PROTECTED]
(Seattle)

"Everybody's ignorant, just in different subjects."  Will Rogers



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: We interrupt you regularly scheduled catfight for.. Linux 2.2.18pre13

[Pavel Machek]

Hi!

  Where does the idea that the kernel 'needs' a special compiler 
  come from ?  I have been under the impression that that is just
 
 Mostly from the sad fact that it does.
 
  what we were trying to get away from .  I am reminded of other
  os's that required their propritary compiler in order to create
  a os image .  Please let us not travel that road .  Tia ,  JimL
 
 Patches are welcome. But keep in mind that we _are_ dependent on a
 particular compiler. gcc, that is. I would be glad to get rid of it - the
 codebase is extremely messy. However, removing gcc-isms is a huge
 work. You are welcome to do it, indeed, but so far nobody had done that.

Actually there's another compiler (codepro or how is it called), made
by SGI(?) for merced, available under gpl, and hving all gcc
extensions, including __asm__().
Pavel
-- 
The best software in life is free (not shareware)!  Pavel
GCM d? s-: !g p?:+ au- a--@ w+ v- C++@ UL+++ L++ N++ E++ W--- M- Y- R+
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: makefile bash2 typo (Re: We interrupt you regularly scheduled catfight for.. Linux 2.2.18pre13)

[Tim Waugh]

On Mon, Oct 02, 2000 at 07:47:54AM -0700, Clayton Weaver wrote:

 What is the second "fi" for?

The first "if".

Tim.
*/

 PGP signature

Re: We interrupt you regularly scheduled catfight for.. Linux 2.2.18pre13

[Christoph Hellwig]

On Mon, Oct 02, 2000 at 05:17:46PM +0200, Pavel Machek wrote:
 Actually there's another compiler (codepro or how is it called), made
 by SGI(?) for merced, available under gpl, and hving all gcc
 extensions, including __asm__().

SGI Pro64 - it's IA64 only and uses the gcc frontends.
But I doubt that it will compily a kernel correctly ...

Christoph

-- 
Always remember that you are unique.  Just like everyone else.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: makefile bash2 typo (Re: We interrupt you regularly scheduled catfight for.. Linux 2.2.18pre13)

[Andreas Schwab]

Tim Waugh [EMAIL PROTECTED] writes:

| On Mon, Oct 02, 2000 at 07:47:54AM -0700, Clayton Weaver wrote:
| 
|  What is the second "fi" for?
| 
| The first "if".

Btw, the Bourne language also has `elif':

  CONFIG_SHELL := $(shell if [ -x "$$BASH" ]; then echo $$BASH; \
elif [ -x /bin/bash ]; then echo /bin/bash; \
else echo sh; fi)

Andreas.

-- 
Andreas Schwab  "And now for something
SuSE Labscompletely different."
[EMAIL PROTECTED]
SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: We interrupt you regularly scheduled catfight for.. Linux 2.2.18pre13

[Petri Kaukasoina]

On Sun, Oct 01, 2000 at 01:01:34AM +0100, Alan Cox wrote:
> I've dropped Miquel's version into my tree. He simply side steps the entire
> 'which which' issue and uses scripts/kwhich

Peter Samuelson's version worked in my Slackware systems. Miquel's kwhich is
ok too.

Another problem in Makefile. I guess this change between pre 12 and 13 is a
typo:

 CONFIG_SHELL := $(shell if [ -x "$$BASH" ]; then echo $$BASH; \
- else if [ -x /bin/bash ]; then echo /bin/bash; \
+ else if [ -x /bin/bash ]; then echo /bin/bash2; \
  else echo sh; fi ; fi)

I have ash as /bin/sh and there's also /bin/bash but no /bin/bash2.

$ make oldconfig
Syntax error: "(" unexpected (expecting "then")
rm -f include/asm
( cd include ; ln -sf asm-i386 asm)
/bin/bash2 scripts/Configure -d arch/i386/config.in
make: /bin/bash2: Command not found
make: *** [oldconfig] Error 127
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: We interrupt you regularly scheduled catfight for.. Linux 2.2.18pre13

[Jeff Garzik]

On Sat, 30 Sep 2000, Alexander Viro wrote:
> Patches are welcome. But keep in mind that we _are_ dependent on a
> particular compiler. gcc, that is. I would be glad to get rid of it - the
> codebase is extremely messy. However, removing gcc-isms is a huge
> work. You are welcome to do it, indeed, but so far nobody had done that.

Ug.  Have you seen the ISO version of "field: value" struct initializers?

gcc all the way, bay-bee :)

Jeff



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: We interrupt you regularly scheduled catfight for.. Linux 2.2.18pre13

[Olivier Galibert]

On Sat, Sep 30, 2000 at 11:29:13PM +0100, Alan Cox wrote:
> If you get
> a link error or a module load error about bad_udelay let me know.

insmod pcmcia_core.o from pcmcia 3.1.20 gets the T-shirt.

  OG.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: We interrupt you regularly scheduled catfight for.. Linux 2.2.18pre13

[Olivier Galibert]

On Sat, Sep 30, 2000 at 11:29:13PM +0100, Alan Cox wrote:
 If you get
 a link error or a module load error about bad_udelay let me know.

insmod pcmcia_core.o from pcmcia 3.1.20 gets the T-shirt.

  OG.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: We interrupt you regularly scheduled catfight for.. Linux 2.2.18pre13

[Jeff Garzik]

On Sat, 30 Sep 2000, Alexander Viro wrote:
 Patches are welcome. But keep in mind that we _are_ dependent on a
 particular compiler. gcc, that is. I would be glad to get rid of it - the
 codebase is extremely messy. However, removing gcc-isms is a huge
 work. You are welcome to do it, indeed, but so far nobody had done that.

Ug.  Have you seen the ISO version of "field: value" struct initializers?

gcc all the way, bay-bee :)

Jeff



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: We interrupt you regularly scheduled catfight for.. Linux 2.2.18pre13

[Petri Kaukasoina]

On Sun, Oct 01, 2000 at 01:01:34AM +0100, Alan Cox wrote:
 I've dropped Miquel's version into my tree. He simply side steps the entire
 'which which' issue and uses scripts/kwhich

Peter Samuelson's version worked in my Slackware systems. Miquel's kwhich is
ok too.

Another problem in Makefile. I guess this change between pre 12 and 13 is a
typo:

 CONFIG_SHELL := $(shell if [ -x "$$BASH" ]; then echo $$BASH; \
- else if [ -x /bin/bash ]; then echo /bin/bash; \
+ else if [ -x /bin/bash ]; then echo /bin/bash2; \
  else echo sh; fi ; fi)

I have ash as /bin/sh and there's also /bin/bash but no /bin/bash2.

$ make oldconfig
Syntax error: "(" unexpected (expecting "then")
rm -f include/asm
( cd include ; ln -sf asm-i386 asm)
/bin/bash2 scripts/Configure -d arch/i386/config.in
make: /bin/bash2: Command not found
make: *** [oldconfig] Error 127
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: We interrupt you regularly scheduled catfight for.. Linux 2.2.18pre13

[Mitch Adair]

Compile bombs out in bridging:

br.c: In function `brg_probe':
br.c:2458: `loops_per_sec' undeclared (first use in this function)
br.c:2458: (Each undeclared identifier is reported only once
br.c:2458: for each function it appears in.)
br.c:2442: warning: `bogomips' might be used uninitialized in this function
br.c: At top level:
br.c:165: warning: `br_get_ifnames' declared `static' but never defined
make[3]: *** [br.o] Error 1
make[2]: *** [first_rule] Error 2
make[1]: *** [_subdir_bridge] Error 2
make: *** [_dir_net] Error 2


In the style of the other loops_per_sec->loops_per_jiffy changes this makes
it compile (not booted, yet...)

--- net/bridge/br.c~Sun Sep 10 11:38:46 2000
+++ net/bridge/br.c Sun Oct  1 00:26:26 2000
@@ -2455,7 +2455,7 @@
 
/* Set up MAC address based on BogoMIPs figure for first CPU and time
 */ 
-   bogomips = (loops_per_sec+2500)/50 ;
+   bogomips = (loops_per_jiffy+2500)/(50/HZ);
get_fast_time();
 
/* U  YES! */


M
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: We interrupt you regularly scheduled catfight for.. Linux 2.2.18pre13

[Horst von Brand]

Alexander Viro <[EMAIL PROTECTED]> said:

[...]

> Patches are welcome. But keep in mind that we _are_ dependent on a
> particular compiler. gcc, that is. I would be glad to get rid of it - the
> codebase is extremely messy. However, removing gcc-isms is a huge
> work. You are welcome to do it, indeed, but so far nobody had done that.

Is there any _real_ gcc alternative in sight?

Just wondering...
-- 
Horst von Brand [EMAIL PROTECTED]
Casilla 9G, Vin~a del Mar, Chile   +56 32 672616
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: We interrupt you regularly scheduled catfight for.. Linux 2.2.18pre13

[Peter Samuelson]

[Christoph Hellwig]
> If you are using a distribution that ships with a default C compiler
> that is not able to compile linux kernel, use make CC=kgcc (redhat)
> or CC=gcc272 (debian) instead.

That works for >= 2.3.30 or so.  For 2.2 it's more like

  make CC="kgcc -D__KERNEL__ -I`pwd`/include"

which is really too much to tell people to do.  Most people would
probably rather just edit the makefile.

Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: We interrupt you regularly scheduled catfight for.. Linux 2.2.18pre13

[Alan Cox]

> > Isn't this completely broken? I mean, it wont detect the others at all. It
> > will leave CC="" if gcc272 or kgcc are there.
> 
> Yes. Sorry I' too selfish today ;) Your version seems more accurate to me.

I've dropped Miquel's version into my tree. He simply side steps the entire
'which which' issue and uses scripts/kwhich

Alan

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: We interrupt you regularly scheduled catfight for.. Linux 2.2.18pre13

[Christoph Hellwig]

Ben Collins <[EMAIL PROTECTED]> wrote:
> Isn't this completely broken? I mean, it wont detect the others at all. It
> will leave CC="" if gcc272 or kgcc are there.

Yes. Sorry I' too selfish today ;) Your version seems more accurate to me.

Christoph

-- 
Always remember that you are unique.  Just like everyone else.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: We interrupt you regularly scheduled catfight for.. Linux 2.2.18pre13

[Christoph Hellwig]

On Sat, Sep 30, 2000 at 07:30:42PM -0400, Alexander Viro wrote:
> Forget distributions. There is a very, very good reason to have the choice
> of cc used in kernel builds uncoupled from the userland one. IMO kgcc is a
> misnomer (kcc would be better), but the idea is sound - you don't want to
> deal with the miscompiled kernel while you are porting the userland to
> another version of compiler. You also don't want it once you've are done
> with the userland stuff - level of dependency on gcc details is much
> higher in case of the kernel.

I have no problem with that although I didn't think about it yet.
What I disklike is having magic in the Makefile to find the right compiler.
Probably we could just put CC=kcc in the Makefile and everyone would
have to arrange it right.
(This is also a good way to make the newbies the documentation ;))

Christoph

-- 
Always remember that you are unique.  Just like everyone else.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: We interrupt you regularly scheduled catfight for.. Linux 2.2.18pre13

[Ben Collins]

> - snip -
> 
> --- Makefile~ Sun Oct  1 00:46:27 2000
> +++ Makefile  Sun Oct  1 00:49:27 2000
> @@ -23,7 +23,7 @@
>  AS   =$(CROSS_COMPILE)as
>  LD   =$(CROSS_COMPILE)ld
>  CC   =$(shell if [ -n "$(CROSS_COMPILE)" ]; then echo $(CROSS_COMPILE)cc; else \
> - which gcc272 2>/dev/null || which kgcc 2>/dev/null || echo cc; fi) \
> + which gcc272 >/dev/null 2>/dev/null || which kgcc > /dev/null 2>/dev/null || 
>echo cc; fi) \
>   -D__KERNEL__ -I$(HPATH)
>  #CC  =$(CROSS_COMPILE)cc -D__KERNEL__ -I$(HPATH)
>  CPP  =$(CC) -E
> - snip -

Isn't this completely broken? I mean, it wont detect the others at all. It
will leave CC="" if gcc272 or kgcc are there.

How about:

CC =$(shell if [ -n "$(CROSS_COMPILE)" ]; then echo $(CROSS_COMPILE)cc; else \
if which gcc272 > /dev/null 2> /dev/null; then \
which gcc272; \
else \
if which kgcc > /dev/null 2> /dev/null; then \
which kgcc; \
else \
echo cc; \
fi; \
fi) -D__KERNEL__ -I$(HPATH)

(obscure as needed)

-- 
 ---===-=-==-=---==-=--
/  Ben Collins  --  ...on that fantastic voyage...  --  Debian GNU/Linux   \
`  [EMAIL PROTECTED]  --  [EMAIL PROTECTED]  --  [EMAIL PROTECTED]  '
 `---=--===-=-=-=-===-==---=--=---'
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: We interrupt you regularly scheduled catfight for.. Linux 2.2.18pre13

[Alan Cox]

> I personally dislike the 'autmatically detect kgcc and gcc272' patches a lot,
> and I think we should put a sentence like
> 
> If you are using a distribution that ships with a default C compiler that is
> not able to compile linux kernel, use make CC=kgcc (redhat) or CC=gcc272
> (debian) instead.

kgcc is also conectiva but maybe

You are under the delusion that people read the README file ?

I'd like to get a solution to this. If I can get one that works everywhere
then its README file time yes. Herbert Xu posted a fairly sane looking
approach

Alan

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: We interrupt you regularly scheduled catfight for.. Linux 2.2.18pre13

[Christoph Hellwig]

> o Fix the 'which' compiler stuff  (Horst von Brand,
>Peter Samuelson)
>   | Can someone verify for me this works on Slackware and
>   | on Caldera ?

It breaks on Caldera.
The errors are:

-- snip -
bin/sh: syntax error near unexpected token `(/'
/bin/sh: -c: line 1: `if which: no gcc272 in 
(/bin:/usr/bin:/usr/sbin:/sbin:/home/lstguest/hch/bin)
which: no kgcc in (/bin:/usr/bin:/usr/sbin:/sbin:/home/lstguest/hch/bin) cc 
-D__KERNEL__
-I/home.stand/lstguest/hch/linux/include -fno-strict-aliasing -S -o /dev/null -xc 
/dev/null >/dev/null
2>&1; then echo "-fno-strict-aliasing"; fi'
(/bin:/usr/bin:/usr/sbin:/sbin:/home/lstguest/hch/bin) cc -D__KERNEL__
-I/home.stand/lstguest/hch/linux/include -Wall -Wstrict-prototypes -O2 
-fomit-frame-pointer  -D__SMP__
-pipe -fno-strength-reduce -m486 -malign-loops=2 -malign-jumps=2 -malign-functions=2 
-DCPU=686 -v 2>&1
-- snip -

The problem is that the which output is not ignored.
The following patch fixes it:

- snip -

--- Makefile~   Sun Oct  1 00:46:27 2000
+++ MakefileSun Oct  1 00:49:27 2000
@@ -23,7 +23,7 @@
 AS =$(CROSS_COMPILE)as
 LD =$(CROSS_COMPILE)ld
 CC =$(shell if [ -n "$(CROSS_COMPILE)" ]; then echo $(CROSS_COMPILE)cc; else \
-   which gcc272 2>/dev/null || which kgcc 2>/dev/null || echo cc; fi) \
+   which gcc272 >/dev/null 2>/dev/null || which kgcc > /dev/null 2>/dev/null || 
+echo cc; fi) \
-D__KERNEL__ -I$(HPATH)
 #CC=$(CROSS_COMPILE)cc -D__KERNEL__ -I$(HPATH)
 CPP=$(CC) -E
- snip -

I personally dislike the 'autmatically detect kgcc and gcc272' patches a lot,
and I think we should put a sentence like

If you are using a distribution that ships with a default C compiler that is
not able to compile linux kernel, use make CC=kgcc (redhat) or CC=gcc272
(debian) instead.

into README, instead of fiddling around with a command/program with lots of
different and incompatible versions.

Christoph

-- 
Always remember that you are unique.  Just like everyone else.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

We interrupt you regularly scheduled catfight for.. Linux 2.2.18pre13

[Alan Cox]

Bug squash number one. This should fix the 'it doesnt compile at all' bug.
The other change here is that support for faster processors, that will catch
out anyone using (abusing) udelay with extremely large values. If you get
a link error or a module load error about bad_udelay let me know.

Everything but x86 is probably in need of some small fixing by the port
maintainers. 

Alan

Stuff left to do for 2.2.18final
-   Support for >2GHz processors
-   Merge the S/390 stuff and make S/390 build again
-   Hunt bugs in the stuff so far.
-   Fix the megaraid (revert if need be)

The S/390 stuff shouldnt touch the mainstream so from hereon in its simply
a case of squashing bugs as they pop out until its ready to be 2.2.18.

2.2.18pre13
o   Change udelay to use loops_per tick (Philipp Rumpf)
| Otherwise we bomb out at 2GHz which isnt far enough
| away with 1.4/1.6GHz stuff due out RSN
o   Fix drivers using big delays to use mdelay  (me)
o   Fix drivers that used loops_per_sec (Philipp Rumpf, me)
o   Fix yamaha PCI sound SMP bug(Arjan van de Ven)
o   Change to preferred USB init fix(David Rees)
o   Fix rio fix (Arjan van de Ven)
o   Catch the VT but no mouse case in init/main.c   (Arjan van de Ven)
o   Fix the 'which' compiler stuff  (Horst von Brand,
 Peter Samuelson)
| Can someone verify for me this works on Slackware and
| on Caldera ?
o   Add devfs include. Devfs wont be going into 2.2 (Richard Gooch)
but this again makes it easier to do 2.2/2.4
drivers.

2.2.18pre12
o   Fix cyrix MTRR handling bug (IIZUKA Daisuke)
o   Fix ymfpci poll (me, Arjan)
o   Update radio-maestro, add Configure.help(Adam Tla/lka>
o   Fix rio/generic serial build bug(Marcelo Tossati)
o   USB build bug fix   (Arjan van de Ven)
o   Fix missing ac97_codec.c return value   (Arjan van de Ven)
o   Fix several warnings(Arjan van de Ven)
o   Made the PS/2 reconnect behaviour optional  (me)
| Its now 'psaux-reconnect' on the boot line
o   Allow for newer Hauppauge with 4 ports  (Krischan Jodies)
o   Switch sound drivers from library to object (Arjan van de Ven)
o   Kill the not working ac97 lock on the 810   (me)
o   Automatically select older compilers for kernel
builds on Debian and RH (Arjan van de Ven)
o   Start volumes higher on ac97, teach the driver  (Rui Sousa)
about 5bit and 6bit codec precision and use
the mute bit.

2.2.18pre11
o   Kill bogus codec_id assignment  (Linus Torvalds)
o   Update codec init code to handle id right   (me)
o   Fix dead/clashing define for NFS(Trond Myklebust)
o   Remove the find_vga crap from bttv  (me)
o   Fix return on probe failure for cadet   (Arjan van de Ven)
o   Add missing configure.help stuff from 2.4test   (Alan Ford)
o   Fix inia100/megaraid define clash   (Arjan van de Ven)
o   __xchg marked as taking volatiles   (Arjan van de Ven)
o   Fix vwsnd warning in sound core (Arjan van de Ven)
o   wdt_pci driver should return -EIO on error  (Arjan van de Ven)
o   Fix init_adfs_fs warning(Arjan van de Ven)
o   Fix the joystick driver option parsing  (Arjan van de Ven)
o   Update mkdep to handle // commenting(Mike Klar)
o   Thunderlan driver typo fixes(Torben Mathiasen)
o   Add KX133/KT133 stuff to the AGP/DRM(Jeff Nguyen)
o   FIx multiple card bug in eepro driver   (Aristeu Filho)
o   Initial YMF PCI native driver   (Pete Zaitcev)
| Based on Jaroslav's ALSA driver and I've tweaked it
| a bit and maybe broken it 8)
o   Fix procfs unlink bugs  (Willy Tarreau)
o   X.25 bugfix backport(Henner Eisen)
o   Fix incorrect free_dma on DMAless boxes (Boria)
o   Fix via audio driver merge  (Nick Lamb)
o   Update plusb driver to 2.4 one  (Greg Kroah-Hartman)
o   Put description info in wacom driver(Greg Kroah-Hartman)
o   Update both UHCI drivers to match 2.4test   (Greg Kroah-Hartman)
o   Masquerade cleanup/warning fixes(Horst von Brand)

2.2.18pre10
o   Add printk level to partition printk messages   (me)
o   Fix bluesmoke address report/serialize  (Andrea Arcangeli)
o   Add 2.4pre CPUID/MSR docs to 2.2.18pre  (Adrian 

We interrupt you regularly scheduled catfight for.. Linux 2.2.18pre13

[Alan Cox]

Bug squash number one. This should fix the 'it doesnt compile at all' bug.
The other change here is that support for faster processors, that will catch
out anyone using (abusing) udelay with extremely large values. If you get
a link error or a module load error about bad_udelay let me know.

Everything but x86 is probably in need of some small fixing by the port
maintainers. 

Alan

Stuff left to do for 2.2.18final
-   Support for 2GHz processors
-   Merge the S/390 stuff and make S/390 build again
-   Hunt bugs in the stuff so far.
-   Fix the megaraid (revert if need be)

The S/390 stuff shouldnt touch the mainstream so from hereon in its simply
a case of squashing bugs as they pop out until its ready to be 2.2.18.

2.2.18pre13
o   Change udelay to use loops_per tick (Philipp Rumpf)
| Otherwise we bomb out at 2GHz which isnt far enough
| away with 1.4/1.6GHz stuff due out RSN
o   Fix drivers using big delays to use mdelay  (me)
o   Fix drivers that used loops_per_sec (Philipp Rumpf, me)
o   Fix yamaha PCI sound SMP bug(Arjan van de Ven)
o   Change to preferred USB init fix(David Rees)
o   Fix rio fix (Arjan van de Ven)
o   Catch the VT but no mouse case in init/main.c   (Arjan van de Ven)
o   Fix the 'which' compiler stuff  (Horst von Brand,
 Peter Samuelson)
| Can someone verify for me this works on Slackware and
| on Caldera ?
o   Add devfs include. Devfs wont be going into 2.2 (Richard Gooch)
but this again makes it easier to do 2.2/2.4
drivers.

2.2.18pre12
o   Fix cyrix MTRR handling bug (IIZUKA Daisuke)
o   Fix ymfpci poll (me, Arjan)
o   Update radio-maestro, add Configure.help(Adam Tla/lka
o   Fix rio/generic serial build bug(Marcelo Tossati)
o   USB build bug fix   (Arjan van de Ven)
o   Fix missing ac97_codec.c return value   (Arjan van de Ven)
o   Fix several warnings(Arjan van de Ven)
o   Made the PS/2 reconnect behaviour optional  (me)
| Its now 'psaux-reconnect' on the boot line
o   Allow for newer Hauppauge with 4 ports  (Krischan Jodies)
o   Switch sound drivers from library to object (Arjan van de Ven)
o   Kill the not working ac97 lock on the 810   (me)
o   Automatically select older compilers for kernel
builds on Debian and RH (Arjan van de Ven)
o   Start volumes higher on ac97, teach the driver  (Rui Sousa)
about 5bit and 6bit codec precision and use
the mute bit.

2.2.18pre11
o   Kill bogus codec_id assignment  (Linus Torvalds)
o   Update codec init code to handle id right   (me)
o   Fix dead/clashing define for NFS(Trond Myklebust)
o   Remove the find_vga crap from bttv  (me)
o   Fix return on probe failure for cadet   (Arjan van de Ven)
o   Add missing configure.help stuff from 2.4test   (Alan Ford)
o   Fix inia100/megaraid define clash   (Arjan van de Ven)
o   __xchg marked as taking volatiles   (Arjan van de Ven)
o   Fix vwsnd warning in sound core (Arjan van de Ven)
o   wdt_pci driver should return -EIO on error  (Arjan van de Ven)
o   Fix init_adfs_fs warning(Arjan van de Ven)
o   Fix the joystick driver option parsing  (Arjan van de Ven)
o   Update mkdep to handle // commenting(Mike Klar)
o   Thunderlan driver typo fixes(Torben Mathiasen)
o   Add KX133/KT133 stuff to the AGP/DRM(Jeff Nguyen)
o   FIx multiple card bug in eepro driver   (Aristeu Filho)
o   Initial YMF PCI native driver   (Pete Zaitcev)
| Based on Jaroslav's ALSA driver and I've tweaked it
| a bit and maybe broken it 8)
o   Fix procfs unlink bugs  (Willy Tarreau)
o   X.25 bugfix backport(Henner Eisen)
o   Fix incorrect free_dma on DMAless boxes (Boria)
o   Fix via audio driver merge  (Nick Lamb)
o   Update plusb driver to 2.4 one  (Greg Kroah-Hartman)
o   Put description info in wacom driver(Greg Kroah-Hartman)
o   Update both UHCI drivers to match 2.4test   (Greg Kroah-Hartman)
o   Masquerade cleanup/warning fixes(Horst von Brand)

2.2.18pre10
o   Add printk level to partition printk messages   (me)
o   Fix bluesmoke address report/serialize  (Andrea Arcangeli)
o   Add 2.4pre CPUID/MSR docs to 2.2.18pre  (Adrian 

Re: We interrupt you regularly scheduled catfight for.. Linux 2.2.18pre13

[Christoph Hellwig]

 o Fix the 'which' compiler stuff  (Horst von Brand,
Peter Samuelson)
   | Can someone verify for me this works on Slackware and
   | on Caldera ?

It breaks on Caldera.
The errors are:

-- snip -
bin/sh: syntax error near unexpected token `(/'
/bin/sh: -c: line 1: `if which: no gcc272 in 
(/bin:/usr/bin:/usr/sbin:/sbin:/home/lstguest/hch/bin)
which: no kgcc in (/bin:/usr/bin:/usr/sbin:/sbin:/home/lstguest/hch/bin) cc 
-D__KERNEL__
-I/home.stand/lstguest/hch/linux/include -fno-strict-aliasing -S -o /dev/null -xc 
/dev/null /dev/null
21; then echo "-fno-strict-aliasing"; fi'
(/bin:/usr/bin:/usr/sbin:/sbin:/home/lstguest/hch/bin) cc -D__KERNEL__
-I/home.stand/lstguest/hch/linux/include -Wall -Wstrict-prototypes -O2 
-fomit-frame-pointer  -D__SMP__
-pipe -fno-strength-reduce -m486 -malign-loops=2 -malign-jumps=2 -malign-functions=2 
-DCPU=686 -v 21
-- snip -

The problem is that the which output is not ignored.
The following patch fixes it:

- snip -

--- Makefile~   Sun Oct  1 00:46:27 2000
+++ MakefileSun Oct  1 00:49:27 2000
@@ -23,7 +23,7 @@
 AS =$(CROSS_COMPILE)as
 LD =$(CROSS_COMPILE)ld
 CC =$(shell if [ -n "$(CROSS_COMPILE)" ]; then echo $(CROSS_COMPILE)cc; else \
-   which gcc272 2/dev/null || which kgcc 2/dev/null || echo cc; fi) \
+   which gcc272 /dev/null 2/dev/null || which kgcc  /dev/null 2/dev/null || 
+echo cc; fi) \
-D__KERNEL__ -I$(HPATH)
 #CC=$(CROSS_COMPILE)cc -D__KERNEL__ -I$(HPATH)
 CPP=$(CC) -E
- snip -

I personally dislike the 'autmatically detect kgcc and gcc272' patches a lot,
and I think we should put a sentence like

If you are using a distribution that ships with a default C compiler that is
not able to compile linux kernel, use make CC=kgcc (redhat) or CC=gcc272
(debian) instead.

into README, instead of fiddling around with a command/program with lots of
different and incompatible versions.

Christoph

-- 
Always remember that you are unique.  Just like everyone else.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: We interrupt you regularly scheduled catfight for.. Linux 2.2.18pre13

[Alan Cox]

 I personally dislike the 'autmatically detect kgcc and gcc272' patches a lot,
 and I think we should put a sentence like
 
 If you are using a distribution that ships with a default C compiler that is
 not able to compile linux kernel, use make CC=kgcc (redhat) or CC=gcc272
 (debian) instead.

kgcc is also conectiva but maybe

You are under the delusion that people read the README file ?

I'd like to get a solution to this. If I can get one that works everywhere
then its README file time yes. Herbert Xu posted a fairly sane looking
approach

Alan

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: We interrupt you regularly scheduled catfight for.. Linux 2.2.18pre13

[Ben Collins]

 - snip -
 
 --- Makefile~ Sun Oct  1 00:46:27 2000
 +++ Makefile  Sun Oct  1 00:49:27 2000
 @@ -23,7 +23,7 @@
  AS   =$(CROSS_COMPILE)as
  LD   =$(CROSS_COMPILE)ld
  CC   =$(shell if [ -n "$(CROSS_COMPILE)" ]; then echo $(CROSS_COMPILE)cc; else \
 - which gcc272 2/dev/null || which kgcc 2/dev/null || echo cc; fi) \
 + which gcc272 /dev/null 2/dev/null || which kgcc  /dev/null 2/dev/null || 
echo cc; fi) \
   -D__KERNEL__ -I$(HPATH)
  #CC  =$(CROSS_COMPILE)cc -D__KERNEL__ -I$(HPATH)
  CPP  =$(CC) -E
 - snip -

Isn't this completely broken? I mean, it wont detect the others at all. It
will leave CC="" if gcc272 or kgcc are there.

How about:

CC =$(shell if [ -n "$(CROSS_COMPILE)" ]; then echo $(CROSS_COMPILE)cc; else \
if which gcc272  /dev/null 2 /dev/null; then \
which gcc272; \
else \
if which kgcc  /dev/null 2 /dev/null; then \
which kgcc; \
else \
echo cc; \
fi; \
fi) -D__KERNEL__ -I$(HPATH)

(obscure as needed)

-- 
 ---===-=-==-=---==-=--
/  Ben Collins  --  ...on that fantastic voyage...  --  Debian GNU/Linux   \
`  [EMAIL PROTECTED]  --  [EMAIL PROTECTED]  --  [EMAIL PROTECTED]  '
 `---=--===-=-=-=-===-==---=--=---'
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: We interrupt you regularly scheduled catfight for.. Linux 2.2.18pre13

[Christoph Hellwig]

On Sat, Sep 30, 2000 at 07:30:42PM -0400, Alexander Viro wrote:
 Forget distributions. There is a very, very good reason to have the choice
 of cc used in kernel builds uncoupled from the userland one. IMO kgcc is a
 misnomer (kcc would be better), but the idea is sound - you don't want to
 deal with the miscompiled kernel while you are porting the userland to
 another version of compiler. You also don't want it once you've are done
 with the userland stuff - level of dependency on gcc details is much
 higher in case of the kernel.

I have no problem with that although I didn't think about it yet.
What I disklike is having magic in the Makefile to find the right compiler.
Probably we could just put CC=kcc in the Makefile and everyone would
have to arrange it right.
(This is also a good way to make the newbies the documentation ;))

Christoph

-- 
Always remember that you are unique.  Just like everyone else.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: We interrupt you regularly scheduled catfight for.. Linux 2.2.18pre13

[Christoph Hellwig]

Ben Collins [EMAIL PROTECTED] wrote:
 Isn't this completely broken? I mean, it wont detect the others at all. It
 will leave CC="" if gcc272 or kgcc are there.

Yes. Sorry I' too selfish today ;) Your version seems more accurate to me.

Christoph

-- 
Always remember that you are unique.  Just like everyone else.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: We interrupt you regularly scheduled catfight for.. Linux 2.2.18pre13

[Alan Cox]

  Isn't this completely broken? I mean, it wont detect the others at all. It
  will leave CC="" if gcc272 or kgcc are there.
 
 Yes. Sorry I' too selfish today ;) Your version seems more accurate to me.

I've dropped Miquel's version into my tree. He simply side steps the entire
'which which' issue and uses scripts/kwhich

Alan

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: We interrupt you regularly scheduled catfight for.. Linux 2.2.18pre13

[Peter Samuelson]

[Christoph Hellwig]
 If you are using a distribution that ships with a default C compiler
 that is not able to compile linux kernel, use make CC=kgcc (redhat)
 or CC=gcc272 (debian) instead.

That works for = 2.3.30 or so.  For 2.2 it's more like

  make CC="kgcc -D__KERNEL__ -I`pwd`/include"

which is really too much to tell people to do.  Most people would
probably rather just edit the makefile.

Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: We interrupt you regularly scheduled catfight for.. Linux 2.2.18pre13

[Horst von Brand]

Alexander Viro [EMAIL PROTECTED] said:

[...]

 Patches are welcome. But keep in mind that we _are_ dependent on a
 particular compiler. gcc, that is. I would be glad to get rid of it - the
 codebase is extremely messy. However, removing gcc-isms is a huge
 work. You are welcome to do it, indeed, but so far nobody had done that.

Is there any _real_ gcc alternative in sight?

Just wondering...
-- 
Horst von Brand [EMAIL PROTECTED]
Casilla 9G, Vin~a del Mar, Chile   +56 32 672616
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: We interrupt you regularly scheduled catfight for.. Linux 2.2.18pre13

[Mitch Adair]

Compile bombs out in bridging:

br.c: In function `brg_probe':
br.c:2458: `loops_per_sec' undeclared (first use in this function)
br.c:2458: (Each undeclared identifier is reported only once
br.c:2458: for each function it appears in.)
br.c:2442: warning: `bogomips' might be used uninitialized in this function
br.c: At top level:
br.c:165: warning: `br_get_ifnames' declared `static' but never defined
make[3]: *** [br.o] Error 1
make[2]: *** [first_rule] Error 2
make[1]: *** [_subdir_bridge] Error 2
make: *** [_dir_net] Error 2


In the style of the other loops_per_sec-loops_per_jiffy changes this makes
it compile (not booted, yet...)

--- net/bridge/br.c~Sun Sep 10 11:38:46 2000
+++ net/bridge/br.c Sun Oct  1 00:26:26 2000
@@ -2455,7 +2455,7 @@
 
/* Set up MAC address based on BogoMIPs figure for first CPU and time
 */ 
-   bogomips = (loops_per_sec+2500)/50 ;
+   bogomips = (loops_per_jiffy+2500)/(50/HZ);
get_fast_time(utime);
 
/* U  YES! */


M
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/