Gcc

Gcc

Post by Nima Negahba » Thu, 30 Apr 1998 04:00:00



I am trying to compile a program like windowmaker for the first time I
am reletivley new to Linux and I figure I have to stop using RPM as a
crutch, and when do make I get either one of two things gcc cannot
create executables and or I am missing a whole bunch of headers.

thanks in advance


thank you

 
 
 

Gcc

Post by rick0.. » Wed, 06 May 1998 04:00:00


: I am trying to compile a program like windowmaker for the first time I
: am reletivley new to Linux and I figure I have to stop using RPM as a
: crutch, and when do make I get either one of two things gcc cannot
: create executables and or I am missing a whole bunch of headers.

As you've found out, RPM (or .deb) is incredibly useful to get a
system up and running, but has some long-term disadvantages.  One
useful step in weaning yourself off is to use SRPM packages.
Those are the versions with extension .src.rpm (instead of .i386.rpm,
or whatever).   When you "install" them, you get (usually) several
files created under /usr/src/redhat/SOURCES/:

   -- one or more .tar.gz (or .Z) files.  This is the original source
      archive
   -- one or more patch file.  These can be applied to the aforementioned
      source archive to "RedHat-ise" it, using the "patch" utility.
   -- possibly, some extra documentation or example files

Having all those components allows you to study the source, modify
things like installation locations, and yet still get the benefit of
the patches intended to make the package install correctly on most
Red Hat-type systems.  So, you get most of the advantages of binary
RPMs, plus most of those from using source "tarballs" (archives),
including compilation against your own libs.

If you're indeed missing a number of headers, this probably indicates
that you're missing the related libraries.  Next time you reinstall
Linux, you might want to make a point of installing all available
libs, except those you're absolutely sure you'll not be needing.  I
find this to be a good policy.


Nope.  This is Usenet.  You find the replies here, because people
send them here to benefit others as well as you.  With DejaNews
available, nobody has an excuse for needing personally-delivered
copies, any more.

--
Cheers,                 "Heedless of grammar, they all cried 'It's him!'"
Rick Moen                       -- R.H Barham, _Misadventure at Margate_


 
 
 

1. RH6.0 - i386-glibc20-linux-gcc or i386-redhat-linux-gcc

I notice that the RH6.0 has two gcc compilers in

  /usr/bin/i386-glibc20-linux-gcc
  /usr/bin/i386-redhat-linux-gcc

and the default one is /usr/bin/i386-redhat-linux-gcc. Anyone
know what is different between them? Because I have found some
programs fail to be compiled using the redhat one but successful
if using /usr/bin/i386-glibc20-linux-gcc.

Thanks

david

2. Is there an lpd that is multithreaded for remote printers?

3. gcc 2.96 vs. gcc 3.2: namespace, template incompatability

4. Dual bootup with linux and win98. How?

5. gcc 4.1.1 build under Intel Solaris 10 does not build gcc

6. Ultra ATA/100 with Linux

7. HOWTO build/install GCC 3.1 from SRPM w/o replacing GCC 2.96 ?

8. job control for a shell under linux

9. gcc-2.96/RH7,3 .vs gcc-3.2/RH8.0 portability issues

10. Upgrade gcc 2.96-98 to gcc 3.2-7 on Redhat 7.2

11. gcc 2.8.1 vs gcc 2.95.3 optimization on Sparc V8

12. GCC-2.8.0 or GCC-2.8.1(alpha?)

13. Patch for kernel with new gcc (was Re: GCC-2.7.1...)