All of lore.kernel.org
 help / color / mirror / Atom feed
* make in 2.6.x
@ 2004-01-23 14:50 Karel Kulhavý
  2004-01-23 15:11 ` Bas Mevissen
                   ` (3 more replies)
  0 siblings, 4 replies; 20+ messages in thread
From: Karel Kulhavý @ 2004-01-23 14:50 UTC (permalink / raw)
  To: linux-kernel

Hello

Is it correct to issue "make bzImage modules modules_install"
or do I have to do make bzImage; make modules modules_install?

Is there any documentation where I can read answer to this question?

Cl<

^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: make in 2.6.x
  2004-01-23 14:50 make in 2.6.x Karel Kulhavý
@ 2004-01-23 15:11 ` Bas Mevissen
       [not found] ` <20040123100035.73bee41f.jeremy@kerneltrap.org>
                   ` (2 subsequent siblings)
  3 siblings, 0 replies; 20+ messages in thread
From: Bas Mevissen @ 2004-01-23 15:11 UTC (permalink / raw)
  To: Karel Kulhavý; +Cc: linux-kernel

Karel Kulhavý wrote:
> Hello
> 
> Is it correct to issue "make bzImage modules modules_install"
> or do I have to do make bzImage; make modules modules_install?

# make all modules_install install

Builds image and modules and installs them both. At least on Redhat, 
also an initial ram disk is created and grub is adapted.

> Is there any documentation where I can read answer to this question?
> 

# make help

and read the top-level Makefile itself. It is a quite readable file format.

Regards,

Bas.


^ permalink raw reply	[flat|nested] 20+ messages in thread

* gcc 2.95.3
       [not found] ` <20040123100035.73bee41f.jeremy@kerneltrap.org>
@ 2004-01-23 15:13   ` Karel Kulhavý
  2004-01-23 16:03     ` Daniel Andersen
                       ` (3 more replies)
  2004-01-23 15:20   ` make in 2.6.x Karel Kulhavý
  1 sibling, 4 replies; 20+ messages in thread
From: Karel Kulhavý @ 2004-01-23 15:13 UTC (permalink / raw)
  To: linux-kernel

On Fri, Jan 23, 2004 at 10:00:35AM -0500, Jeremy Andrews wrote:
> > Is it correct to issue "make bzImage modules modules_install"
> > or do I have to do make bzImage; make modules modules_install?
> > 
> > Is there any documentation where I can read answer to this question?
> 
> make help

Cool. I got to README :)

I read here "make sure you have gcc 2.95.3 available" - does it mean
my gcc-3.2.3 or gcc-3.2.2 is not suitable for kernel compiling?

Cl<

^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: make in 2.6.x
  2004-01-23 14:50 make in 2.6.x Karel Kulhavý
  2004-01-23 15:11 ` Bas Mevissen
       [not found] ` <20040123100035.73bee41f.jeremy@kerneltrap.org>
@ 2004-01-23 15:20 ` Sam Ravnborg
  2004-01-23 15:39   ` David Woodhouse
  2004-01-23 17:42 ` Wakko Warner
  3 siblings, 1 reply; 20+ messages in thread
From: Sam Ravnborg @ 2004-01-23 15:20 UTC (permalink / raw)
  To: Karel Kulhavý; +Cc: linux-kernel

On Fri, Jan 23, 2004 at 02:50:48PM +0000, Karel Kulhavý wrote:
> Hello
> 
> Is it correct to issue "make bzImage modules modules_install"
> or do I have to do make bzImage; make modules modules_install?

It is today supported that you specify all targets in one line.
The preferred way to do this is to use:

make all modules_install

'all' will build bot default target and modules - and works across
all architectures.

> Is there any documentation where I can read answer to this question?

No, the top-level README could have included this, but does not so today.

	Sam

^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: make in 2.6.x
       [not found] ` <20040123100035.73bee41f.jeremy@kerneltrap.org>
  2004-01-23 15:13   ` gcc 2.95.3 Karel Kulhavý
@ 2004-01-23 15:20   ` Karel Kulhavý
  1 sibling, 0 replies; 20+ messages in thread
From: Karel Kulhavý @ 2004-01-23 15:20 UTC (permalink / raw)
  To: linux-kernel

On Fri, Jan 23, 2004 at 10:00:35AM -0500, Jeremy Andrews wrote:
> > Is it correct to issue "make bzImage modules modules_install"
> > or do I have to do make bzImage; make modules modules_install?
> > 
> > Is there any documentation where I can read answer to this question?
> 
> make help
> 
> Cheers,
>  -Jeremy

