This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.


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: Cross Tools Help


> > This option is fine, But my question was that when iam building
> > the toolset, i want it to be built for one CPU only and not for entire
> > M68k family.
> >
> > The option you are suggesting is when compiling an application,
> > whereas my question is when building the toolchain how do i do it.
> 
> I appreciate that - but as far as I am aware, it would not be an easy job to
> build a compiler for only a specific member of the family.  However, I would
> suppose it is possible to change the default CPU, so that when no flags are
> specified the compiler will assume "-m68020", rather than a generic m68k
> chip.

It should just be a very small edit to the specs file to accomplish that.
If you're not going to rebuild the toolchain often, it's likely easiest
just to edit the specs file after final installation.  It gets installed
to $PREFIX/lib/gcc-lib/$TARGET/$VERSION/specs.  If you go this route
(rather than tracking down where specs gets built from in the source
tree and editing that), you'll need to perform this edit again after
each time you rebuild and reinstall the toolchain.


                          Carl Miller
                          Firmware Engineer, ViaSat

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com


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