| 1 |
On Wed, 2005-08-24 at 14:53 +0200, Paul de Vrieze wrote: |
| 2 |
> On Saturday 06 August 2005 20:18, Jeff Walter wrote: |
| 3 |
> > Yuri Vasilevski wrote: |
| 4 |
> > > Hi, |
| 5 |
> > > |
| 6 |
> > > On Sat, 06 Aug 2005 20:04:20 +0300 |
| 7 |
> > > |
| 8 |
> > > Ivan Yosifov <ivan@×××××××.net> wrote: |
| 9 |
> > >>I am not sure if it is better, but you can |
| 10 |
> > >>cat /proc/cpuinfo | grep flags | grep sse |
| 11 |
> > >>and die if not found. |
| 12 |
> > > |
| 13 |
> > > This will make packages dependant on the build system, |
| 14 |
> > > which will create inconsistencies in binary gentoo packages. |
| 15 |
> > > |
| 16 |
> > > Yuri. |
| 17 |
> > |
| 18 |
> > This is true, and there's no good way around the issue. I had written |
| 19 |
> > a small script to actually search for the flag (grep'ing for sse will |
| 20 |
> > go true for sse2 as well), we I noticed this. |
| 21 |
> > |
| 22 |
> > Will valgrind 3.0.0 ever work on systems without sse? If not, the USE |
| 23 |
> > flag might be your best bet. |
| 24 |
> |
| 25 |
> Put a check on /proc/cpuinfo in pkg_preinst. This should get executed on |
| 26 |
> the final machine, so not when building binary packages. |
| 27 |
> |
| 28 |
|
| 29 |
Same thing (and probably better option) if you put it in pkg_setup() ... |
| 30 |
|
| 31 |
|
| 32 |
-- |
| 33 |
Martin Schlemmer |
Archives