I have read make help and skimmed through README however what I learned is
that the sequence "make bzImage ; make modules ; make modules_install" is
correct, but found no approval or disapproval for
"make bzImage modules modules_install"

Cl<

^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: make in 2.6.x
  2004-01-23 15:20 ` Sam Ravnborg
@ 2004-01-23 15:39   ` David Woodhouse
  0 siblings, 0 replies; 20+ messages in thread
From: David Woodhouse @ 2004-01-23 15:39 UTC (permalink / raw)
  To: Sam Ravnborg; +Cc: Karel Kulhavý, linux-kernel

On Fri, 2004-01-23 at 16:20 +0100, Sam Ravnborg wrote:
> On Fri, Jan 23, 2004 at 02:50:48PM +0000, Karel Kulhavý wrote:
> > Hello
> > 
> > Is it correct to issue "make bzImage modules modules_install"
> > or do I have to do make bzImage; make modules modules_install?
> 
> It is today supported that you specify all targets in one line.

Last time I tried, there were bugs with 'make -j3 bzImage modules'. Is
that now fixed?

-- 
dwmw2


^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: gcc 2.95.3
  2004-01-23 15:13   ` gcc 2.95.3 Karel Kulhavý
@ 2004-01-23 16:03     ` Daniel Andersen
       [not found]     ` <001b01c3e1ca$26101f20$1e00000a@black>
                       ` (2 subsequent siblings)
  3 siblings, 0 replies; 20+ messages in thread
From: Daniel Andersen @ 2004-01-23 16:03 UTC (permalink / raw)
  To: Karel Kulhavý; +Cc: linux-kernel

> I read here "make sure you have gcc 2.95.3 available" - does it mean
> my gcc-3.2.3 or gcc-3.2.2 is not suitable for kernel compiling?

Please have a look at http://developer.osdl.org/cherry/compile/

It should work fine.

Daniel Andersen

^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: gcc 2.95.3
       [not found]     ` <001b01c3e1ca$26101f20$1e00000a@black>
@ 2004-01-23 16:30       ` Karel Kulhavý
  2004-01-23 18:33         ` Matthew Reppert
  0 siblings, 1 reply; 20+ messages in thread
From: Karel Kulhavý @ 2004-01-23 16:30 UTC (permalink / raw)
  To: Daniel Andersen; +Cc: linux-kernel

On Fri, Jan 23, 2004 at 05:01:23PM +0100, Daniel Andersen wrote:
> > I read here "make sure you have gcc 2.95.3 available" - does it mean
> > my gcc-3.2.3 or gcc-3.2.2 is not suitable for kernel compiling?
> 
> Please have a look at http://developer.osdl.org/cherry/compile/

What if the kernel compiles cleanly but the generated code is invalid?
Or is gcc-3.2.2 BugFree(TM) (BugFree as in BugFree speech, not as
in BugFree beer)?

Cl<

^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: make in 2.6.x
  2004-01-23 14:50 make in 2.6.x Karel Kulhavý
                   ` (2 preceding siblings ...)
  2004-01-23 15:20 ` Sam Ravnborg
@ 2004-01-23 17:42 ` Wakko Warner
  2004-01-23 20:32   ` Sam Ravnborg
  3 siblings, 1 reply; 20+ messages in thread
From: Wakko Warner @ 2004-01-23 17:42 UTC (permalink / raw)
  To: Karel Kulhavý; +Cc: linux-kernel

> Is it correct to issue "make bzImage modules modules_install"
> or do I have to do make bzImage; make modules modules_install?
> 
> Is there any documentation where I can read answer to this question?

I see nothing wrong with the first invocation, the second you should change
the ; to &&.  if make bzImage fails, it'll stop there.

I typically do all seperate like this:
make -j 20 bzImage && make -j 20 modules && make -j modules_install

Sometimes it doesn't complete, not sure why.

-- 
 Lab tests show that use of micro$oft causes cancer in lab animals

^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: gcc 2.95.3
  2004-01-23 16:30       ` Karel Kulhavý
@ 2004-01-23 18:33         ` Matthew Reppert
  2004-01-23 23:20           ` Stef van der Made
  0 siblings, 1 reply; 20+ messages in thread
From: Matthew Reppert @ 2004-01-23 18:33 UTC (permalink / raw)
  To: Karel Kulhavý; +Cc: Daniel Andersen, linux-kernel

