I followed the directions in the README files: I ran configure in one case
and make in the other. See my response below.

Thanks for your help

-Roy


Jerry Lynn Kreps wrote:

> Roy Brewer wrote:
> >
> > I've tried to compile two apps recently (xfstt and kpackage) and they
> > both bombed because they couldn't find the file crtbegin.o. This file is
> > on the system, under /usr/lib/gcc-lib/i486-linux/2.7.2.3/crtbegin.o.
> >
> > Am I missing some symbolic link that would set up the directory tree
> > properly? Should I just modify the Makefile or configure files in
> > question to find the right libraries? If so, how do I do this? (I'm
> > obviously fairly new to Linux software development). Isn't there
> > supposed to be a standardized directory structure?
>
> You can modify Makefile, or you could run ./configure and let it make
> the modifications.  Did you run ./configure before you ran make?
> Any text editor can be used to modify Makefile.  I use either MC's edit
> mode or Pico.
> Standardized structure?  If you are trying to modify Makefile to include
> libraries in non-standard locations (which uses the -L switch as apposed
> to the -l switch for libraries in the standard paths) and you haven't
> read/don't know what these switches mean and what the standard paths are
> then you have the cart before the horse.  The -i switch is for libraries
> in /usr/lib and the -L switch is for libraries in other locations.  I
> haven't said anything about the 'shorthand' used to represent the
> libraries: say you have a program called LeastSquares and you are using
> functions found in a static math library, libm.a, which is in /usr/lib.
> You would compile LeastSquares by issuing:
>         cc -o LeastSquares -lm
> Why didn't I include the whole name of the library?  Because libraries
> begin with 'lib' and the shorthand is not to include 'lib' - the switch
> knows to prefix m with 'lib' to get libm.
> How does -l know to append an 'a' and not 'sa' (for shared libraries)?
> Well, see how the topic is growing?  And the questions you're asking
> indicates you haven't even read the fundamentals.
> It time you took a breather from the mail-list server, got a good book
> on compiling and did some practice programming and compiling.  Let me
> recommend "Beginning Linux Programming" and "Practical C++ Programming"
> and "Linux Application Development".  They are at Amazon.com.
> No need to appoligize, we understand.  ;-)
>
> >
> > I'm using SuSE Linux v 6.0 upgraded to kernel 2.2.5, although I didn't
> > upgrade the glibc above its default 2.0.7pre6.
> >
> > Thanks in advance
> > -Roy
> >
>
> --
>
> JLK
> Linux, because it's STABLE, the source code is included, the price is
> right.

--
To get out of this list, please send email to [EMAIL PROTECTED] with
this text in its body: unsubscribe suse-linux-e
Check out the SuSE-FAQ at http://www.suse.com/Support/Doku/FAQ/ and the
archive at http://www.suse.com/Mailinglists/suse-linux-e/index.html

Reply via email to