All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@mailhost.uni-koblenz.de>
Subject: GCC bug
Date: Sat, 5 Jul 1997 23:09:21 +0200 (MET DST)	[thread overview]
Message-ID: <199707052109.XAA12388@informatik.uni-koblenz.de> (raw)

Hi,

the most current GCC package installs the header file assert.h although
it shouldn't.  The problem is that the GCC version of assert.h will
not include <gnu/stubs.h> but autoconf generated configure scripts
rely on that.  If you ever wondered why loading programs caused warnings
like 'the function lchown is not implemented and will always fail', this
is caused by the wrong assert.h.

Quick fix: rm <prefix>/<target>/include/assert.h, for example.
rm /usr/local/mipsel-linux/include/assert.h.  Note that this applies
to both native and crosscompilers.  None of them will install the
assert.h file in /usr/include/.

  Ralf

             reply	other threads:[~1997-07-05 21:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-07-05 21:09 Ralf Baechle [this message]
  -- strict thread matches above, loose matches on Subject: below --
1998-07-10 19:49 GCC bug ralf
2000-03-31 14:27 gcc bug Josh Huber
2000-03-31 15:18 ` Gabriel Paubert
2003-06-18 19:00 David Mosberger

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=199707052109.XAA12388@informatik.uni-koblenz.de \
    --to=ralf@mailhost.uni-koblenz.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.