You should have a config.log file that contains most of the output of the
configure command, along with a lot of extra stuff that is useful for looking
into issues with the configure step.
Issue the following command before doing the configure...
script
Then issue the configure and make, and then issue the command...
exit
You will end up with a file name 'typescript' that contains all the output of
the configure and make commands.
Kris
On Mon, Jun 13, 2005 at 03:12:37PM -0400, Post, Mark K wrote:
> No. By default, all output goes to stdout, and stderr. If you want
> that to wind up in a file, you need to redirect it.
>
>
> Mark Post
>
> -----Original Message-----
> From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
> Tom Duerbusch
> Sent: Monday, June 13, 2005 3:06 PM
> To: [email protected]
> Subject: Re: Question for those "C" types out there
>
>
> I would have been happy if, somehow, all these warning/error messages
> could be gathered and repeated at the end (like real compilers do<G>).
>
> I assume that all these messages also went to a file. At this point, I
> don't know enought to know where that file is. I was hoping for
> something over in '/var', but nothing from the './configure' or 'make'.
>
> Tom Duerbusch
> THD Consulting
>
> ----------------------------------------------------------------------
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
--
Never underestimate a Mage with:
- the Intelligence to cast Magic Missile,
- the Constitution to survive the first hit, and
- the Dexterity to run fast enough to avoid being hit a second time.
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
