Markus Hoenicka wrote:
Quoting km4hr <[EMAIL PROTECTED]>:
I just happened to notice that I may not be executing the sqlite
installation process (configure/make/make install) in a full "bash"
environment. My usual environment is "ksh". Typing in the command
"/bin/OpenSource/bin/bash" I get a bash prompt. But apparently that
doesn't
put me in a full bash environment. I just noticed that unless I
specify the
full path to the GNU make command (/opt/OpenSource/bin/make) then the ksh
version (/usr/bin/make) is executed. I wonder what I have to do to get
into
a true bash environment? Must be some environment viable that has to be
changed. Oh well, one mystery begets another!
There is no such thing as a full "bash" environment. bash is just
another shell, just like ksh. You may experience some differences
because the shells may read different startup files, so e.g.
environment variables may be set differently.
Some systems like FreeBSD call the GNU make binary "gmake" to
distinguish it from the system's own make binary. You could put a
symlink called "gmake" into /usr/bin (or /usr/local/bin, depending on
your local policy) which points to /opt/OpenSource/bin/make. You can
then run GNU make by using "gmake" instead of "make" in the build
process from any shell you prefer.
regards,
Markus
Markus has good advice. We make legacy Unix machines compatible with
open source software by installing gcc and key GNU utilities like make,
bison etc in /usr/local/bin and put that in the path. Where the names
clash, like with "make" we name the GNU one gmake.
You then have the ./configure, gmake and gmake install sequence working.
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
