public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: crossgcc@sourceware.org
Cc: Renaud Allard <renaud@allard.it>
Subject: Re: Using crosstool-ng on OpenBSD
Date: Mon, 23 Jan 2012 22:14:00 -0000	[thread overview]
Message-ID: <201201232314.26146.yann.morin.1998@free.fr> (raw)
In-Reply-To: <4F1DA739.2000901@allard.it>

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

  reply	other threads:[~2012-01-23 22:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-23  7:52 Renaud Allard
2012-01-23 17:39 ` Yann E. MORIN
2012-01-23 17:50   ` Renaud Allard
2012-01-23 18:25     ` Yann E. MORIN
2012-01-23 18:30       ` Renaud Allard
2012-01-23 22:14         ` Yann E. MORIN [this message]
2012-02-01 21:15         ` Yann E. MORIN
2012-02-01 21:44           ` Renaud Allard

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=201201232314.26146.yann.morin.1998@free.fr \
    --to=yann.morin.1998@free.fr \
    --cc=crossgcc@sourceware.org \
    --cc=renaud@allard.it \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).