Sorry - I seem to have a knack for confusing people.
I think I'm going to quit posting here again because of that - my fault; not yours.
Quote:
Originally Posted by chaz_bro1972
Ok, when i installed fox, there were warnings, but it kept going.
|
Warnings are usually just that - warnings. So that's probably nothing to worry about.
Quote:
it did install. so maybe its the fact its in the /opt directory. I am new to things... and i do get things wrong. where am i to download files... then install them from - be explicit please.
|
Everybody gets things wrong - even the kernel devs have had a few 'brown paper bag' releases (means very embarrassing goofs). Okay - there are two things to distinguish here: (1) where you are installing *from* and where the source code *is*, (2) where you are installing *to* and where the binaries produced from the source *will go*. So the fact that you have the source code in /opt and are installing from there is not a problem at all. Just unusual, so I was wondering if you were also installing *to* /opt. In that case, as I said, you'd need to add that library path to ld.so.conf.
Quote:
How do i 'point to it with LDFLAGS'?
|
As an example, 'LDFLAGS=-L/opt/lib ./configure && make && make install', I believe. Basically, this is putting something into the environment by assigning a value to a variable which the toolchain used to build packages will look for and modify their behavior accordingly.
Quote:
Packaged it (dont know what u mean)? I just do the normal steps for source code install:
1) # tar zxvf (or jxvf) <file>.tar.gz (or tar.bz2)
2) # cd ./<directory>
3) <read INSTALL &/or README>
4) # ./configure --help
5) # ./configure <whatever it needs>
6) # make
7) # make install
|
Well, Slackware is composed of *tgz packages, such as bash-3.2.015-i486-1 and these are built by creating a buildscript which basically does the steps you outline above and then calls the 'makepkg' script (which is part of the pkgtools package). This makes it easy to add, remove, rebuild, etc., programs. Some people build their own packages just like that (myself included) and some use various third party tools like checkinstall that do somewhat similar things.
Incidentally, tar versions >= 1.15 don't require the z or j flags (though it certainly doesn't hurt and is good for backware compatibility) so if you don't need them, you can skip them. I also don't have much use for the verbose flag except in specific cases. Steps 3 & 4 you describe are very important - many people skip those.
Quote:
should i (when installing fox)?:
# ./configure --prefix=/usr --exec-prefix=/usr
|
You could - as I say, if you do './configure' that should be exactly the same as doing './configure --prefix=/usr/local'. Both xfe and fox should do this and so xfe should have no trouble finding the fox library and building. But stock Slackware packages (and most 3rd party packages) are built with './configure --prefix=/usr'. This should also work, but shouldn't work any 'better' than /usr/local. So, as I say, I was reduced to wondering if fox had installed at all, or if what you had actually issued was something like './configure --prefix=/opt'. If you had done that, xfe would not be likely to find fox.
Quote:
Are you telling me there is 2 different kinds of paths? now i am really confused. Thanks... thanks a lot.
|
Well, if it's confusing, ignore it for now, but there are all kinds of paths - for instance, I get:
Code:
:set | awk -F= '/PATH/{ print $1 }'
CHOICESPATH
MANPATH
PATH
PKG_CONFIG_PATH
manpath
The first is cruft from a file manager I set to /dev/null (it now uses XDG stuff) and the second is where the 'man' command looks for documentation, the third is where binaries/scripts are looked for, and the fourth is where the *pc files live, which are used to pass some of the library/include values we've been talking about. But when people say plain 'path' they generally mean the search path for executable binaries and scripts. Like I say, if this helps great and, if not, ignore it.
Anyway - if you didn't pass an argument of something like '--prefix=/opt' to configure, and 'ls /usr/local/lib/libFOX*' returns a few files, I have no idea what's wrong, because xfe should find that. If not, do either an 'updatedb' and the 'locate libFOX' or do a 'find / -name '*libFOX*''. (This is another reason for building packages - you can see where stuff is going before you install it and if you forget and need to find out again later, you can just grep /var/log/packages.) And if you don't find it, fox didn't install after all and, if you find it somewhere weird, take one or more of the steps we've mentioned to fix it.
And as far as generalized troubleshooting, always pay careful attention to error messages, paste them into a search engine if needed, check the relevant man pages if you know which ones, or try 'man -k' if you don't.
Hope something in here helps.