This is the mail archive of the mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: copying gcc binaries

I cannot quite use your script. My installation is on one machine and I want
to have it on another.
Copying is the only option as these two machines have only ftp connection
(so cannot mount the required directories on the new machine). I have copied
everything over and I don't want to use the same directory names as the ones
specified when configure was run on the first machine.


> -----Original Message-----
> From: Janis Johnson []
> Sent: Friday, March 22, 2002 4:01 PM
> To: Bob Boz
> Cc:
> Subject: Re: copying gcc binaries
> On Fri, Mar 22, 2002 at 03:39:52PM -0500, Bob Boz wrote:
> > To use gcc on a machine where gcc is not installed, I have to
> tar the whole
> > directory structure and ftp it over (mounting the directory is not an
> > option). This by itself does not work since a lot of the
> variables set at
> > configure time are still pointing to the old directories (trying
> > "gcc -print-search-dirs" for example will show some of them). I
> have tried
> > playing around with GCC_EXEC_PREFIX and such but I have not
> gotten anywhere.
> > Does a better solution exist? if not, could anyone help with
> setting up gcc
> > once I have copied (ftped) everything over?
> >
> > Thanks,
> >  Bob
> When I've needed to copy an installation to a new location I've used it
> via a script like this:
> #! /bin/sh
> INST=/builds/gcc_3_0_4_release/ia64/install
> TARGET=ia64-unknown-linux
> ${INST}/bin/gcc \
>   -B ${INST}/bin \
>   -B ${INST}/${TARGET}/bin \
>   -isystem ${INST}/${TARGET}/include \
>   -isystem ${INST}/${TARGET}/sys-include \
>   $*
> Hope this helps.
> Janis

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]