Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Andrew Shugg <andrew@neep.com.au>
To: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] 2.4.6-pa20 question about modules
Date: Fri, 20 Jul 2001 13:56:46 +0800	[thread overview]
Message-ID: <20010720135640.W23932@neep.com.au> (raw)
In-Reply-To: <OF46B79DB5.FE766246-ONC1256A8E.005BA756@LocalDomain>; from jso@europay.com on Thu, Jul 19, 2001 at 07:46:09PM +0200

Quoth Joël Soete:
> Just a small tips I use on my i386 linux-box: I launch the make in one line
> and tacke a log which I can so analyze later like:
> 
> make dep clean bzImage modules modules_install 2>&1 | tee /var/tmp/kl-200107.log

Safer to run them separately.  You can still easily log them, there are
many possible ways to do this ...

$ for target in clean dep vmlinuz modules modules_install
> do make $target 2>&1 | tee -a /var/tmp/kl-200107.log
> done

$ (make clean ; make dep ; make vmlinux ; make modules ; make modules_install) 2>&1 | tee -a /var/tmp/kl-200107.log

$ script /var/tmp/kl-200107.log
Script started, output file is /var/tmp/kl-200107.log
$ make clean ; make dep ; make vmlinux ; make modules ; make modules_install ; exit
...
Script done, output file is /var/tmp/kl-200107.log
$


Andrew.

-- 
Andrew Shugg <andrew@neep.com.au>                   http://www.neep.com.au/

"Just remember, Mr Fawlty, there's always someone worse off than yourself."
"Is there?  Well I'd like to meet him.  I could do with a good laugh."

  parent reply	other threads:[~2001-07-20  5:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-19 17:46 [parisc-linux] 2.4.6-pa20 question about modules Joël Soete
2001-07-19 18:14 ` Matthew Wilcox
2001-07-20  5:56 ` Andrew Shugg [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-07-19  8:48 Joël Soete
2001-07-18 16:33 Joël Soete
2001-07-18 23:24 ` Richard Hirst

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010720135640.W23932@neep.com.au \
    --to=andrew@neep.com.au \
    --cc=parisc-linux@lists.parisc-linux.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox