From: Chris Wakefield <c_wakefield@shaw.ca>
To: reiserfs-list@namesys.com
Subject: Re: grub reiser4 won't compile
Date: Fri, 29 Apr 2005 02:11:42 -0700 [thread overview]
Message-ID: <200504290211.42905.c_wakefield@shaw.ca> (raw)
In-Reply-To: <200504281606.42243.vitaly@namesys.com>
Hi Vitaly.
Thanks for your reply.
I tried every reasonable combo:
apt-get source grub ... patched it with LATEST_PATCH ...that wouldn't compile
with or without the patch,
grub-0.95,
grub-0.96,
all the same result.
I wasn't sure what to do with "LATEST_GRUB", it seemed to be a binary for some
reason.
I'm stumped.
Thanks,
Chris W.
On April 28, 2005 05:06 am, Vitaly Fertman wrote:
> On Thursday 28 April 2005 09:26, Chris Wakefield wrote:
> > Greetings all.
> >
> > I'm attempting to setup Reiser4 on a partition and I've got as far as
> > trying to compiling grub and I've run into a wall.
> >
> > It's a Reiser4 patched grub source from:
> > ftp://ftp.namesys.com/pub/reiser4progs/grub/LATEST_PATCH
>
> so is it reiser4 patched grub from LATEST_GRUB or
> the reiser4 grub patch from LATEST_PATCH?
>
> > anyways, I run configure and I get:
> >
> > "....checking build system type... x86_64-unknown-linux-gnu
> > checking host system type... x86_64-unknown-linux-gnu...
> >
> > .........................
> >
> > ........"checking for C compiler default output file name... configure:
> > error: C compiler cannot create executables".
> >
> > config log error is:
> > ......."configure:2416: $? = 1
> > configure: failed program was: | /* confdefs.h. */" ......
> >
> > This is happening only with reiser4 grub, as I'm able to compile kernels
> > and who knows what else .. it's just this source only.
> > Do I require a different source or do I have to compile reiser4 grub in a
> > 32 bit chroot environment?
>
> what does the plain grub-0.96 without reiser4 patch say?
next prev parent reply other threads:[~2005-04-29 9:11 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 [this message]
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
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=200504290211.42905.c_wakefield@shaw.ca \
--to=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.