Re: netkit-telnet compile fail. `exit' undeclared in main.cc ?

On 29 Jun 2006, in the Usenet newsgroup comp.os.linux.misc, in article
<1151573045.088711.198830@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>, onionsjk@xxxxxxxxx
wrote:

As an alternative, I decided to use SRPMS, though I am not really used
to rpm. Thanks to you, I could get telnet-0.17-23.src.rpm and could
rebuild telnet.

Depending on your setup, you probably will find things up in
/usr/src/RedHat/ with the tarball and patches in /usr/src/RedHat/SOURCES
and the spec file in /usr/src/RedHat/SPECS/. The .spec file tells how
and in what order to run the patches and what is done to compile, install,
or remove the package. The format is somewhat similar to a Makefile in
concept.

But I found another problem here. "rpmbuild --bb telnet.spec" tries to
patch prior to actual compilation and this patch process fails
depending upon the location where the change occurs in source code.
Some works, some don't. This makes things worse.

Is this your patch, or just the materials that come in the source rpm? As
the source comes out of the box, this should compile exactly the same
binary that you would find in the equivalent .i386.rpm file or equal.
If you are adding your patch, it would have to be added AFTER rpmbuild
patches using the supplied patches.

I am sure there is a generic "telnet source" that is compilable in tar
ball format somewhere.

The basic tarball is in the source rpm. This should be the same as the
basic tarball from uk.linux.org, as well as the unmodified source from any
package manager.

It would appear that you are missing the development packages, or that
the Makefile is not configured for where Red Hat hides things.

I also suspected this but don't know much about this.

Glibc2 is a poor example, but using that - Red Hat 8 should have been
updated to:

glibc-2.3.2-4.80.8.i386.rpm
glibc-2.3.2-4.80.8.i686.rpm
glibc-common-2.3.2-4.80.8.i386.rpm
glibc-debug-2.3.2-4.80.8.i386.rpm
glibc-debug-2.3.2-4.80.8.i686.rpm
glibc-debug-static-2.3.2-4.80.8.i386.rpm
glibc-devel-2.3.2-4.80.8.i386.rpm
glibc-profile-2.3.2-4.80.8.i386.rpm
glibc-utils-2.3.2-4.80.8.i386.rpm

The 'glibc-2.3.2' and 'glibc-common-2.3.2' packages have the parts of the
libraries needed to _run_ compiled binaries. The '-debug' packages are used
when you are debugging the libraries. But that '-devel' is needed when you
are compiling, or building. They have all the headers and .obj stuff you
need for that task. Once the binaries are built/compiled/etc., then you
can remove the -devel package if desired.

Old guy,
.

Relevant Pages

  • RE: Creating RPMS from source without Makefile
    ... Creating RPMS from source without Makefile ... For several applications/tools I'd like to create an RPM to make ... You may want to start with a package less complex than httpd ... "Start with pristine sources; then patch as needed. ...
    (RedHat)
  • Re: Fedora Updates: whole packages vs patches
    ... single Solaris patch can patch more than one package. ... that diff file and original rpm to generate updated rpm. ...
    (Fedora)
  • Re: Make RPMs from .spec and package source tarball? how?
    ... and then make an RPM based on the ATRPMS spec for the package. ... Install the mythtv source package from atrpms. ... Make the changes you need to the sources and prepare a patch. ...
    (Fedora)
  • Re: JRE required - OpenOffice 2 (beta)
    ... > installed Java on my linux computer before. ... I tried to compile a nosrc package and did ... Get the Linux RPM and run it (sh ...
    (Fedora)
  • Re: Fedora Updates: whole packages vs patches
    ... is recreating the base if you remove the patch. ... > location of the original package, and restore the needed parts from there. ... Implementing a tool that could replace changed files inside binary RPM, ... either download a patch, or new RPM. ...
    (Fedora)