-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Donnie Berkholz wrote:
| As I said, very soon. It's out. I will begin adding new categories as
| necessary and the beginnings of the modular tree tomorrow.
What I meant by "tomorrow" was "next week," of course. =) I just made
the first commits.
Plea
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jakub Moc wrote:
>
>
> Check Bug 101457.
>
>
How unlucky. I actually came across this problem days ago and searched
bugzilla for it. Just didn't get around to writing the email until now.
I will add my thoughts to the bug.
Regards,
Petteri Räty (
7.8.2005, 22:46:39, Petteri Räty wrote:
> It is usually not a problem for users because the file gets mirrored but
> when doing version bumps I come across this again. As a solution I added
> - --no-check-certificate to my FETCHCOMMAND so this will not bother me
> again.
> So what about
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
One of the java packages, jdictrayapi, is only available over ssl. Here
is the output I get if I try downloading it with wget:
[EMAIL PROTECTED] ~/java $ wget
https://jdic.dev.java.net/files/documents/880/16466/jdic-0.9.1-src.zip
- --23:37:11--
https:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Benedikt Boehm wrote:
> Hey everybody,
>
> please give a warm welcome to Christian Heim, our latest victim, poping in to
> support the german conspiracy, and to help me with vserver stuff.
Welcome.
>
> Christian currently is in his last third of v
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 Sunday 07 August 2005 16:46, Benedikt Boehm wrote:
> Hey everybody,
>
> please give a warm welcome to Christian Heim, our latest victim, poping in
> to support the german conspiracy, and to help me with vserver stuff.
>
> Christian currently is in his last third of vocational education and will
Hey everybody,
please give a warm welcome to Christian Heim, our latest victim, poping in to
support the german conspiracy, and to help me with vserver stuff.
Christian currently is in his last third of vocational education and will
hopefully finished on 25 Aug. Besides the education as managem
On Sun, 07 Aug 2005 12:24:35 +0200 Jan Kundrát <[EMAIL PROTECTED]> wrote:
| > Hrm, we can't mess with encoding without breaking things for people
| > using silly terminals (like aterm, gnome-terminal and konsole) that
| > lie about their $TERM.
|
| My konsole reports "xterm"; what's wrong with tha
Ivan Yosifov posted <[EMAIL PROTECTED]>, excerpted
below, on Sun, 07 Aug 2005 13:28:11 +0300:
> On Sun, 2005-08-07 at 12:11 +0200, Diego 'Flameeyes' Pettenò wrote:
>> On Sunday 07 August 2005 12:03, Ivan Yosifov wrote: Well ppc doesn't
>> have SSE
>
> Then why is the ppc keyword there ?
Well, h
On Sun, 2005-08-07 at 12:11 +0200, Diego 'Flameeyes' Pettenò wrote:
> On Sunday 07 August 2005 12:03, Ivan Yosifov wrote:
> Well ppc doesn't have SSE
Then why is the ppc keyword there ?
> but there are many people running Gentoo non machines that does *not* support
> SSE
That's why I suggested
Ciaran McCreesh wrote:
> Bleh, I just figured that one out. The best way around it is to export
> LC_ALL=en_US.utf8 before editing UTF-8 files.
I've had some troubles (mainly `less` and some X apps working
incorrectly) with LC_CTYPE=cs_CZ.utf8 which were fixed by
LC_CTYPE=cs_CZ.UTF-8. It seems tha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ivan Yosifov wrote:
>
> Then the only fail-safe way to do it is to print a big red warning and
> pause for 10 seconds during ebuild emerge. Given the valgrind-3.0.0
> keywords ( -* ~amd64 ~ppc ~x86 ) I guess most people on those arches
> have SSE anyw
On Sunday 07 August 2005 12:03, Ivan Yosifov wrote:
> Then the only fail-safe way to do it is to print a big red warning and
> pause for 10 seconds during ebuild emerge.
Probably is the better plan, looking for tc-arch = x86.
> Given the valgrind-3.0.0
> keywords ( -* ~amd64 ~ppc ~x86 ) I guess m
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
On Sat, 2005-08-06 at 21:37 +0200, Diego 'Flameeyes' Pettenò wrote:
> On Saturday 06 August 2005 21:24, R Hill wrote:
> > compile a small test program containing SSE specific intrinsics and die
> > if it returns an error code? does valgrind's configure check for sse?
> That will break while prepar
16 matches
Mail list logo
