From: "Charles E. Leiserson, Jr." <locutus@MIT.EDU>
To: Hollis R Blanchard <hollis+@andrew.cmu.edu>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: No-IDE kernel compile link errors
Date: Tue, 09 Mar 1999 11:38:44 EST [thread overview]
Message-ID: <199903091638.LAA14811@all-night-tool.mit.edu> (raw)
In-Reply-To: Your message of "Mon, 08 Mar 1999 23:12:18 EST." <Pine.LNX.3.96L.990308225823.26298C-100000@unix48.andrew.cmu.edu>
-----BEGIN PGP SIGNED MESSAGE-----
> Awesome. Of course it can't find those symbols - I haven't compiled (and don't
> want) any IDE stuff.
I seem to recall having read something about the 2.2 kernels not compiling if
IDE isn't set. I had the same problem, so I just compiled in IDE support,
even though I have no IDE devices or bus.
Feel free to correct me if I'm wrong.
- Ricky
-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
iQCVAwUBNuVOk/o7QJfqAx6RAQHquQQAt4t0gsatGCnvVpwvLJQZh7a7Vj2rISNP
I+pYrvhDN9SyIAr4rTZNnrObB9zM8JntGAxmq8fQQOULcymNJTE+33ll9kLvbJFg
OdHIfQFgn5phshEPKoo1S5P16Ss76fzGTqhJIbF/NQk+jHJpjU9k8q21yBXJJ1Zs
73wqg6a++To=
=TBjn
-----END PGP SIGNATURE-----
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
next prev parent reply other threads:[~1999-03-09 16:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-09 4:12 No-IDE kernel compile link errors Hollis R Blanchard
1999-03-09 10:23 ` Martin Costabel
1999-03-09 14:05 ` Tom Rini
1999-03-09 14:36 ` Hollis R Blanchard
1999-03-09 15:05 ` Tom Rini
1999-03-09 16:38 ` Charles E. Leiserson, Jr. [this message]
1999-03-09 21:31 ` Tom Rini
-- strict thread matches above, loose matches on Subject: below --
1999-03-11 2:41 Steven Sartorius
1999-03-11 4:00 ` Paul Mackerras
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=199903091638.LAA14811@all-night-tool.mit.edu \
--to=locutus@mit.edu \
--cc=hollis+@andrew.cmu.edu \
--cc=linuxppc-dev@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.