From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17581 invoked by alias); 23 Jan 2012 22:14:47 -0000 Received: (qmail 17573 invoked by uid 22791); 23 Jan 2012 22:14:46 -0000 X-SWARE-Spam-Status: No, hits=-1.3 required=5.0 tests=AWL,BAYES_00,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE X-Spam-Check-By: sourceware.org Received: from smtp06.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.128) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 23 Jan 2012 22:14:29 +0000 Received: from treguer.localnet ([90.32.112.232]) by mwinf5d41 with ME id RAES1i00Q50tzZm03AES55; Mon, 23 Jan 2012 23:14:28 +0100 From: "Yann E. MORIN" To: crossgcc@sourceware.org Subject: Re: Using crosstool-ng on OpenBSD Date: Mon, 23 Jan 2012 22:14:00 -0000 User-Agent: KMail/1.13.5 (Linux/3.2.1-treguer; KDE/4.4.5; x86_64; ; ) Cc: Renaud Allard References: <4F1D11AA.6010602@allard.it> <201201231925.07143.yann.morin.1998@free.fr> <4F1DA739.2000901@allard.it> In-Reply-To: <4F1DA739.2000901@allard.it> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201201232314.26146.yann.morin.1998@free.fr> Mailing-List: contact crossgcc-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: crossgcc-owner@sourceware.org X-SW-Source: 2012-01/txt/msg00057.txt.bz2 On Monday 23 January 2012 19:30:17 Renaud Allard wrote: > On 23/01/12 19:25, Yann E. MORIN wrote: > > OK, -r is not even in POSIX, while -R is. Can you check that BSD's cp > > does handle the -pR combination? If so, I'll chamge it. > Yes, it does support -pR, which is indeed the correct way to pass the > recursive argument. OK. > > -v missing is not too problematic either. Its only use is to make the > > progress bar rotate, so as to give the user some feedback that the > > process is not hung. If we remove it, the progress bar will hang for > > some time during very big copies, but if that's the price to pay... > Doesn't it also affect debugging output? Well, partialy. At least, the command being executed is logged, its stdout, as well as its stderr. So, if the commands prints some progress status (as 'cp -v' was used for), or prints errors (on stderr), it should be logged appropriately. And because the command being executed is logged, it's always possible to hand-type it for further investigation. The 'cp -v' was really intended for cases where the copy could take a bunch of time, see eg. this changeset: http://crosstool-ng.org/hg/crosstool-ng/rev/c3ff88a0c788 So, removing the '-v' from 'cp' incantations would just look like no progress for a little while for unsuspecting users. That should be eventually worked around with a _usability_ fix, but for now, it's time for a _feature_ fix. And yes, I know, there are a bunch of pending patches on the list. I'll catter to them during the week, and then hope for the release to be ready before the end of the month (and obviously, before FOSDEM! Beer, yeah! :-)) Regards, Yann E. MORIN. -- .-----------------.--------------------.------------------.--------------------. | Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: | | +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ | | +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no | | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. | '------------------------------^-------^------------------^--------------------' -- For unsubscribe information see http://sourceware.org/lists.html#faq