This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
RE: multilib default dir.
- From: "Sanjiv Gupta" <skg at cradle dot com>
- To: <gcc at gcc dot gnu dot org>
- Date: Sat, 31 Jan 2004 16:49:49 +0530
- Subject: RE: multilib default dir.
> What all I am looking for is that the driver should pass -L lib/foo
> even if -march=foo option is NOT specified on the command line.
>
>
correction.
What all I am looking for is that the driver should pass -L lib/foo
even none of MULTILIB_OPTIONS are specified on the command line.
> > -----Original Message-----
> > From: gcc-owner@gcc.gnu.org [mailto:gcc-owner@gcc.gnu.org]On Behalf Of
> > Sanjiv Gupta
> > Sent: Saturday, January 31, 2004 1:22 PM
> > To: gcc@gcc.gnu.org
> > Subject: multilib default dir.
> >
> >
> > I am building multilibs for
> > MULTILIB_OPTIONS = march=foo/march=bar.
> > MULTILIB_DIRNAMES = foo bar
> >
> > it generates
> >
> > static const char *const multilib_raw[] = {
> > ". !march=foo !march=bar;",
> > "foo march=foo !march=bar;",
> > "bar !march=foo march=bar;",
> > NULL
> > };
> >
> > How can I get the following, since foo is the default arch in our case.
> >
> > static const char *const multilib_raw[] = {
> > "foo !march=foo !march=bar;",
> > "foo march=foo !march=bar;",
> > "bar !march=foo march=bar;",
> > NULL
> > };
> >
> > Best Regards
> > Sanjiv
> >
> > Creating the Next Generation Soft-Silicon Semiconductor Company
> > www.cradle.com
> >
>