All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sander Sweers <sander.sweers@gmail.com>
To: Chris Wakefield <c_wakefield@shaw.ca>
Cc: reiserfs-list@namesys.com
Subject: Re: grub reiser4 won't compile
Date: Mon, 2 May 2005 23:39:39 +0000	[thread overview]
Message-ID: <b65fbb1305050216391187d449@mail.gmail.com> (raw)
In-Reply-To: <200505021520.00991.c_wakefield@shaw.ca>

On 02/05/05, Chris Wakefield <c_wakefield@shaw.ca> wrote:
> ls -l /var/cache/apt/archives|grep grub
> -rw-r--r--  1 root root   733102 2005-01-17 16:40
> grub_0.95+cvs20040624-13_amd64.deb
> -rw-r--r--  1 root root   733396 2005-02-05 07:18
> grub_0.95+cvs20040624-14_amd64.deb
> -rw-r--r--  1 root root   733610 2005-02-18 16:18
> grub_0.95+cvs20040624-15_amd64.deb
> -rw-r--r--  1 root root   733800 2005-03-21 00:41
> grub_0.95+cvs20040624-16_amd64.deb
> 
> This is odd.   I run pure64 amd64 and these packages indicate that they are 64
> bit?
> 
> Chris W.
On gentoo if you have a multilib environment it will be built with
-m32 (just checked) and if you built it with -m64 i get the same error
as you. Gentoo has a special static 32bit package if you do not run
multilib, my guess is that Debian does the same with those packages.

Sander

-- 
After a time, you may find that "having" is not so pleasing a thing,
after all, as "wanting." It is not logical, but it is often true.

Spock, "Amok Time"
stardate 3372.7

  reply	other threads:[~2005-05-02 23:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-28  5:26 grub reiser4 won't compile Chris Wakefield
2005-04-28 12:06 ` Vitaly Fertman
2005-04-29  9:11   ` Chris Wakefield
2005-04-29 11:19     ` Vitaly Fertman
2005-05-02 14:51       ` Hans Reiser
2005-05-02 15:17         ` Sander Sweers
2005-05-02 22:20           ` Chris Wakefield
2005-05-02 23:39             ` Sander Sweers [this message]
2005-05-03 17:50           ` Hans Reiser

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=b65fbb1305050216391187d449@mail.gmail.com \
    --to=sander.sweers@gmail.com \
    --cc=c_wakefield@shaw.ca \
    --cc=reiserfs-list@namesys.com \
    /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.