From: Tom Rini <trini@kernel.crashing.org>
To: "Curtis, Allen" <Allen.Curtis@Thales-IFS.com>
Cc: "'linuxppc-dev@lists.linuxppc.org'"
<linuxppc-dev@lists.linuxppc.org>,
"'acurtis@onz.com'" <acurtis@onz.com>
Subject: Re: linuxppc_2_4_devel - Walnut compile
Date: Fri, 3 May 2002 09:42:42 -0700 [thread overview]
Message-ID: <20020503164242.GB894@opus.bloom.county> (raw)
In-Reply-To: <FA06AA2C99BCD511951200005A99441043863E@irvexch1.sextantifs.com>
On Thu, May 02, 2002 at 04:06:46PM -0700, Curtis, Allen wrote:
> 1. make menuconfig (xconfig - does not work)
> and stripped out all of the extra junk
>
I hopefully just fixed xconfig. Now I need to talk to Keith Owens to
get the proper fix pushed onto Marcelo.
> 2. linker error - early_serial* symbols undefined
> modified drivers/char/Makefile - to include serial.c
Turn on CONFIG_SERIAL. No one has tested any of the 4xx configs w/o
CONFIG_SERIAL, so it's not supprising it didn't work. I've pushed a few
small things which might help however.
> 3. linker error - serial_close() undefined
> reviewed the source code in arch/ppc. I believe that I need serial_sicc.c
This is odd. Where was the linker error? serial_close() is also in the
bootwrapper stuff.
> 4. Reviewed arch/ppc/config.in and discovered the following
Fix this as well (missing space was the actual problem).
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-05-03 16:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-02 23:06 linuxppc_2_4_devel - Walnut compile Curtis, Allen
2002-05-03 16:42 ` Tom Rini [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-03 16:39 Curtis, Allen
2002-05-03 16:59 ` Tom Rini
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=20020503164242.GB894@opus.bloom.county \
--to=trini@kernel.crashing.org \
--cc=Allen.Curtis@Thales-IFS.com \
--cc=acurtis@onz.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox