| 1 |
On Saturday 17 June 2006 13:28, Harald van Dijk wrote: |
| 2 |
> On Sat, Jun 17, 2006 at 01:15:58PM -0400, Mike Frysinger wrote: |
| 3 |
> > On Saturday 17 June 2006 06:17, Luca Barbato wrote: |
| 4 |
> > > Long term solution: |
| 5 |
> > > 1- check your new package for aliasing compliance, and if you have time |
| 6 |
> > > fix it in the code or in the makefile, if you haven't append |
| 7 |
> > > -fno-strict-aliasing to the cflags and maybe send a notice about it |
| 8 |
> > > upstream |
| 9 |
> > > |
| 10 |
> > > 2- append -fno-strict-aliasing to every source known to have such |
| 11 |
> > > issue. |
| 12 |
> > |
| 13 |
> > 3 - include checking in portage |
| 14 |
> > http://bugs.gentoo.org/111436 |
| 15 |
> |
| 16 |
> Would this make builds fail by default, or would it provide a hook for |
| 17 |
> the user to allow builds to fail if specific conditions are matched ? |
| 18 |
|
| 19 |
right now such behavior is not defined |
| 20 |
|
| 21 |
i would lean on the FEATURES=stricter setting though to control warn/die |
| 22 |
behavior |
| 23 |
-mike |
Archives