Essien Essien wrote:
>
> that was really funny you know :)
Always a pleasure to provide entertainment for my friends.
>
> On POSIX systems you're supposed to do three things to get your
> software installed (usually a standard set of three commands).
>
> 1. ./configure (some packages leave this out, since they don't use GNU
> autotools)
> 2. make (there's almost always this, or an alternative, CMAKE, Scons, ant,
> etc)
> 3. make install (if there's a Makefile, you'll be able to do a make
> install, if the software is supposed to be used anyways... and all
> replacements have equivalents - ant deploy for instance).
>
I did try your method. These are the same steps given in the sqlite README
file. I've used them before in other installations. But they didn't work for
me in this case. Here's the directions from the sqlite README file.
tar xzf sqlite.tar.gz ;# Unpack the source tree into "sqlite"
mkdir bld ;# Build will occur in a sibling directory
cd bld ;# Change to the build directory
../sqlite/configure ;# Run the configure script
make ;# Run the makefile.
make install ;# (Optional) Install the build products
I performed the above steps as stated. But they failed on my HPUX 11.0 box.
First, the "make" step fails immediately as I explained earlier. The README
file doesn't explain that HP's "make" won't work and that you have to use
the GNU "make" instead. Many people won't realize this. I have done them a
service by telling them so.
The "make install" step doesn't work either. It gives error messages saying
the "-d" option is invalid for the "cp" command. You also get the following
crytic message. I asked HP about this. They don't recommend it.
>> If you ever happen to want to link against installed libraries
>> in a given directory, LIBDIR, you must either use libtool, and
>> specify the full pathname of the library, or use the `-LLIBDIR'
>> flag during linking and do at least one of the following:
>>- add LIBDIR to the `SHLIB_PATH' environment variable
>> during execution
>> - use the `-Wl,+b -Wl,LIBDIR' linker flag
>> See any operating system documentation about shared libraries for
>> more information, such as the ld(1) and ld.so(8) manual pages.
I posted my experience on this site hoping it might benefit anyone who wants
to use sqlite but has found that the standard install process isn't working.
Even though my method looks strange, I prefer funny success over sad
failure.
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!
--
View this message in context:
http://www.nabble.com/I%27m-Starving-for-New-User-Information-tf3701471.html#a10412825
Sent from the SQLite mailing list archive at Nabble.com.
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
