Hi-

I recently went through the process of getting emacs from gnu site and doing a custom build, and I also added mu4e for emacs an email client. My question is I think fedora already had emacs on there. When I did the build (.tar.gz) it was complaining of missing certain things when I ran ./configure. How come I had to install more packages to get emacs built from a different version off gnu site? How do they put emacs kde in the repository with less software required? I think I had to add what they call development libraries.

I do have emacs and mu4e up and running awesomely, but I am just curious.

Thanks for any insight/help!

3rdshiftcoder

Hi-

I just thought of how they might do it. Maybe when they build it they can put it out there 'already built' without needing to include everything else that I need to build it from source. Is that right?

thanks,
3rdshiftcoder

Hi-

I will try out installing from the package manager and uninstalling emacs from source with make uninstall. I think it was unecessary to build from source when I couldn't get emacs 2.4.5 to work with mu4e. I found out that there was a newer version of mu4e and worked through the steps of building that new version with build tools I was unfamiliar with. So I can have a complete understanding, I will uninstall the source build and reinstall emacs from the package manager. If it works, I will list what changes I have been making and start undoing them with the package manager. I am not in a big hurry to do all this but I think I should go through the steps of checking out if it can be done.

I am closing this thread as solved because it is kind of quiet today and no one replied. I think I am correct so thread is closed and 'solved'.

thanks

No need to build from source. If you did build from source, create a binary package from it rather than use make install.

Binary distributions will not be able to track a make install and you will end up with clutter, orphaned files.

Also, if you can't satisfy dependencies it's likely because your missing them due to the fact that you don't have them installed or that they are the wrong versions. This is another reason to use you binary distributions repository to install software and rebuild it from repo sources, rather than to try and build upstream sources from source.

Yes ,there are exceptions to these statements, but generally speaking they are accurate.

1 members found this post helpful.

Hi mralk3-

Thanks for the cool tip. I will read how to make a binary package from source rather than make install tomorrow. I have to go to bed and get ready for work.

Somehow I crashed my system when fooling around with folderview for more than one desktop. I thought I read that you could have more than one folderview per desktop. That is what I was trying to set up and all of the sudden bam I had a system that didn't work. I am glad I took the time to partition and mount a home directory before. I didn't format it and everything is okay except I had to reinstall the system partition and format.

When I reinstalled I did build one from source with make install but it was a small source installl not involving a lot of dependencies. I am interested in doing further reading on your post.

thanks,
3rdshiftcoder