functions: avoid CR when progress bar is not enabled

Using CT-NG with progress bar disabled, still prints CR ('\r') characters
on the output. When you capture the output to a file as part of an
automated build, it shows extra empty lines.

For example:

------------------------------------------------------------
[INFO ] Performing some trivial sanity checks

[INFO ] Build started 20110404.113619

[INFO ] Building environment variables

[EXTRA] Preparing working directories

[EXTRA] Installing user-supplied crosstool-NG configuration
------------------------------------------------------------

Signed-off-by: Javier Viguera <javier.viguera@digi.com>
(transplanted from cbd07f3dd6e3689a6b971e999aa82d09fb94d515)

diff -dur binutils-2.17.old/bfd/opncls.c binutils-2.17/bfd/opncls.c

--- binutils-2.17.old/bfd/opncls.c	2006-03-16 13:20:16.000000000 +0100

+++ binutils-2.17/bfd/opncls.c	2007-05-01 18:26:11.000000000 +0200

@@ -158,6 +158,13 @@

 {

   bfd *nbfd;

   const bfd_target *target_vec;

+  struct stat s;

+

+  if (stat (filename, &s) == 0)

+    if (S_ISDIR(s.st_mode)) {

+      bfd_set_error (bfd_error_file_not_recognized);

+      return NULL;

+    }

   nbfd = _bfd_new_bfd ();

   if (nbfd == NULL)