On 6/26/06, Shaun Jackman <[EMAIL PROTECTED]> wrote:
Reading through gcc/genmultilib, it looks as though
MULTILIB_EXCLUSIONS can take a '!' parameter, but MULTILIB_EXCEPTIONS
cannot.
The solutions was to use MULTILIB_EXCLUSIONS!
MULTILIB_EXCLUSIONS += !fPIC/msingle-pic-base
Yeeha!
Cheers,
Sh
"Shaun Jackman" <[EMAIL PROTECTED]> writes:
> Reading through gcc/genmultilib, it looks as though
> MULTILIB_EXCLUSIONS can take a '!' parameter, but MULTILIB_EXCEPTIONS
> cannot.
I forgot about MULTILIB_EXCLUSIONS (it might be nice if it were
documented). I don't know if it would help you, sinc
On 26 Jun 2006 14:42:20 -0700, Ian Lance Taylor <[EMAIL PROTECTED]> wrote:
No, that wouldn't work. MULTILIB_EXCEPTIONS takes a shell glob
pattern. It is invoked for each option set which is going to be
generated. I would expect that one of the option sets would be simply
"-msingle-pic-base".
"Shaun Jackman" <[EMAIL PROTECTED]> writes:
> On 26 Jun 2006 14:04:36 -0700, Ian Lance Taylor <[EMAIL PROTECTED]> >
> The usual hacked up way is to MULTILIB_EXCEPTIONS to remove
> > -msingle-pic-base without -fPIC. Something like
> >
> > MULTILIB_EXCEPTIONS = -msingle-pic-base
> >
> > might do it
On 26 Jun 2006 14:04:36 -0700, Ian Lance Taylor <[EMAIL PROTECTED]> >
The usual hacked up way is to MULTILIB_EXCEPTIONS to remove
-msingle-pic-base without -fPIC. Something like
MULTILIB_EXCEPTIONS = -msingle-pic-base
might do it.
I tried your suggestion, but it didn't seem to have the desir
"Shaun Jackman" <[EMAIL PROTECTED]> writes:
> I'm using MULTILIB_OPTIONS and MULTILIB_DIRNAMES to compile a PIC/XIP
> toolchain. I'm familiar with the MULTILIB_EXCEPTIONS mechanism to
> specify incompatible configurations. How, though, do I indicate that
> msingle-pic-base depends on fPIC?
>
> MU
