| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 314.1 | Re: Invoking a different compiler... | SMURF::FILTER | Automatic Posting Software - mail to flume::puck | Fri Sep 10 1993 12:16 | 22 |
| Date Of Receipt: 10-SEP-1993 10:15:34.81
From: FLUME::jmcg "Jim McGinness"
To: [email protected], [email protected]
CC:
Subj: Re: Invoking a different compiler...
There's probably a dozen ways to do what you're asking...
Two possibilities are:
1) Place the compiler you want in the sandbox tools directory under the
name that would have been used normally.
2) Add a line to the Makefile that says CC=/name/of/your/compiler/here
Things get more complicated if your compiler won't take the same flags
as the standard compiler, if you just want to apply this compiler to
a few of the files, or if you're compiling for another architecture.
In those cases you'd probably have to invest in understanding the
CCTYPE logic supported by the Makefiles.
-- jmcg
|
| 314.2 | Re: Invoking a different compiler... | SMURF::FILTER | Automatic Posting Software - mail to flume::puck | Fri Sep 10 1993 12:18 | 12 |
| Date Of Receipt: 10-SEP-1993 10:23:07.79
From: ALPHA::"[email protected]" "10-Sep-1993 1024"
To: [email protected] (Jim McGinness)
CC: [email protected], [email protected]
Subj: Re: Invoking a different compiler...
Is it possible to override the compiler which is defined in
the makefile by specifying a command line argument to the
build command?
-Rich
|
| 314.3 | Re: Invoking a different compiler... | SMURF::FILTER | Automatic Posting Software - mail to flume::puck | Fri Sep 10 1993 12:19 | 19 |
| Date Of Receipt: 10-SEP-1993 10:40:39.59
From: FLUME::jmcg "Jim McGinness"
To: [email protected], [email protected]
CC: [email protected]
Subj: Re: Invoking a different compiler...
Re: invoking a different compiler by giving an argument to build
I don't know of a way. At the level of the "build" command, there is
not just one compiler. There are a few variables with names like
COMP_HOST_ROOT that might do what you want; I suggest looking at
the rc_files/custom.build file in the submit tree for ideas.
I still think the easiest way to accomplish what you want is to put
what you want run in the tools directory. This is how our general
build process tests new compiler fixes and ensures that the system
is built with an already-tested compiler.
-- jmcg
|
| 314.4 | Re: Invoking a different compiler... | SMURF::FILTER | Automatic Posting Software - mail to flume::puck | Fri Sep 10 1993 21:56 | 31 |
| Date Of Receipt: 10-SEP-1993 20:28:40.72
From: FLUME::"[email protected]" "Grant Van Dyck"
To: [email protected] (Jim McGinness)
CC: [email protected], [email protected], [email protected]
Subj: Re: Invoking a different compiler...
> Re: invoking a different compiler by giving an argument to build
>
> I don't know of a way. At the level of the "build" command, there is
> not just one compiler. There are a few variables with names like
> COMP_HOST_ROOT that might do what you want; I suggest looking at
> the rc_files/custom.build file in the submit tree for ideas.
>
> I still think the easiest way to accomplish what you want is to put
> what you want run in the tools directory. This is how our general
> build process tests new compiler fixes and ensures that the system
> is built with an already-tested compiler.
>
> -- jmcg
Yes, but it does that by building in a backingtree, it gets trickier in a
sandbox - you need to add a custom file to your rc_files dir to override the
backingtree defined variables. The contents of this are as I descibed to rich
a week of two ago when he asked a similar question about using a different
ld.
--
Grant Van Dyck enet: [email protected]
Release Engineering
|