This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
distributing g++
- From: Bob Rossi <bob_rossi at cox dot net>
- To: gcc at gcc dot gnu dot org
- Date: Fri, 15 Dec 2006 15:00:43 -0500
- Subject: distributing g++
Hi,
I've compiled g++ for mingw with,
../gcc-4.1.1/configure --prefix=/home/bobbybrasko/g++/prefixdir --host=mingw32 \
--target=mingw32 --program-prefix="" \
--program-suffix="-4.1" --with-gcc --with-gnu-ld --with-gnu-as --enable-threads --disable-nls \
--enable-languages=c,c++ --disable-win32-registry --disable-shared --without-x \
--enable-interpreter --enable-hash-synchronization --enable-libstdcxx-debug
Since i've used a prefix, I'm assumming gcc wants to be installed where
I told it to be. I'm wondering 2 things.
What are the standard practices with installing multiple versions of gcc
on a system. I renamed this gcc to be gcc-4.1. However, it looks like it
will still overwrite some files when I do 'make install'. Is this true?
How do people put multiple version on the same machine?
Second, say I wanted to tar up a release of gcc that i've built for
others to use. When the other user downloads and untars the file on
there filesystem in an arbitrary point, I'm assumming it won't work
because it's not in the --prefix=.. directory. Is it possible to get
around this? I would like a user to be able to untar it anywhere, and
have it work just fine. If this is possible, please advise.
Thanks,
Bob Rossi