All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dale Amon <amon@vnl.com>
To: linux-kernel@vger.kernel.org
Subject: 2.6.0 compile failure
Date: Fri, 26 Dec 2003 01:02:04 +0000	[thread overview]
Message-ID: <20031226010204.GM4987@vnl.com> (raw)

Looks like this is the night for 2.6.0 bug reports!
Here's the output when the build craps out:

fs/smbfs/inode.c: In function `smb_fill_super':
fs/smbfs/inode.c:554: warning: comparison is always false due to limited range of data type
fs/smbfs/inode.c:555: warning: comparison is always false due to limited range of data type
gcc: {standard input}: Assembler messages:
{standard input}:11930: Warning: end of file not at end of a line; newline inserted
{standard input}:12164: Error: invalid character '_' in mnemonic
Internal error: Terminated (program cc1)
Please submit a full bug report.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
For Debian GNU/Linux specific bugs,
please see /usr/share/doc/debian/bug-reporting.txt.

make[2]: *** [drivers/block/floppy.o] Error 1
make[1]: *** [drivers/block] Error 2
make: *** [drivers] Error 2

I'll probably try building without smbfs. Same
config worked with test11.

-- 
------------------------------------------------------
   Dale Amon     amon@islandone.org    +44-7802-188325
       International linux systems consultancy
     Hardware & software system design, security
    and networking, systems programming and Admin
	      "Have Laptop, Will Travel"
------------------------------------------------------

             reply	other threads:[~2003-12-26  1:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-26  1:02 Dale Amon [this message]
2003-12-26  1:45 ` 2.6.0 compile failure Joshua Kwan
2003-12-26  9:49   ` Dale Amon

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=20031226010204.GM4987@vnl.com \
    --to=amon@vnl.com \
    --cc=linux-kernel@vger.kernel.org \
    /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.