Building a Slackware Package when trackinstall -i="make install" fails
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Building a Slackware Package when trackinstall -i="make install" fails
Hi Forum
There are some libs that I want to build, as *.t?z, I know how to build them from source as binaries, things like PETSc, Spooles, ARPACK...
But I do not want to "make install" them, what I want after the build is to be able to create them as packages, that can easily be managed...
But trying to run trackinstall -i="make install" in the source tree of PETSc, for instance, yelds an error, even after having configured --prefix=/usr/local ... yet the thing was actually built...
I've searched in man trackinstall but the closest thing I've found so far is the "install line", still this fails...
Detailed instructions:
(MS Windows only) Install cygwin package (including make, python modules) and use cygwin shell.
Sugest downloading and installing PETSc as a regular/non-root user, perhaps in /home/username/soft
Download latest PETSc release tarball: petsc-3.0.0-p0.tar.gz
cd /home/username/soft
gunzip -c petsc-3.0.0-p0.tar.gz | tar -xof -
cd petsc-3.0.0-p0
sh/bash shell: PETSC_DIR=$PWD; export PETSC_DIR
csh/tcsh shell: setenv PETSC_DIR $PWD
./config/configure.py (use --help for options or the example usages below)
make all
make test
More specifically :
Quote:
Installing PETSc in /usr/local or /opt where sudo or root previledges are required:
If one wants to install PETSc [with sources] in a common system location like /usr/local or /opt, then sugest creating a dir for PETSc in the required location with user previledges, and then do the PETSc install [as a regular/non-root user]. i.e
sudo mkdir /opt/petsc
sudo chown user:group /opt/petsc
cd /opt/petsc
tar -xzf petsc-3.0.0-p0.tar.gz
cd petsc-3.0.0-p0
./config/configure.py
make
One can also use the gnu prefix-install mode.
[untar PETSc in a non-root regular location - say /home/username]
setenv PETSC_DIR $PWD
After the install is done, one has to switch to using PETSC_DIR=/opt/petsc/petsc-3.0.0-p0. If you've installed PETSc with the --prefix option then you DO NOT use a PETSC_ARCH variable. You should install different configurations using different --prefix names.
So Far, I have set the environment variables, configured with prefix /usr/local, and tried trackinstall with no success...
Like I told you, the detailed error message i do not know by head, by I can post it back here tomorrow... :-)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.