This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH] Keep an uncompressed build log

From: Trevor Woerner <twoerner at gmail dot com>
To: "Yann E. MORIN" <yann dot morin dot 1998 at anciens dot enib dot fr>
Cc: crossgcc at sourceware dot org
Date: Fri, 4 Mar 2011 13:39:26 -0500
Subject: Re: [PATCH] Keep an uncompressed build log
References: <77ce48248e124ecc80d5.1299134840@suse64.vjbtlw> <201103032344.52094.yann.morin.1998@anciens.enib.fr> <AANLkTik0uQC-4-SnTAQ2JpsJ2Bnrt3NwJLWMy3vVJCOB@mail.gmail.com> <201103041933.40043.yann.morin.1998@anciens.enib.fr>

Yann,

On Fri, Mar 4, 2011 at 1:33 PM, Yann E. MORIN
<yann.morin.1998@anciens.enib.fr> wrote:
>> These lines (and behaviour) were pre-existing:
>
> Yes, I know! I (still!) know how to read a patch! ;-)

Sorry Yann, I didn't mean to insult you. I misunderstood your email :-(

> Yes, that was my suggestion. That would be much more logical. If the build
> fails for whatever reason, the build.log is there in the working directory
> for the user to look at it. And if the build is complete, the build.log is
> also there.
>
> Then, the copy in the toolchain directory is just that the build.log gets
> associated with a complete toolchain.

I like that idea much better; I'll get working on it.

--
For unsubscribe information see http://sourceware.org/lists.html#faq

References:
- [PATCH] Keep an uncompressed build log
  - From: Trevor Woerner
- Re: [PATCH] Keep an uncompressed build log
  - From: Yann E. MORIN
- Re: [PATCH] Keep an uncompressed build log
  - From: Trevor Woerner
- Re: [PATCH] Keep an uncompressed build log
  - From: Yann E. MORIN

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]