From: Steve Rossi <srossi@ccrl.mot.com>
To: Embedded Linux PPC List <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: more on e2fsck
Date: Wed, 17 May 2000 15:30:34 -0500 [thread overview]
Message-ID: <3923016A.6AB13AE8@ccrl.mot.com> (raw)
In-Reply-To: 200005171655.SAA21603@denx.local.net
It was operator error ... in the MCONFIG.in I changed $CC to
powerpc-linux-gcc but $LD was still set to cc, so I changed
$LD to powerpc-linux-gcc and it worked. Must have been
screwing something up in the link stage.
Thanks for the help!
Steve
Wolfgang Denk wrote:
> In message <3922CB9E.873738B6@ccrl.mot.com> you wrote:
> >
> > is there possibly some disparity between the kernel's ext2 fs code and
> > what
> > mke2fs and e2fsck are doing? if anyone has any further thoughts on this
> > I would appreciate it.
>
> Maybe header files, endianess, or so?
>
> What is your build environment?
>
> Wolfgang Denk
>
> --
> Software Engineering: Embedded and Realtime Systems, Embedded Linux
> Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
> Quote from a recent meeting: "We are going to continue having these
> meetings everyday until I find out why no work is getting done."
--
-------------------------------------------------------
Steven K. Rossi srossi@ccrl.mot.com
Staff Engineer
Multimedia Communications Research Laboratory
Motorola Labs
-------------------------------------------------------
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next parent reply other threads:[~2000-05-17 20:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200005171655.SAA21603@denx.local.net>
2000-05-17 20:30 ` Steve Rossi [this message]
2000-05-17 16:41 more on e2fsck Steve Rossi
2000-05-17 16:49 ` Pavel Roskin
2000-05-17 22:06 ` Dan Malek
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=3923016A.6AB13AE8@ccrl.mot.com \
--to=srossi@ccrl.mot.com \
--cc=linuxppc-embedded@lists.linuxppc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).