From: pa3gcu <pa3gcu@zeelandnet.nl>
To: wb9mjn <wb9mjn@wb9mjn-11.ampr.org>
Cc: linux-hams@vger.kernel.org
Subject: Re: Linux Newbie with Compiling Problems...
Date: Sun, 2 Mar 2003 22:06:11 +0000 [thread overview]
Message-ID: <03030222061105.00595@unix.pa3gcu> (raw)
In-Reply-To: <01C2E0CD.FDFF9C20.wb9mjn@wb9mjn-11.ampr.org>
On Sunday 02 March 2003 21:11, wb9mjn wrote:
> Hi All,
>
> I think I may have found a workaround.
I doubt that very much, 'as' is not 'as86'
as = the portable GNU assembler
as86 = Assembler for 8086..80386 processors
But having said that it would not suprise me to see that Mandarke have
converted both into one and simply called it 'as'.
> With allot of looking, I
> found that as86 is a part of a package that does the same thing as dev86
> (real mode assembly). So, I started looking around in the directories that
> dev86 deposits its files. No, 'as86' (or 'as') was not part of dev86
> itself. But, the system had installed a program called 'as' in /usr/bin/
> directory. I did a 'as --help' command and the result made it clear that
> this was indeed an assembler program. So, made a copy of 'as' renamed to
> 'as86' and did
>
> make clean
> make bzImage
>
> It seems to be taking allot longer than previously. Hopefully this
> will work. Any comments?
Tell us if it did work and you can actually boot you kernel assembled with as
called as86.
> 73, Don...
--
Regards Richard
pa3gcu@zeelandnet.nl
http://people.zeelandnet.nl/pa3gcu/
next prev parent reply other threads:[~2003-03-02 22:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-02 21:11 Linux Newbie with Compiling Problems wb9mjn
2003-03-02 21:32 ` Hamish Moffatt
2003-03-02 22:06 ` pa3gcu [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-02 22:05 wb9mjn
2003-03-02 17:20 wb9mjn
2003-03-02 21:33 ` Ray Heasman
2003-03-02 14:42 wb9mjn
2003-03-03 18:37 ` Bernard Pidoux F6BVP
2003-03-02 0:58 wb9mjn
2003-03-02 5:23 ` Kelly Black
2003-03-02 8:40 ` Jean-Luc
2003-03-03 7:46 ` Wilbert Knol
[not found] <01C2DD5E.5937F920.wb9mjn@wb9mjn-11.ampr.org>
2003-02-26 12:55 ` Pontus Falk
[not found] <01C2DCFB.BA1D9C80.wb9mjn@wb9mjn-11.ampr.org>
2003-02-26 6:56 ` Pontus Falk
2003-02-26 7:41 ` pa3gcu
[not found] <01C2DC36.D1A6A7E0.wb9mjn@wb9mjn-11.ampr.org>
2003-02-25 19:09 ` Pontus Falk
[not found] <01C2DB6A.A5024180.wb9mjn@wb9mjn-11.ampr.org>
2003-02-24 6:00 ` Pontus Falk
2003-02-23 23:36 Pontus Falk
2003-02-23 21:51 wb9mjn
2003-02-23 22:50 ` Shane Deering
2003-02-24 18:10 ` Bernard Pidoux F6BVP
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=03030222061105.00595@unix.pa3gcu \
--to=pa3gcu@zeelandnet.nl \
--cc=linux-hams@vger.kernel.org \
--cc=wb9mjn@wb9mjn-11.ampr.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