[-- Attachment #1: Type: text/plain, Size: 960 bytes --]

On Fri, 2004-01-23 at 10:30, Karel Kulhavý wrote:
> On Fri, Jan 23, 2004 at 05:01:23PM +0100, Daniel Andersen wrote:
> > > I read here "make sure you have gcc 2.95.3 available" - does it mean
> > > my gcc-3.2.3 or gcc-3.2.2 is not suitable for kernel compiling?
> > 
> > Please have a look at http://developer.osdl.org/cherry/compile/
> 
> What if the kernel compiles cleanly but the generated code is invalid?
> Or is gcc-3.2.2 BugFree(TM) (BugFree as in BugFree speech, not as
> in BugFree beer)?

Many people have been using gcc-3.2 or later to build kernels, and I
haven't really heard of any problems with this, at least on i386. I
personally have used 3.2.2 and 3.3.2 (well, with Debian's patches) and
haven't had any weirdness with 2.6 or 2.4. ISTR there being arches that
need 3.x to compile, but I could be mistaken.

2.95.3 is definitely the *oldest* compiler you'd want to use, and pretty
much skip between that and 3.2.

Matt

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: gcc 2.95.3
  2004-01-23 15:13   ` gcc 2.95.3 Karel Kulhavý
  2004-01-23 16:03     ` Daniel Andersen
       [not found]     ` <001b01c3e1ca$26101f20$1e00000a@black>
@ 2004-01-23 18:55     ` Felipe Alfaro Solana
  2004-01-25 11:05     ` Florian Weimer
  3 siblings, 0 replies; 20+ messages in thread
From: Felipe Alfaro Solana @ 2004-01-23 18:55 UTC (permalink / raw)
  To: Karel Kulhavý; +Cc: Linux Kernel Mailinglist

On Fri, 2004-01-23 at 16:13, Karel Kulhavý wrote:
> On Fri, Jan 23, 2004 at 10:00:35AM -0500, Jeremy Andrews wrote:
> > > Is it correct to issue "make bzImage modules modules_install"
> > > or do I have to do make bzImage; make modules modules_install?
> > > 
> > > Is there any documentation where I can read answer to this question?
> > 
> > make help
> 
> Cool. I got to README :)
> 
> I read here "make sure you have gcc 2.95.3 available" - does it mean
> my gcc-3.2.3 or gcc-3.2.2 is not suitable for kernel compiling?

I've been compiling 2.5 and 2.6 kernels since gcc 3.3 with no problems.
In fact, there are patches on the -mm tree to help compiling with gcc
3.4 and 3.5.

I think the Documentation is a little bit updated ;-)


^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: make in 2.6.x
  2004-01-23 17:42 ` Wakko Warner
@ 2004-01-23 20:32   ` Sam Ravnborg
  0 siblings, 0 replies; 20+ messages in thread
From: Sam Ravnborg @ 2004-01-23 20:32 UTC (permalink / raw)
  To: Wakko Warner; +Cc: Karel Kulhavý, linux-kernel

On Fri, Jan 23, 2004 at 12:42:24PM -0500, Wakko Warner wrote:
> > Is it correct to issue "make bzImage modules modules_install"
> > or do I have to do make bzImage; make modules modules_install?
> > 
> > Is there any documentation where I can read answer to this question?
> 
> I see nothing wrong with the first invocation, the second you should change
> the ; to &&.  if make bzImage fails, it'll stop there.
> 
> I typically do all seperate like this:
> make -j 20 bzImage && make -j 20 modules && make -j modules_install
> 
> Sometimes it doesn't complete, not sure why.

Could you please enable verbose output, and send me a private mail with
the log when it fails.

Maybe I can dig out why it fails.
I'm sitting on UP here, so i usually never tries with -jN
where N > 2.

make V=1 -j20 && make V=1 -j20 modules && make V=1 -j20 modules_install

	Sam

^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: gcc 2.95.3
  2004-01-23 18:33         ` Matthew Reppert
@ 2004-01-23 23:20           ` Stef van der Made
  2004-01-24  0:48             ` Russell King
  2004-01-24 12:46             ` Ingo Buescher
  0 siblings, 2 replies; 20+ messages in thread
From: Stef van der Made @ 2004-01-23 23:20 UTC (permalink / raw)
  Cc: linux-kernel

Matthew Reppert wrote:

>snip
>  
>

>Many people have been using gcc-3.2 or later to build kernels, and I
>haven't really heard of any problems with this, at least on i386. I
>personally have used 3.2.2 and 3.3.2 (well, with Debian's patches) and
>haven't had any weirdness with 2.6 or 2.4. ISTR there being arches that
>need 3.x to compile, but I could be mistaken.
>
>2.95.3 is definitely the *oldest* compiler you'd want to use, and pretty
>much skip between that and 3.2.
>
>Matt
>  
>
Same here. I've been using gcc3.2.0 and beyond currently 3.3.2 since the 
day they were released and never had any big issues. I would recomend 
using gcc 3.3.2 since it improves performance when using optimizations 
quite a bit as far as I can remember the statistics.

Stef

^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: gcc 2.95.3
  2004-01-23 23:20           ` Stef van der Made
@ 2004-01-24  0:48             ` Russell King
  2004-01-26 14:41               ` David Woodhouse
  2004-01-24 12:46             ` Ingo Buescher
  1 sibling, 1 reply; 20+ messages in thread
From: Russell King @ 2004-01-24  0:48 UTC (permalink / raw)
  To: Stef van der Made; +Cc: linux-kernel

On Sat, Jan 24, 2004 at 12:20:02AM +0100, Stef van der Made wrote:
> Same here. I've been using gcc3.2.0 and beyond currently 3.3.2 since the 
> day they were released and never had any big issues. I would recomend 
> using gcc 3.3.2 since it improves performance when using optimizations 
> quite a bit as far as I can remember the statistics.

On ARM at least, gcc 3.2.x seems buggy.  It's along the lines of this:

 3.2.0: incorrect function argument offset calculation.
 3.2.x: miscompiles NEW_AUX_ENT in fs/binfmt_elf.c
        (http://gcc.gnu.org/PR8896) and incorrect structure
        initialisation in fs/jffs2/erase.c

I suspect that the fs/jffs2/erase.c problem is not ARM-specific, though
I'm no compiler expert.

However, gcc 3.3 seems table on ARM, and I'm not aware of any problems
with any further 3.3.x releases.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 PCMCIA      - http://pcmcia.arm.linux.org.uk/
                 2.6 Serial core

^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: gcc 2.95.3
  2004-01-23 23:20           ` Stef van der Made
  2004-01-24  0:48             ` Russell King
@ 2004-01-24 12:46             ` Ingo Buescher
  2004-01-24 18:32               ` Stef van der Made
  1 sibling, 1 reply; 20+ messages in thread
From: Ingo Buescher @ 2004-01-24 12:46 UTC (permalink / raw)
  To: linux-kernel

On Sat, 24 Jan 2004, Stef van der Made wrote:

> Matthew Reppert wrote:
> Same here. I've been using gcc3.2.0 and beyond currently 3.3.2 since the
> day they were released and never had any big issues. I would recomend
> using gcc 3.3.2 since it improves performance when using optimizations
> quite a bit as far as I can remember the statistics.
>


> Stef

Well, according to this list, gcc-3.3.2 at least has problems to compile
ALSA correctly, unless you activate framepointer support.

IB
-- 
"For every government X there is at least one government Y such that X
would claim that Y is a bunch of corrupt assholes.  Since every government
is  a bunch of corrupt assholes, every government is right at least in
one of its claims." -- Al Viro discussing politics on lkml

^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: gcc 2.95.3
  2004-01-24 12:46             ` Ingo Buescher
@ 2004-01-24 18:32               ` Stef van der Made
  0 siblings, 0 replies; 20+ messages in thread
From: Stef van der Made @ 2004-01-24 18:32 UTC (permalink / raw)
  Cc: linux-kernel

Ingo Buescher wrote:

>snip
>
>Well, according to this list, gcc-3.3.2 at least has problems to compile
>ALSA correctly, unless you activate framepointer support.
>
>IB
>  
>
I don't seem to have any issues using ALSA since kernel 2.6.1 and gcc 
3.3.2. I'm using an soundblaster live emu10k. I did have issues before 
this kernel version and had to use OSS emulation. btw I'm using x86 
(Athlon K7)

Cheers,

Stef

^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: gcc 2.95.3
  2004-01-23 15:13   ` gcc 2.95.3 Karel Kulhavý
                       ` (2 preceding siblings ...)
  2004-01-23 18:55     ` Felipe Alfaro Solana
@ 2004-01-25 11:05     ` Florian Weimer
  3 siblings, 0 replies; 20+ messages in thread
From: Florian Weimer @ 2004-01-25 11:05 UTC (permalink / raw)
  To: Karel Kulhavý; +Cc: linux-kernel

Karel Kulhavý wrote:

> Cool. I got to README :)
> 
> I read here "make sure you have gcc 2.95.3 available" - does it mean
> my gcc-3.2.3 or gcc-3.2.2 is not suitable for kernel compiling?

AFAIK, the README is woefully out of date.

^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: gcc 2.95.3
  2004-01-24  0:48             ` Russell King
@ 2004-01-26 14:41               ` David Woodhouse
  0 siblings, 0 replies; 20+ messages in thread
From: David Woodhouse @ 2004-01-26 14:41 UTC (permalink / raw)
  To: Russell King; +Cc: Stef van der Made, linux-kernel

On Sat, 2004-01-24 at 00:48 +0000, Russell King wrote:
> I suspect that the fs/jffs2/erase.c problem is not ARM-specific, though
> I'm no compiler expert.

I think it's been seen on MIPS too.

-- 
dwmw2


^ permalink raw reply	[flat|nested] 20+ messages in thread

* GCC 2.95.3
@ 2001-11-13  1:02 Hawkins Jeffrey-CJH016
  0 siblings, 0 replies; 20+ messages in thread
From: Hawkins Jeffrey-CJH016 @ 2001-11-13  1:02 UTC (permalink / raw)
  To: 'linuxppc-dev@lists.linuxppc.org'


I am looking for the last release of the GCC 2.95.3
for PowerPC.  From the linuxppc.org FTP Site (under
F. Sirl's area), I have been able to download the
2.95.3-v versions of all the GCC RPMs, except for
the GCC-C++-2.95.3-v.  For this file, I get a File not
on Server Error ????  I tried other Versions of 2.95.3
under the F. Sirl Area, as well as, tried getting files
from the LinuxPPC2000-Q4 and LinuxPPC-STABLE area ---
no luck getting the GCC-C++ RPM :(....

Any help would be appreciated....



Jeff

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

^ permalink raw reply	[flat|nested] 20+ messages in thread

* gcc 2.95.3
@ 2001-02-21 14:48 Tom Appermont
  0 siblings, 0 replies; 20+ messages in thread
From: Tom Appermont @ 2001-02-21 14:48 UTC (permalink / raw)
  To: linux-mips


Howdy,

This is just to report a problem I was having with gcc 2.95.3,
on an R5000 LE target (ddb5074). I got the compiler and binutils 
from ftp.ds2.pg.gda.pl (thank you Maciej ;).

For some reason (which I don't know), the code compiled with
gcc 2.95.3-14 fails to deal correctly with tlb exceptions on my
target. One obvious result is that page faults do not occur. 
Compiling with egcs 1.1.2 made this problem disappear. I spent 
many days trying to pin down what went wrong where, needless to 
say that it has been a painful introduction to Linux/MIPS... 


Cheerio,

Tom


-- 
................................................................
Tom Appermont                       SDCE
mailto: tom.appermont@sonycom.com   Sint Stevens Woluwestraat 55
tel: +32 2 7248620                  1130 Brussel
fax: +32 2 7262686                  Belgium

^ permalink raw reply	[flat|nested] 20+ messages in thread

end of thread, other threads:[~2004-01-26 14:42 UTC | newest]

Thread overview: 20+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-01-23 14:50 make in 2.6.x Karel Kulhavý
2004-01-23 15:11 ` Bas Mevissen
     [not found] ` <20040123100035.73bee41f.jeremy@kerneltrap.org>
2004-01-23 15:13   ` gcc 2.95.3 Karel Kulhavý
2004-01-23 16:03     ` Daniel Andersen
     [not found]     ` <001b01c3e1ca$26101f20$1e00000a@black>
2004-01-23 16:30       ` Karel Kulhavý
2004-01-23 18:33         ` Matthew Reppert
2004-01-23 23:20           ` Stef van der Made
2004-01-24  0:48             ` Russell King
2004-01-26 14:41               ` David Woodhouse
2004-01-24 12:46             ` Ingo Buescher
2004-01-24 18:32               ` Stef van der Made
2004-01-23 18:55     ` Felipe Alfaro Solana
2004-01-25 11:05     ` Florian Weimer
2004-01-23 15:20   ` make in 2.6.x Karel Kulhavý
2004-01-23 15:20 ` Sam Ravnborg
2004-01-23 15:39   ` David Woodhouse
2004-01-23 17:42 ` Wakko Warner
2004-01-23 20:32   ` Sam Ravnborg
  -- strict thread matches above, loose matches on Subject: below --
2001-11-13  1:02 GCC 2.95.3 Hawkins Jeffrey-CJH016
2001-02-21 14:48 gcc 2.95.3 Tom Appermont

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.