From: Brendan Simon <bsimon@ctam.com.au>
Cc: linuxppc-dev <linuxppc-dev@lists.linuxppc.org>,
linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>,
linux-embedded <linux-embedded@waste.org>
Subject: Re: Building 'mount' for an embedded system
Date: Fri, 19 Nov 1999 12:58:46 +1100 [thread overview]
Message-ID: <3834AED6.60CEFA8D@ctam.com.au> (raw)
In-Reply-To: kfyiu2z7wby.fsf@kieraypc07.p.y.ki.era.ericsson.se
Marcus Sundberg wrote:
> Brendan Simon <bsimon@ctam.com.au> writes:
>
> > I read README.mount which said mount was presently maintained by Andries
> > Brouwer <aeb@cwi.nl> and the ftp site is ftp.win.tue.nl/pub/linux/util.
> >
> > I downloaded
> > ftp://ftp.win.tue.nl/pub/linux/utils/util-linux/util-linux-2.10b.tar.gz
> > which had some of the missing files but not all of them.
>
> It would help if you told what files are missing.
It was make_include. I thought I had executed configure but I objviously
didn't.
> I built mount from one of the 2.9 versions of util-linux without
> problems.
Did you compile on a native powerpc system or did you use a cross-compiler ?
I think the problem I am having is that configure is not setup to support
cross-compilation. I have got a little further now by massaging the MCONFIG
file and the generate make_include file. I will have a go at editing the
configure script and submit any changes to the utils-linux maintainer. I
will also let the linux-embedded mailing lists know of my results.
Thanks,
Brendan Simon.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~1999-11-19 1:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <38333C71.3FFD50E@ctam.com.au>
1999-11-18 13:39 ` Building 'mount' for an embedded system Marcus Sundberg
1999-11-19 1:58 ` Brendan Simon [this message]
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=3834AED6.60CEFA8D@ctam.com.au \
--to=bsimon@ctam.com.au \
--cc=linux-embedded@waste.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--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 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.