On Thursday 25 August 2005 21:17, Martin Schlemmer wrote:
> On Thu, 2005-08-25 at 13:41 +0200, Paul de Vrieze wrote:
> > On Wednesday 24 August 2005 15:23, Martin Schlemmer wrote:
> > > Same thing (and probably better option) if you put it in
> > > pkg_setup() ...
> >
> > Isn't pkg_setup run too wh
On Thu, 2005-08-25 at 13:41 +0200, Paul de Vrieze wrote:
> On Wednesday 24 August 2005 15:23, Martin Schlemmer wrote:
> >
> > Same thing (and probably better option) if you put it in pkg_setup()
> > ...
>
> Isn't pkg_setup run too when just building a binary package (-B) (then the
> check shouldn
On Thursday 25 August 2005 17:29, Brian Harring wrote:
> On Thu, Aug 25, 2005 at 01:41:00PM +0200, Paul de Vrieze wrote:
> > On Wednesday 24 August 2005 15:23, Martin Schlemmer wrote:
> > > Same thing (and probably better option) if you put it in pkg_setup()
> > > ...
> >
> > Isn't pkg_setup run to
On Thu, Aug 25, 2005 at 01:41:00PM +0200, Paul de Vrieze wrote:
> On Wednesday 24 August 2005 15:23, Martin Schlemmer wrote:
> >
> > Same thing (and probably better option) if you put it in pkg_setup()
> > ...
>
> Isn't pkg_setup run too when just building a binary package (-B) (then the
> check
On Wednesday 24 August 2005 15:23, Martin Schlemmer wrote:
>
> Same thing (and probably better option) if you put it in pkg_setup()
> ...
Isn't pkg_setup run too when just building a binary package (-B) (then the
check shouldn't be performed), and just before installing a binary
package?
Paul
On Wed, 2005-08-24 at 14:53 +0200, Paul de Vrieze wrote:
> On Saturday 06 August 2005 20:18, Jeff Walter wrote:
> > Yuri Vasilevski wrote:
> > > Hi,
> > >
> > > On Sat, 06 Aug 2005 20:04:20 +0300
> > >
> > > Ivan Yosifov <[EMAIL PROTECTED]> wrote:
> > >>I am not sure if it is better, but you can
>
On Sun, Aug 07, 2005 at 06:13:56AM -0400, Mike Frysinger wrote:
> that's pretty retarded imho ... this applies only to x86 right ?
Yes, it does. The valgrind developers are currently waiting to see if it
causes many complaints to see if they can prevent multiple code paths.
> > To make people aw
On Saturday 06 August 2005 10:15 am, Maurice van der Pot wrote:
> The new valgrind version (3.0.0) requires sse support. If you have a
> processor without sse, you'll need to stay at 2.4.1.
that's pretty retarded imho ... this applies only to x86 right ?
> To make people aware of this, I could us
Yuri Vasilevski wrote:
Hi,
On Sat, 06 Aug 2005 20:04:20 +0300
Ivan Yosifov <[EMAIL PROTECTED]> wrote:
I am not sure if it is better, but you can
cat /proc/cpuinfo | grep flags | grep sse
and die if not found.
This will make packages dependant on the build system,
which will create inconsi
On Sat, 6 Aug 2005 16:15:32 +0200 Maurice van der Pot
<[EMAIL PROTECTED]> wrote:
| The new valgrind version (3.0.0) requires sse support. If you have a
| processor without sse, you'll need to stay at 2.4.1.
|
| To make people aware of this, I could use the sse use flag in 3.0.0
| and die if it is
Hi,
On Sat, 06 Aug 2005 20:04:20 +0300
Ivan Yosifov <[EMAIL PROTECTED]> wrote:
> I am not sure if it is better, but you can
> cat /proc/cpuinfo | grep flags | grep sse
> and die if not found.
This will make packages dependant on the build system,
which will create inconsistencies in binary gen
Ivan Yosifov wrote:
cat /proc/cpuinfo | grep flags | grep sse
This assumes that they have used SSE support during compilation though,
which wouldn't be the case with -march=i686 or the like. However, it'd
be a good test.
Maybe a lookup table against -msse? Is there a way to check -msse,
On Sat, 2005-08-06 at 16:15 +0200, Maurice van der Pot wrote:
> The new valgrind version (3.0.0) requires sse support. If you have a
> processor without sse, you'll need to stay at 2.4.1.
>
> To make people aware of this, I could use the sse use flag in 3.0.0
> and die if it is not present, telli
The new valgrind version (3.0.0) requires sse support. If you have a
processor without sse, you'll need to stay at 2.4.1.
To make people aware of this, I could use the sse use flag in 3.0.0
and die if it is not present, telling people to mask versions 3.0.0
and up if they have a processor withou
14 matches
Mail list logo
