From: Phil Goembel <phil-goembel@wi.rr.com>
To: Raghavan <raghavan.viswanathan@wipro.com>
Cc: Riley Williams <Riley@Williams.Name>,
Linux ELKS <Linux-8086@vger.kernel.org>
Subject: Re: ELKS Development/FAQ Questions
Date: 01 Aug 2003 09:19:27 -0500 [thread overview]
Message-ID: <1059747566.15148.7899.camel@castle> (raw)
In-Reply-To: <003201c35749$fe749c30$1056a8c0@wipro.com>
[-- Attachment #1: Type: text/plain, Size: 1041 bytes --]
Hi Rags,
Thank you. This is what I want to do. I will take a look at the
Makefile for dev86 to see how to specify the install directory.
I assume I will have to do one or more of these things:
a. edit the Makefile,
b. set an environment variable,
c. or pass an argument to the make command
Is that correct?
Regards,
Phil
On Thu, 2003-07-31 at 04:56, Raghavan wrote:
> Phil,
>
> I got the dev86 sources (dev86-0.16.1 ), built it and installed it in my
> Home directory as a part of making ELKS 1.1
>
> I installed it in ~/ELKS/my_install directory. I had to mention that this
> was where I wanted to install in my Makefile ( or one of its related config
> file ) while building the dev86.
> The, I did a 'make install'.
>
> After that , I tweaked PATH as follows to make it see my bcc before the
> system'c bcc which was there in /usr/bin or /usr/local/bin..
>
> PATH=$HOME/ELKS/my_install/bin:$PATH
>
> After that I built ELKS , It just worked fine. No Issues at all.
>
> bye,
> rags
>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-08-01 14:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-24 19:58 Web language codes Riley Williams
2003-07-31 0:33 ` ELKS Development/FAQ Questions Phil Goembel
2003-07-31 6:01 ` Riley Williams
2003-07-31 9:56 ` Raghavan
2003-07-31 21:30 ` Phil Goembel
2003-07-31 21:41 ` Paul Nasrat
2003-08-01 14:19 ` Phil Goembel [this message]
2003-08-01 14:05 ` Phil Goembel
2003-08-01 22:42 ` Riley Williams
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=1059747566.15148.7899.camel@castle \
--to=phil-goembel@wi.rr.com \
--cc=Linux-8086@vger.kernel.org \
--cc=Riley@Williams.Name \
--cc=raghavan.viswanathan@wipro.com \
/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