[Techtalk] Install went wrong

[Andrew]

Jen V, 

	That/this helps a lot. Few of my readings give in *plain* language what
is happening. For me this is a slow and long learning process. Can I
simply trash the the compiled stuff(?) and unpack a new targz? Or will
that leave "stuff" around in other folders?  Put another way, does
./configure put stuff in other directories or does that happen with
"make" or  only with "make install"? 
  
> Then you will need to read the INSTALL file and find the script
> (usually a make script similar to 'make clean') that gets read of the
> detritus of failed installation attempts, run it, then run the
> configure/make/make install sequence again..... 
> Does this help?

	How is the weather where you are? Dry & warm? I am still a bit dazzeled
by the ability to "talk" to strangers from all over the world. 

 	Thank you,
	Andrew

On 10 Nov 2002 14:56:21 +1100
Jenn Vesperman <jenn at anthill.echidna.id.au> wrote:

> On Sun, 2002-11-10 at 02:49, Andrew wrote:
> > Hi All,
> > 
> > 	I bet there is someone here who can tell what went wrong.  And
> > 	where.
> > And possibly what to do about it. 
> 
> Others have told you what to do about it, so I'll tell you what went
> wrong. :)
> 
> (rough guide: pure-sysadmin types know how to fix this sort of stuff.
> pure-programmer types know what is wrong. Blends know both.)
> 
> The first thing you did was run 'configure', which is a script that
> determines what's in your system and writes a file called 'config.h'
> which is read by the next stage and tells it which options to use.
> 
> > [root at Linux1a korinoco-0.2.1]# make
> > make  all-recursive
> > make[1]: Entering directory `/home/andrew/Desktop/DWloaded
> > progs/K-wireless/korinoco-0.2.1'
> > Making all in korinoco
> > make[2]: Entering directory `/home/andrew/Desktop/DWloaded
> > progs/K-wireless/korinoco-0.2.1/korinoco'
> > c++ -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/lib/qt2/include
> > -I/usr/X11R6/include
> >  -O2 -fno-exceptions -fno-check-new  -c stuff.cpp
> > In file included from stuff.cpp:18:
> > stuff.h:6:28: arts/iomanager.h: No such file or directory
> > stuff.h:7:29: arts/dispatcher.h: No such file or directory
> > stuff.cpp:22:27: arts/artsflow.h: No such file or directory
> > stuff.cpp:23:26: arts/connect.h: No such file or directory
> > stuff.cpp:24:28: arts/iomanager.h: No such file or directory
> > stuff.cpp:25:33: arts/referenceclean.h: No such file or directory
> > make[2]: *** [stuff.o] Error 1
> > make[2]: Leaving directory `/home/andrew/Desktop/DWloaded
> > progs/K-wireless/korinoco-0.2.1/korinoco'
> > make[1]: *** [all-recursive] Error 1
> > make[1]: Leaving directory `/home/andrew/Desktop/DWloaded
> > progs/K-wireless/korinoco-0.2.1'
> > make: *** [all-recursive-am] Error 2
> 
> Make is a tool for compiling or building source programs into
> executables. (Make doesn't actually do it, but you can write 'make
> scripts' that list which files must be present and what tasks must be
> performed. Make scripts are often also used for installation.)
> 
> So make read the config.h, read it's script file (Makefile, usually),
> and started trying to compile the source code.
> In the source files stuff.h and stuff.cpp, the source code mentioned
> that it needed the 'header files' for various arts packages. But Make
> couldn't find them, so it reported the error and failed.
> 
> The make install failed because the make had failed - the code wasn't
> completely compiled.
> 
> Header files are files used in C to declare what a function is like.
> If the header files are missing, the files that actually contain those
> functions will probably also be missing. (And if your program needs
> the headers, it almost always needs the functions, too.)
> 
> In Debian, and I assume in RedHat and others, the 'you can compile
> against this' version of a package is different from the 'you can use
> this' version. In Debian, the compile-against package for foo is
> usually called foo-devel.
> 
> You need to find the package that contains 'artsflow.h' and the other
> files, and download those. Look for -devel packages.
> 
> Then you will need to read the INSTALL file and find the script
> (usually a make script similar to 'make clean') that gets read of the
> detritus of failed installation attempts, run it, then run the
> configure/make/make install sequence again.
> 
> 
> Does this help?
> 
> 
> 
> Jenn V.
> -- 
>     "Do you ever wonder if there's a whole section of geek culture 
>         	you miss out on by being a geek?" - Dancer.
> 
> jenn at anthill.echidna.id.au     http://anthill.echidna.id.au/~jenn/
> 
> 
> _______________________________________________
> Techtalk mailing list
> Techtalk at linuxchix.org
> http://mailman.linuxchix.org/mailman/listinfo/techtalk