Hi! Did anyone tried to compile the cmake 2.8.4 on fedora 14? trying to bootstrap with or without the system libs i receive this:
cmSystemTools.o: In function `cmSystemTools::GuessLibrarySOName(std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::basic_string<char, std::char_traits<char>, std::allocator<char> >&)': cmSystemTools.cxx:(.text+0x49f3): undefined reference to `cmELF::cmELF(char const*)' cmSystemTools.cxx:(.text+0x4a16): undefined reference to `cmELF::GetSOName(std::basic_string<char, std::char_traits<char>, std::allocator<char> >&)' cmSystemTools.cxx:(.text+0x4b6f): undefined reference to `cmELF::~cmELF()' cmSystemTools.cxx:(.text+0x4bc3): undefined reference to `cmELF::~cmELF()' cmSystemTools.o: In function `cmSystemTools::ChangeRPath(std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::basic_string<char, std::char_traits<char>, std::allocator<char> >*, bool*)': cmSystemTools.cxx:(.text+0x4e77): undefined reference to `cmELF::cmELF(char const*)' cmSystemTools.cxx:(.text+0x4eb9): undefined reference to `cmELF::GetRPath()' cmSystemTools.cxx:(.text+0x4ef9): undefined reference to `cmELF::GetRunPath()' cmSystemTools.cxx:(.text+0x53cc): undefined reference to `cmELF::~cmELF()' cmSystemTools.cxx:(.text+0x577e): undefined reference to `cmELF::~cmELF()' cmSystemTools.o: In function `cmSystemTools::RemoveRPath(std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::basic_string<char, std::char_traits<char>, std::allocator<char> >*, bool*)': cmSystemTools.cxx:(.text+0x5985): undefined reference to `cmELF::cmELF(char const*)' cmSystemTools.cxx:(.text+0x59b1): undefined reference to `cmELF::GetRPath()' cmSystemTools.cxx:(.text+0x59e0): undefined reference to `cmELF::GetRunPath()' cmSystemTools.cxx:(.text+0x5a60): undefined reference to `cmELF::GetDynamicEntryCount() const' cmSystemTools.cxx:(.text+0x5b54): undefined reference to `cmELF::GetDynamicEntryPosition(int) const' cmSystemTools.cxx:(.text+0x5b88): undefined reference to `cmELF::GetDynamicEntryPosition(int) const' cmSystemTools.cxx:(.text+0x5bbd): undefined reference to `cmELF::GetDynamicEntryPosition(int) const' cmSystemTools.cxx:(.text+0x5c87): undefined reference to `cmELF::ReadBytes(unsigned long, unsigned long, char*) const' cmSystemTools.cxx:(.text+0x5cfb): undefined reference to `cmELF::~cmELF()' cmSystemTools.cxx:(.text+0x5ff6): undefined reference to `cmELF::~cmELF()' cmSystemTools.o: In function `cmSystemTools::CheckRPath(std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)': cmSystemTools.cxx:(.text+0x6059): undefined reference to `cmELF::cmELF(char const*)' cmSystemTools.cxx:(.text+0x6065): undefined reference to `cmELF::GetRPath()' cmSystemTools.cxx:(.text+0x607c): undefined reference to `cmELF::GetRunPath()' cmSystemTools.cxx:(.text+0x60e6): undefined reference to `cmELF::~cmELF()' cmSystemTools.cxx:(.text+0x60fe): undefined reference to `cmELF::~cmELF()' cmSystemTools.o: In function `cmELF::operator bool() const': cmSystemTools.cxx:(.text._ZNK5cmELFcvbEv[cmELF::operator bool() const]+0x14): undefined reference to `cmELF::Valid() const' collect2: ld returned 1 exit status gmake: *** [cmake] Error 1
the thing is that i really need cmake 2.8.4 .. i also already tried the rpm of f15 .. but i receive the error: [root@sev cmake]# rpm -ivh cmake-2.8.4-1.fc15.x86_64.rpm error: Failed dependencies: libstdc++.so.6(GLIBCXX_3.4.15)(64bit) is needed by cmake-2.8.4-1.fc15.x86_64
even thou: [root@sev cmake]# locate libstdc++.so.6 /usr/lib64/libstdc++.so.6 /usr/lib64/libstdc++.so.6.0.14 /usr/share/gdb/auto-load/usr/lib64/libstdc++.so.6.0.14-gdb.py /usr/share/gdb/auto-load/usr/lib64/libstdc++.so.6.0.14-gdb.pyc /usr/share/gdb/auto-load/usr/lib64/libstdc++.so.6.0.14-gdb.pyo
can anyone help me with some suggestion? Thanks! Adrian
On Sun, 6 Mar 2011 14:54:06 +0200 Adrian Sevcenco Adrian.Sevcenco@cern.ch wrote:
Hi! Did anyone tried to compile the cmake 2.8.4 on fedora 14? trying to bootstrap with or without the system libs i receive this:
[snip]
can anyone help me with some suggestion?
I too am running F14 x86_64. I downloaded the source, unpacked it, changed to the directory, ran ./configure (which runs ./bootstrap), and when that completed ran gmake. Everything compiled just fine. I ran the resulting binary without a target and it seemed to run just fine. I have accumulated lots of devel packages over the years, though.
I think you are missing a header file. Which one? Ha! I am unfamiliar with cmake, so I don't know where to find such information from the configuration output (usually it is in config.log). From the error output you provided, I wonder if you aren't missing elf.h. But that is just a guess.
You could try a yum groupinstall development-tools development-libs as a shotgun approach to try to pick up the missing header file. If you want to get everything, you could put into /etc/yum.conf the line group_package_types=optional, default, mandatory
Alternatively, run ldd on the currently installed binaries of cmake for F14, and see which libraries are used. Then install the -devel versions of those libraries' packages.
On Sun, Mar 6, 2011 at 11:02 AM, stan gryt2@q.com wrote:
On Sun, 6 Mar 2011 14:54:06 +0200 Adrian Sevcenco Adrian.Sevcenco@cern.ch wrote:
Hi! Did anyone tried to compile the cmake 2.8.4 on fedora 14? trying to bootstrap with or without the system libs i receive this:
[snip]
can anyone help me with some suggestion?
I too am running F14 x86_64. I downloaded the source, unpacked it, changed to the directory, ran ./configure (which runs ./bootstrap), and when that completed ran gmake. Everything compiled just fine. I ran the resulting binary without a target and it seemed to run just fine. I have accumulated lots of devel packages over the years, though.
I think he's talking about cmake, not blender :)
The best thing may be to download the source from a source RPM:
http://koji.fedoraproject.org/koji/buildinfo?buildID=229248
The link is for 2.8.4 for Fedora 15 but I've found you can often take the source RPM and recompile it for your version with little or no issue.
The src RPM will have a spec file with all the dependencies listed or you can let yum-builddep handle it for you
$ yum-builddep /path/to/src/rpm
Then install the rpm as YOUR USER!!! NEVER AS ROOT!!!
Source RPMs are not designed to be installed system wide. They will unpack to ~/rpmbuild. I actually use a separate build account so a rogue package doesn't destroy my account.
(as you or another unprivileged user) $ rpm -ivh <source rpm>
Then try:
$ rpmbuild -bb ~/rpmbuild/SPECS/cmake.spec
By default this will try to build a binary package for your current distribution (F14) and architecture (x86_64)
See the following links for more detailed instructions:
http://www.g-loaded.eu/2006/04/05/how-to-build-rpm-packages-on-fedora/ http://fedoraproject.org/wiki/Docs/Drafts/BuildingPackagesGuide
Richard
On 03/06/2011 07:20 PM, Richard Shaw wrote:
On Sun, Mar 6, 2011 at 11:02 AM, stan gryt2@q.com wrote:
On Sun, 6 Mar 2011 14:54:06 +0200 Adrian Sevcenco Adrian.Sevcenco@cern.ch wrote:
Hi! Did anyone tried to compile the cmake 2.8.4 on fedora 14? trying to bootstrap with or without the system libs i receive this:
[snip]
can anyone help me with some suggestion?
I too am running F14 x86_64. I downloaded the source, unpacked it, changed to the directory, ran ./configure (which runs ./bootstrap), and when that completed ran gmake. Everything compiled just fine. I ran the resulting binary without a target and it seemed to run just fine. I have accumulated lots of devel packages over the years, though.
I think he's talking about cmake, not blender :)
The best thing may be to download the source from a source RPM:
http://koji.fedoraproject.org/koji/buildinfo?buildID=229248
The link is for 2.8.4 for Fedora 15 but I've found you can often take the source RPM and recompile it for your version with little or no issue.
The src RPM will have a spec file with all the dependencies listed or you can let yum-builddep handle it for you
$ yum-builddep /path/to/src/rpm
Then install the rpm as YOUR USER!!! NEVER AS ROOT!!!
Source RPMs are not designed to be installed system wide. They will unpack to ~/rpmbuild. I actually use a separate build account so a rogue package doesn't destroy my account.
(as you or another unprivileged user) $ rpm -ivh <source rpm>
Then try:
$ rpmbuild -bb ~/rpmbuild/SPECS/cmake.spec
By default this will try to build a binary package for your current distribution (F14) and architecture (x86_64)
See the following links for more detailed instructions:
http://www.g-loaded.eu/2006/04/05/how-to-build-rpm-packages-on-fedora/ http://fedoraproject.org/wiki/Docs/Drafts/BuildingPackagesGuide
Thanks a lot for info .. i will try to do it and come back with results Adrian
On 03/06/11 19:20, Richard Shaw wrote:
On Sun, Mar 6, 2011 at 11:02 AM, stangryt2@q.com wrote:
On Sun, 6 Mar 2011 14:54:06 +0200 Adrian SevcencoAdrian.Sevcenco@cern.ch wrote:
Hi! Did anyone tried to compile the cmake 2.8.4 on fedora 14? trying to bootstrap with or without the system libs i receive this:
[snip]
can anyone help me with some suggestion?
I too am running F14 x86_64. I downloaded the source, unpacked it, changed to the directory, ran ./configure (which runs ./bootstrap), and when that completed ran gmake. Everything compiled just fine. I ran the resulting binary without a target and it seemed to run just fine. I have accumulated lots of devel packages over the years, though.
I think he's talking about cmake, not blender :)
The best thing may be to download the source from a source RPM:
http://koji.fedoraproject.org/koji/buildinfo?buildID=229248
The link is for 2.8.4 for Fedora 15 but I've found you can often take the source RPM and recompile it for your version with little or no issue.
The src RPM will have a spec file with all the dependencies listed or you can let yum-builddep handle it for you
$ yum-builddep /path/to/src/rpm
Then install the rpm as YOUR USER!!! NEVER AS ROOT!!!
Source RPMs are not designed to be installed system wide. They will unpack to ~/rpmbuild. I actually use a separate build account so a rogue package doesn't destroy my account.
(as you or another unprivileged user) $ rpm -ivh<source rpm>
Then try:
$ rpmbuild -bb ~/rpmbuild/SPECS/cmake.spec
By default this will try to build a binary package for your current distribution (F14) and architecture (x86_64)
Everything worked! Thanks! Adrian
On Mon, Mar 7, 2011 at 8:29 AM, Adrian Sevcenco Adrian.Sevcenco@cern.ch wrote:
On 03/06/11 19:20, Richard Shaw wrote:
On Sun, Mar 6, 2011 at 11:02 AM, stangryt2@q.com wrote:
On Sun, 6 Mar 2011 14:54:06 +0200 Adrian SevcencoAdrian.Sevcenco@cern.ch wrote:
Hi! Did anyone tried to compile the cmake 2.8.4 on fedora 14? trying to bootstrap with or without the system libs i receive this:
[snip]
can anyone help me with some suggestion?
I too am running F14 x86_64. I downloaded the source, unpacked it, changed to the directory, ran ./configure (which runs ./bootstrap), and when that completed ran gmake. Everything compiled just fine. I ran the resulting binary without a target and it seemed to run just fine. I have accumulated lots of devel packages over the years, though.
I think he's talking about cmake, not blender :)
The best thing may be to download the source from a source RPM:
http://koji.fedoraproject.org/koji/buildinfo?buildID=229248
The link is for 2.8.4 for Fedora 15 but I've found you can often take the source RPM and recompile it for your version with little or no issue.
The src RPM will have a spec file with all the dependencies listed or you can let yum-builddep handle it for you
$ yum-builddep /path/to/src/rpm
Then install the rpm as YOUR USER!!! NEVER AS ROOT!!!
Source RPMs are not designed to be installed system wide. They will unpack to ~/rpmbuild. I actually use a separate build account so a rogue package doesn't destroy my account.
(as you or another unprivileged user) $ rpm -ivh<source rpm>
Then try:
$ rpmbuild -bb ~/rpmbuild/SPECS/cmake.spec
By default this will try to build a binary package for your current distribution (F14) and architecture (x86_64)
Everything worked! Thanks! Adrian
I'm glad it was easy! If you decide you like building your own packages I would check out mock[1]. It is a fancy python script which will build the package in a chroot environment. It makes sure (among other things) that you have the correct BuildRequires: in the spec file by installing only those packages in the spec file into the chroot environment. It downloads and installs all the -devel packages which can take a while the first time but they are cached for future builds.
Also, checkout rpmlint[2]. It checks the resultant RPMs for typical issues and errors. Both are required for formal acceptance of a package into the Fedora repos.
Richard
[1] http://fedoraproject.org/wiki/Projects/Mock [2] http://fedoraproject.org/wiki/PackagingGuidelines#Use_rpmlint
On 03/07/11 17:06, Richard Shaw wrote:
[snip]
I'm glad it was easy! If you decide you like building your own packages I would check out mock[1]. It is a fancy python script which will build the package in a chroot environment. It makes sure (among other things) that you have the correct BuildRequires: in the spec file by installing only those packages in the spec file into the chroot environment. It downloads and installs all the -devel packages which can take a while the first time but they are cached for future builds.
Also, checkout rpmlint[2]. It checks the resultant RPMs for typical issues and errors. Both are required for formal acceptance of a package into the Fedora repos.
Thanks! with this info i might dare to venture into giving back something to community.. :) Adrian
Richard
[1] http://fedoraproject.org/wiki/Projects/Mock [2] http://fedoraproject.org/wiki/PackagingGuidelines#Use_rpmlint
So far i have no problem with cmake usage ... but i check it out with rpmlint and i have this .. are this errors ok?
[root@sev ~]# rpmlint cmake cmake.x86_64: W: spelling-error %description -l en_US makefiles -> make files, make-files, makefast cmake.x86_64: W: spelling-error %description -l en_US pre -> per, ore, pee cmake.x86_64: W: devel-file-in-non-devel-package /usr/share/cmake/Modules/CheckForPthreads.c cmake.x86_64: E: non-executable-script /usr/share/cmake/Modules/CPack.RuntimeScript.in 0644L /bin/sh cmake.x86_64: W: devel-file-in-non-devel-package /usr/share/cmake/Modules/CMakeCXXCompilerABI.cpp cmake.x86_64: W: devel-file-in-non-devel-package /usr/share/cmake/Modules/CMakeTestNMakeCLVersion.c cmake.x86_64: W: devel-file-in-non-devel-package /usr/share/cmake/Modules/FortranCInterface/Verify/VerifyC.c cmake.x86_64: W: devel-file-in-non-devel-package /usr/share/cmake/Modules/TestForAnsiForScope.cxx cmake.x86_64: W: devel-file-in-non-devel-package /usr/share/cmake/Modules/DummyCXXFile.cxx cmake.x86_64: W: devel-file-in-non-devel-package /usr/share/cmake/Modules/FortranCInterface/my_module_.c cmake.x86_64: W: devel-file-in-non-devel-package /usr/share/cmake/Modules/CMakeTestForFreeVC.cxx cmake.x86_64: W: devel-file-in-non-devel-package /usr/share/cmake/Modules/CMakeTestGNU.c cmake.x86_64: E: non-executable-script /usr/share/cmake/Modules/SquishRunTestCase.sh 0644L /bin/sh cmake.x86_64: W: devel-file-in-non-devel-package /usr/share/cmake/Modules/CMakeCompilerABI.h cmake.x86_64: W: devel-file-in-non-devel-package /usr/share/cmake/Modules/TestForANSIStreamHeaders.cxx cmake.x86_64: W: devel-file-in-non-devel-package /usr/share/cmake/include/cmCPluginAPI.h cmake.x86_64: W: devel-file-in-non-devel-package /usr/share/cmake/Modules/FortranCInterface/mymodule_.c cmake.x86_64: W: devel-file-in-non-devel-package /usr/share/cmake/Modules/FortranCInterface/Verify/VerifyCXX.cxx cmake.x86_64: W: devel-file-in-non-devel-package /usr/share/cmake/Modules/CheckFunctionExists.c cmake.x86_64: W: devel-file-in-non-devel-package /usr/share/cmake/Modules/CheckVariableExists.c cmake.x86_64: W: devel-file-in-non-devel-package /usr/share/cmake/Modules/FortranCInterface/Verify/main.c cmake.x86_64: E: non-executable-script /usr/share/cmake/Modules/CPack.STGZ_Header.sh.in 0644L /bin/sh cmake.x86_64: W: devel-file-in-non-devel-package /usr/share/cmake/Modules/TestForSTDNamespace.cxx cmake.x86_64: W: devel-file-in-non-devel-package /usr/share/cmake/Modules/CMakeCCompilerABI.c cmake.x86_64: W: devel-file-in-non-devel-package /usr/share/cmake/Modules/TestForSSTREAM.cxx cmake.src: W: spelling-error %description -l en_US makefiles -> make files, make-files, makefast cmake.src: W: spelling-error %description -l en_US pre -> per, ore, pee cmake.src:6: W: macro-in-comment %{nil} 3 packages and 0 specfiles checked; 3 errors, 25 warnings.
Thanks, Adrian
On Mon, Mar 7, 2011 at 9:27 AM, Adrian Sevcenco Adrian.Sevcenco@cern.ch wrote:
So far i have no problem with cmake usage ... but i check it out with rpmlint and i have this .. are this errors ok?
[root@sev ~]# rpmlint cmake cmake.x86_64: W: spelling-error %description -l en_US makefiles -> make files, make-files, makefast cmake.x86_64: W: spelling-error %description -l en_US pre -> per, ore, pee cmake.x86_64: W: devel-file-in-non-devel-package /usr/share/cmake/Modules/CheckForPthreads.c cmake.x86_64: E: non-executable-script /usr/share/cmake/Modules/CPack.RuntimeScript.in 0644L /bin/sh cmake.x86_64: W: devel-file-in-non-devel-package /usr/share/cmake/Modules/CMakeCXXCompilerABI.cpp cmake.x86_64: W: devel-file-in-non-devel-package /usr/share/cmake/Modules/CMakeTestNMakeCLVersion.c cmake.x86_64: W: devel-file-in-non-devel-package /usr/share/cmake/Modules/FortranCInterface/Verify/VerifyC.c cmake.x86_64: W: devel-file-in-non-devel-package /usr/share/cmake/Modules/TestForAnsiForScope.cxx cmake.x86_64: W: devel-file-in-non-devel-package /usr/share/cmake/Modules/DummyCXXFile.cxx cmake.x86_64: W: devel-file-in-non-devel-package /usr/share/cmake/Modules/FortranCInterface/my_module_.c cmake.x86_64: W: devel-file-in-non-devel-package /usr/share/cmake/Modules/CMakeTestForFreeVC.cxx cmake.x86_64: W: devel-file-in-non-devel-package /usr/share/cmake/Modules/CMakeTestGNU.c cmake.x86_64: E: non-executable-script /usr/share/cmake/Modules/SquishRunTestCase.sh 0644L /bin/sh cmake.x86_64: W: devel-file-in-non-devel-package /usr/share/cmake/Modules/CMakeCompilerABI.h cmake.x86_64: W: devel-file-in-non-devel-package /usr/share/cmake/Modules/TestForANSIStreamHeaders.cxx cmake.x86_64: W: devel-file-in-non-devel-package /usr/share/cmake/include/cmCPluginAPI.h cmake.x86_64: W: devel-file-in-non-devel-package /usr/share/cmake/Modules/FortranCInterface/mymodule_.c cmake.x86_64: W: devel-file-in-non-devel-package /usr/share/cmake/Modules/FortranCInterface/Verify/VerifyCXX.cxx cmake.x86_64: W: devel-file-in-non-devel-package /usr/share/cmake/Modules/CheckFunctionExists.c cmake.x86_64: W: devel-file-in-non-devel-package /usr/share/cmake/Modules/CheckVariableExists.c cmake.x86_64: W: devel-file-in-non-devel-package /usr/share/cmake/Modules/FortranCInterface/Verify/main.c cmake.x86_64: E: non-executable-script /usr/share/cmake/Modules/CPack.STGZ_Header.sh.in 0644L /bin/sh cmake.x86_64: W: devel-file-in-non-devel-package /usr/share/cmake/Modules/TestForSTDNamespace.cxx cmake.x86_64: W: devel-file-in-non-devel-package /usr/share/cmake/Modules/CMakeCCompilerABI.c cmake.x86_64: W: devel-file-in-non-devel-package /usr/share/cmake/Modules/TestForSSTREAM.cxx cmake.src: W: spelling-error %description -l en_US makefiles -> make files, make-files, makefast cmake.src: W: spelling-error %description -l en_US pre -> per, ore, pee cmake.src:6: W: macro-in-comment %{nil} 3 packages and 0 specfiles checked; 3 errors, 25 warnings.
I wouldn't worry too much if it works. It's really the job of the developer/package maintainer to fix these types of things but it is good to know. They of course almost always welcome patches but not everyone can fix things.
You can try reporting it as a bug against F14 and they may do something about it or they could just say it's not expected to build on F14 and close it as WONTFIX since it's scheduled for F15 but it doesn't hurt.
Something I've had to learn the hard way is try not to take it personally if they're a little curt with you.They're pretty busy and sometimes forget that not everyone is an expert at this.
The actual errors "E:" should probably be fixed. Either a script should be executable or not and should have the correct permissions.
Richard
stan wrote:
I have accumulated lots of devel packages over the years, though.
I just found out that yum's --installroot is _not_ meant for installing in a non-default location; this flag, along with rpm's --root flag, are for maintaining separate installations of linux (https://bugzilla.redhat.com/show_bug.cgi?id=682827). So, regarding your accumulated devel packages, do you usually install with yum/rpm or build (i.e., configure --prefix, make, make install) them?
Since relocation is not supported with yum/rpm, how do you manage space? Also, what's the size of your partitions?
Thanks,
On Mon, 7 Mar 2011 12:05:09 -0800 "Suresh Govindachar" sgovindachar@yahoo.com wrote:
stan wrote:
I have accumulated lots of devel packages over the years, though.
I just found out that yum's --installroot is _not_ meant for installing in a non-default location; this flag, along with rpm's --root flag, are for maintaining separate installations of linux (https://bugzilla.redhat.com/show_bug.cgi?id=682827). So, regarding your accumulated devel packages, do you usually install with yum/rpm or build (i.e., configure --prefix, make, make install) them?
I always install include files, -devel packages, using yum. I can't remember a time that I was compiling and needed to install another package from source for dependency because it wasn't already in Fedora. If I did have to I would create a separate directory for it in my user space, compile it, and then change the make file in the app I was working on to add the library location and include location (-I -l, if I recall the gcc options correctly) by pointing to that directory. It's possible to do that with the configuration file, but for one offs I think it is too much trouble. Or you can install them under the /usr/local hierarchy, which is outside rpm and yum control, and tell ldconfig to include them in the system libraries that are scanned. You would still have to add the include directive for the include files though.
Since relocation is not supported with yum/rpm, how do you manage space? Also, what's the size of your partitions?
The /usr/include directory (where all the header files are stored from -devel packages) is about 480 MB. The root partition is 250 GB. I don't really manage the space. Since hard disk is so cheap, I don't even worry about it. I think a 2 Terabyte (2000 GB) sata disk is about $100 US now, though I haven't checked lately. I have a 1TB I bought for $70 US some time ago.
Several versions ago, I was going to build an up to date set of CDs to use to upgrade an old 586 computer. For that I used mock as the build tool. I vaguely recall having some problems getting it all working, and I ended up doing a network install, which worked great. Actually, I used the network to install only the base system, and the CDs I built to install all the packages I wanted on top of it. I can't remember if I used them directly as a repository, or had to create a local repository on hard disk.
When I'm going to upgrade versions, I just use another partition to do a fresh install, overwriting the old version that was there. I keep separate partitions for all my home and permanent stuff, and just link them in from the new home directory. I mount them using fstab. That way I don't run into any problem with new and old configuration files. This technique also means that if things don't go well, I've still got a perfectly functioning fall back in the previous version.