SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Iy you are using src2pkg, just place the patch beside the sources. I'm surprised you had trouble using src2pkg before as others have had success with emacs-23.x
To manually apply the patch, unpack the sources, then copy the patch into the toplevel of the sources, cd in there and apply the patch from the toplevel. For a plain *.patch or *.diff:
patch -p1 < *.diff
patch -p1 < *.patch
For compressed patches you can unpack them and use like above or:
zcat *.patch.gz | patch -p1
Perhaps Sycamorex ran into the same problem I had with Emacs 23 and src2pkg, where src2pkg stopped the build because Emacs wants to put files in locations other than the standard locations.
I'm away from my home computer and my work's IT department blocks the src2pkg wiki. (Why? Who knows, they also block a lot of the state's department of transportation's web sites -- and I'm a transportation planner!)
The solution for me, I believe, was to use the -ACN switch. However, I modified the src2pkg.conf file by changing AUTO_CONFIG_OPTIONS to =native.
Hmm, I don't find that right now in our emails Drew, but I think it was --sysconfdir which was 'panicking the build. So,
src2pkg -e='--syscofndir=/etc' emacs-23.1.tar.?? shoudl fix it. Or, as you suggest:
src2pkg -ACN emacs-23.1.tar.??
Right, thanks for your replies. This morning I tried to use the src2pkg with the patch and that's what I got:
root@slack64:/home/xtd8865/temp/emmm# src2pkg emacs-23.1.tar.bz2
Found source archive: emacs-23.1.tar.bz2
Deleting old build files - Done
Creating working directories:
Unpacking source archive - Done
Correcting source permissions - Done
Checking for patches - Found
Found configure script - Done
Configuring sources using:
LDFLAGS="-Wl,-L/lib64,-L/usr/lib64" CFLAGS="-O2 -fPIC -m64" ./configure --prefix=/usr --libdir=/usr/lib64
ERROR! Configuring sources has failed!
This may be because of some missing libraries, or you may
need to pass extra options to configure using EXTRA_CONFIGS.
Sorry! No Dependency or Requirements information found.
Notice - Showing short options in a separate xterm.
It did compile nicely when building from source (with the patch) but the icons where still missing.
I'll remove it and perhaps try the cvs version now.
I got the cvs (23.1.90) version and tried to add the patch command to its slackbuild file. It did not work.
Most probably I edited the slackbuild in a wrong way.
What I did then was patching the cvs source and used makepkg to create a slack package. It works fine!!!