> "Rupa" == Rupa Schomaker <[EMAIL PROTECTED]> writes:
Rupa> Umm.. I did.
Not very well apparently.
http://lists.debian.org/debian-java/2002/debian-java-200210/msg00092.html>
http://lists.debian.org/debian-java/2002/debian-java-200210/msg00102.html>
--
Stephen
"A duck!"
--
To UNSUBS
Our 1.4.1-beta works fine with glibc 2.3.1 here.
You're right .. It was a 1.4.0 j2sdk ! My freshly installed 1.4.1-beta
works fine :)
--
http://www.tryphon.homeip.net/~alban
Our 1.4.1-beta works fine with glibc 2.3.1 here.
You're right .. It was a 1.4.0 j2sdk ! My freshly installed 1.4.1-beta
works fine :)
--
http://www.tryphon.homeip.net/~alban
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Package: java-common
Version: 0.16
Severity: wishlist
I think the java policy should, in addition to specifying the use of
java-virtual-machine, java-compler and java{1,}-runtime, also recommend
the use of the virtual packages "jar" and "javadoc" to ensure a package
that provides the alternatives
Package: java-common
Version: 0.16
Severity: wishlist
I think the java policy should, in addition to specifying the use of
java-virtual-machine, java-compler and java{1,}-runtime, also recommend
the use of the virtual packages "jar" and "javadoc" to ensure a package
that provides the alternatives
On 25 Oct 2002, Jeff Self wrote:
> On Fri, 2002-10-25 at 09:47, Vincent Renardias wrote:
> > make sure you have 'tcpip_socket=1' somewhere in
> > /etc/postgresql/postgresql.conf.
> I looked and tcpip_socket=1 is there. I also checked my pg_hba.conf and
> I have these lines:
>
> local
I worked on a JSP on my iBook running OS X 10.2, Tomcat 4.1.12, and
PostgreSQL 7.2.3, and Java 1.3.1. The JSP has no problem connecting to
PostgreSQL and displaying the data. So I copied the app over to my
server running Debian 3.0 stable, Tomcat 4.1.12, Blackdown Java 1.3.1
and PostgreSQL 7.2.2.
On Fri, 2002-10-25 at 09:47, Vincent Renardias wrote:
> make sure you have 'tcpip_socket=1' somewhere in
> /etc/postgresql/postgresql.conf.
>
> Cordialement,
>
> --
> Vincent RENARDIAS
> Directeur Technique
> StrongHoldNET / http://www.strongholdnet.com
I looked and tcpip_socket=1 is there. I al
On Friday 25 October 2002 11:44, Erik Browaldh wrote:
> Hello everyone,
>
> Im a newcommer in the Linux-world, therefore, all kind of help may be
> help :-)
>
> I have problems installing these self-extracting files
> j2re-1_4_1_01-linux-i586.bin
> j2sdk-1_4_1_01linux-i586.bin
>
> I've put them und
On 25 Oct 2002, Jeff Self wrote:
> I worked on a JSP on my iBook running OS X 10.2, Tomcat 4.1.12, and
> PostgreSQL 7.2.3, and Java 1.3.1. The JSP has no problem connecting to
> PostgreSQL and displaying the data. So I copied the app over to my
> server running Debian 3.0 stable, Tomcat 4.1.12, B
I worked on a JSP on my iBook running OS X 10.2, Tomcat 4.1.12, and
PostgreSQL 7.2.3, and Java 1.3.1. The JSP has no problem connecting to
PostgreSQL and displaying the data. So I copied the app over to my
server running Debian 3.0 stable, Tomcat 4.1.12, Blackdown Java 1.3.1
and PostgreSQL 7.2.2. I
I worked on a JSP on my iBook running OS X 10.2, Tomcat 4.1.12, and
PostgreSQL 7.2.3, and Java 1.3.1. The JSP has no problem connecting to
PostgreSQL and displaying the data. So I copied the app over to my
server running Debian 3.0 stable, Tomcat 4.1.12, Blackdown Java 1.3.1
and PostgreSQL 7.2.2
On 25 Oct 2002, Jeff Self wrote:
> On Fri, 2002-10-25 at 09:47, Vincent Renardias wrote:
> > make sure you have 'tcpip_socket=1' somewhere in
> > /etc/postgresql/postgresql.conf.
> I looked and tcpip_socket=1 is there. I also checked my pg_hba.conf and
> I have these lines:
>
> local
On Fri, 2002-10-25 at 09:47, Vincent Renardias wrote:
> make sure you have 'tcpip_socket=1' somewhere in
> /etc/postgresql/postgresql.conf.
>
> Cordialement,
>
> --
> Vincent RENARDIAS
> Directeur Technique
> StrongHoldNET / http://www.strongholdnet.com
I looked and tcpip_socket=1 is there. I al
wow.
i am so glad I wrote to the list -- I *never* would have thought to
check the locale.
you were right -- changing back from en_US.tf8 to en_US made the
errors go away. I assume the second set of errors was somehow caused
by the first set -- that, being unable to access some fundamental set
On Friday 25 October 2002 11:44, Erik Browaldh wrote:
> Hello everyone,
>
> Im a newcommer in the Linux-world, therefore, all kind of help may be
> help :-)
>
> I have problems installing these self-extracting files
> j2re-1_4_1_01-linux-i586.bin
> j2sdk-1_4_1_01linux-i586.bin
>
> I've put them und
On 25 Oct 2002, Jeff Self wrote:
> I worked on a JSP on my iBook running OS X 10.2, Tomcat 4.1.12, and
> PostgreSQL 7.2.3, and Java 1.3.1. The JSP has no problem connecting to
> PostgreSQL and displaying the data. So I copied the app over to my
> server running Debian 3.0 stable, Tomcat 4.1.12, B
I worked on a JSP on my iBook running OS X 10.2, Tomcat 4.1.12, and
PostgreSQL 7.2.3, and Java 1.3.1. The JSP has no problem connecting to
PostgreSQL and displaying the data. So I copied the app over to my
server running Debian 3.0 stable, Tomcat 4.1.12, Blackdown Java 1.3.1
and PostgreSQL 7.2.2. I
George Hamilton wrote:
Erik
You have to check that javac in in you path. typing 'which javac' will tell you
the path of the executable. If not, it will tell you it can't be found.
To put in your path find manual where the java executables say
/root/usr/loca/java/bin for example. then
export PATH
wow.
i am so glad I wrote to the list -- I *never* would have thought to
check the locale.
you were right -- changing back from en_US.tf8 to en_US made the
errors go away. I assume the second set of errors was somehow caused
by the first set -- that, being unable to access some fundamental set
Hello everyone,
Im a newcommer in the Linux-world, therefore, all kind of help may be
help :-)
I have problems installing these self-extracting files
j2re-1_4_1_01-linux-i586.bin
j2sdk-1_4_1_01linux-i586.bin
I've put them under /root/usr/local , where I try to extract them
after reading the licen
Hi back!
>My hope was that someone knowledgeable would be able to tell me what
>the errors mean.
I'll give it a try, hope it's usefull...
>[javac] error: compiler message file broken:
>key=compiler.err.sun.io.MalformedInputException arguments=null, null,
>null, null, null, null, null
This is a
George Hamilton wrote:
Erik
You have to check that javac in in you path. typing 'which javac' will tell you the path of the executable. If not, it will tell you it can't be found.
To put in your path find manual where the java executables say
/root/usr/loca/java/bin for example. then
export
Apparently, and if I understand correctly, the older versions of the sdk
(including 1.4.0) used functions in libc that was not part of the
"public" API. Therefore, I assume this should be fixed by Blackdown/Sun
also for 1.3.1 releases, not just 1.4.1. Note I didn't bother reporting
this to either
I'm curious as to what the long term solution to this problem is.
Does libc need patching to make j2sdk1.3 work again?
Does j2sdk1.3 need fixing and recompiling? Is this a job for Blackdown
or the Debian packager?
I downgraded to libc 2.2.5 (from testing) but at least 6 other packages
in unstab
Well, since you say that you cannot upgrade to 1.4.1 your only choice
seems to be to downgrade your libc to version 2.2.5. Alternatively,
maybe you could adhere to the new interface in java.sql.Connection?
- Hein
On Wed, 2002-10-23 at 06:16, Rupa Schomaker wrote:
> -BEGIN PGP SIGNED MESSAGE-
Hello everyone,
Im a newcommer in the Linux-world, therefore, all kind of help may be
help :-)
I have problems installing these self-extracting files
j2re-1_4_1_01-linux-i586.bin
j2sdk-1_4_1_01linux-i586.bin
I've put them under /root/usr/local , where I try to extract them
after reading the lic
Hi back!
>My hope was that someone knowledgeable would be able to tell me what
>the errors mean.
I'll give it a try, hope it's usefull...
>[javac] error: compiler message file broken:
>key=compiler.err.sun.io.MalformedInputException arguments=null, null,
>null, null, null, null, null
This is a
Apparently, and if I understand correctly, the older versions of the sdk
(including 1.4.0) used functions in libc that was not part of the
"public" API. Therefore, I assume this should be fixed by Blackdown/Sun
also for 1.3.1 releases, not just 1.4.1. Note I didn't bother reporting
this to either
I'm curious as to what the long term solution to this problem is.
Does libc need patching to make j2sdk1.3 work again?
Does j2sdk1.3 need fixing and recompiling? Is this a job for Blackdown
or the Debian packager?
I downgraded to libc 2.2.5 (from testing) but at least 6 other packages
in unst
Well, since you say that you cannot upgrade to 1.4.1 your only choice
seems to be to downgrade your libc to version 2.2.5. Alternatively,
maybe you could adhere to the new interface in java.sql.Connection?
- Hein
On Wed, 2002-10-23 at 06:16, Rupa Schomaker wrote:
> -BEGIN PGP SIGNED MESSAGE-
31 matches
Mail list logo
