Re: DRIVER_SELF_SPECS and multilib

2012-12-04 Thread Richard Sandiford
Richard Sandiford writes: > On the face of it, plain: > > "%{mtestoption:-mcpu=cortex-a5 % > ought to be OK. mtestoption will get passed down the cc1 etc., but > adding it to the .opt file should mean that it is accepted and ignored. Er, I meant "%{mtestoption:-mcpu=cortex-a5}". Richard

Re: DRIVER_SELF_SPECS and multilib

2012-12-04 Thread Richard Sandiford
gnubie gnubie writes: > Hi, > > I notice that if you add a DRIVER_SELF_SPEC option and then add that > option as a MULTILIB_OPTION, it doesn't build certain libraries for > that multilib variant. > > for example, if you add: > > "%{mtestoption:-mcpu=cortex-a5 % > (and then define mtestoption in th

DRIVER_SELF_SPECS and multilib

2012-11-29 Thread gnubie gnubie
Hi, I notice that if you add a DRIVER_SELF_SPEC option and then add that option as a MULTILIB_OPTION, it doesn't build certain libraries for that multilib variant. for example, if you add: "%{mtestoption:-mcpu=cortex-a5 %