Re: Wide-char support and libc

2000-05-17 Thread Chris Piazza

On Wed, May 17, 2000 at 02:41:59AM -0400, Thimble Smith wrote:
 On Tue, May 16, 2000 at 11:52:32PM -0400, Donn Miller wrote:
  Anyone like the idea of adding wide char support to our libc?  Maybe
  we could port it over from {Net,Open}BSD or BSDi.  This would add the
  header file wctype.h, etc.
 
 There's a mailing list, freebsd-i18n, that seems to be very active
 regarding this topic (the archives show 0 posts).

It's probably not being archived properly.  I subscribed to this list
on the 24th of april and the first message was on the 5th of may.

% grep '^From ' freebsd-i18n | wc -l
  19 

Nothing was said about wc* in those 19 messages anyway.

 
 The latest I found on it (searching the archives) is this:
 
 http://www.whizkidtech.net/i18n/wc/
 
 As far as I can tell, nothing's been done since last May.

-Chris
-- 
[EMAIL PROTECTED]  | yawn.
[EMAIL PROTECTED]| Abbotsford, BC, Canada


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: OpenSSH 2.1

2000-05-17 Thread Jordan K. Hubbard

 But I'm suddenly confused what you're actually talking about
 here: OpenSSH, OpenSSL, or RSAREF.
 
 OpenSSH has never included crypto code, but it's useless without OpenSSL
 which quite certainly does. OpenSSH no longer requires RSAREF to operate
 (if you've got clients/servers willing to do DSA SSH2), which is the
 "non-free" component I was talking about.

OK, if OpenSSL still contains crypto then "never mind"; I thought
OpenSSL used *only* RSA and it used it through the RSAstubs code,
making it "OK."

 today as well (after you've checked and got that legal advice I've been
 bugging you about :)

I'm working on the legal advice; a firm has been retained and
consulted.  Some paperwork needs to be done in order to get FreeBSD an
export permit and I'm still working on figuring out if this will be an
ongoing issue or we can just do it once.

- Jordan


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: OpenSSH 2.1

2000-05-17 Thread Mark Blackman

speaking of which, I presume that OpenSSH 2.1 is being
merged into Internat by kindly overworked developer types 
at the moment? 

On Tue, May 16, 2000 at 10:06:09AM -0700, David O'Brien wrote:
 Even so, moving SSH into the bindist would be one less thing that has to
 be merged into Internat all the time.
  
 -- 
 -- David([EMAIL PROTECTED])
 
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with "unsubscribe freebsd-current" in the body of the message
 

-- 
Mark Blackman,Internet Systems Administrator,Sophos Anti-Virus
e-mail: [EMAIL PROTECTED]   http://www.sophos.com
US Support: +1 888 SOPHOS 9UK Support: +44 1235 559933


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: OpenSSH 2.1

2000-05-17 Thread Kris Kennaway

On Wed, 17 May 2000, Jordan K. Hubbard wrote:

 OK, if OpenSSL still contains crypto then "never mind"; I thought
 OpenSSL used *only* RSA and it used it through the RSAstubs code,
 making it "OK."

OpenSSL is a general-purpose cryptography toolkit which includes such
goodies as Blowfish, CAST, DES, Diffie-Hellman, DSA, RC[245], and..oh yes,
RSA :-)

  today as well (after you've checked and got that legal advice I've been
  bugging you about :)
 
 I'm working on the legal advice; a firm has been retained and
 consulted.  Some paperwork needs to be done in order to get FreeBSD an
 export permit and I'm still working on figuring out if this will be an
 ongoing issue or we can just do it once.

Whee! Great news!

Once you get the legal issues sorted out, we can finally merge the
internat and freefall crypto repositories so there's just one source of
crypto. I think the only (legitimate) difference between the two is a
single file, rsa_eay.c, which contains the actual RSA crypto on internat.
We can put that into its own cvsup collection (cvs-crypto-rsa) which won't
be installed by default (and won't build anyway for USA_RESIDENT=="YES"),
and which mirrors don't have to replicate. I think that should take care
of all of the legal issues.

Kris


In God we Trust -- all others must submit an X.509 certificate.
-- Charles Forsythe [EMAIL PROTECTED]



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: OpenSSH 2.1

2000-05-17 Thread Kris Kennaway

On Wed, 17 May 2000, Mark Blackman wrote:

 speaking of which, I presume that OpenSSH 2.1 is being
 merged into Internat by kindly overworked developer types 
 at the moment? 

I think Peter Wemm has already finished.

Kris


In God we Trust -- all others must submit an X.509 certificate.
-- Charles Forsythe [EMAIL PROTECTED]



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Wide-char support and libc

2000-05-17 Thread Garance A Drosihn

At 2:41 AM -0400 5/17/00, Thimble Smith wrote:
On Tue, May 16, 2000 at 11:52:32PM -0400, Donn Miller wrote:
  Anyone like the idea of adding wide char support to our libc?  Maybe
  we could port it over from {Net,Open}BSD or BSDi.  This would add the
  header file wctype.h, etc.

There's a mailing list, freebsd-i18n, that seems to be very active
regarding this topic (the archives show 0 posts).

The latest I found on it (searching the archives) is this:

http://www.whizkidtech.net/i18n/wc/

As was recently posted to freebsd-java:

There's a "wchar" implementation available on
http://www.cs.rpi.edu/~crossd/FreeBSD/wcs-19990606.tar.gz

I have tried it myself and it works as expected, meaning
that I was able to successfully link a Motif program.


---
Garance Alistair Drosehn   =   [EMAIL PROTECTED]
Senior Systems Programmer  or  [EMAIL PROTECTED]
Rensselaer Polytechnic Institute


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Motif is now Open Source 8)

2000-05-17 Thread Nate Williams

  It requires two downloads to get a working JDK system.  No other OS
  requires multiple packages to work.
  
  People shouldn't have to compile Motif up just to get a non-source
  version of the JDK to work.  Versioning problems that can be caused by
  folks using different include files and/or X than what was used to build
  the JDK.  Bugs that have slipped in due to changes in the Motif port
  that negatively effect the JDK.
  
  Shall I go on?
 
 I'm curious... what happens when someone who has already installed Motif
 then tries to install JDK?

Nothing.  It should use the version inside the JDK, and it won't effect
the version outside the JDK.


Nate


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



-current buildworld breakage

2000-05-17 Thread Shigeyuki Fukushima

My system is 4.0-CURRENT at Jan 31.
I try to upgrade it to -current (5-current),
but I get the following breakage.

Is my system environment broken?

Thanks!

--
 stage 2: build tools
--

... snip ...

cc -O -pipe -I. -DFREEBSD_NATIVE -DIN_GCC -DHAVE_CONFIG_H -DPREFIX=\"/usr\" 
-I/usr/obj/usr/src/gnu/usr.bin/cc/cc_tools/../cc_tools 
-I/usr/src/gnu/usr.bin/cc/cc_tools/../cc_tools 
-I/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc 
-I/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/config   -c 
/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/print-rtl.c
cc -O -pipe -I. -DFREEBSD_NATIVE -DIN_GCC -DHAVE_CONFIG_H -DPREFIX=\"/usr\" 
-I/usr/obj/usr/src/gnu/usr.bin/cc/cc_tools/../cc_tools 
-I/usr/src/gnu/usr.bin/cc/cc_tools/../cc_tools 
-I/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc 
-I/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/config   -c 
/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/bitmap.c
/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/bitmap.c:626: unterminated 
string or character constant
/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/bitmap.c:338: possible real 
start of unterminated constant
/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/bitmap.c: In function 
`bitmap_clear_bit':
/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/bitmap.c:338: `bitmap_g' 
undeclared (first use in this function)
/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/bitmap.c:338: (Each 
undeclared identifier is reported only once
/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/bitmap.c:338: for each 
function it appears in.)
/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/bitmap.c:562: syntax error 
before string constant
/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/bitmap.c:562: stray '\' in 
program
/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/bitmap.c:566: stray '\' in 
program
/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/bitmap.c:572: stray '\' in 
program
/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/bitmap.c:578: stray '\' in 
program
/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/bitmap.c:578: stray '\' in 
program
/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/bitmap.c:578: stray '\' in 
program
/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/bitmap.c:586: stray '\' in 
program
/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/bitmap.c:586: stray '\' in 
program
/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/bitmap.c:586: stray '\' in 
program
/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/bitmap.c:586: stray '\' in 
program
/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/bitmap.c:595: stray '\' in 
program
/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/bitmap.c:643: Unterminated 
string constant
*** Error code 1

Stop in /usr/src/gnu/usr.bin/cc/cc_tools.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.


--- shige (Shigeyuki Fukushima) [EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



modules

2000-05-17 Thread Brian Somers

Hi,

Sorry to whinge, but wWhat's the state of play with modules at the 
moment ?

1. To update things, I was under the impression that ``make buildworld 
   buildkernel'' then ``make installworld installkernel'' was the idea.  
   This doesn't build modules, but building from sys/compile/whatever 
   builds another kernel...  Is anybody going to finish what was started 
   and make buildkernel/installkernel do the modules too ?

2. Installing rtc.ko (ports/emulators/rtc) gives exec format errors 
   at boot time.

3. Building vmware2 now fails due to the move of bsd.kmod.mk and 
   ultimately suffers from the same exec format error as rtc.ko

Are there any plans to fix this stuff ?
-- 
Brian [EMAIL PROTECTED]brian@[uk.]FreeBSD.org
  http://www.Awfulhak.org   brian@[uk.]OpenBSD.org
Don't _EVER_ lose your sense of humour !




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: -current buildworld breakage

2000-05-17 Thread David O'Brien

On Thu, May 18, 2000 at 12:51:42AM +0900, Shigeyuki Fukushima wrote:
 My system is 4.0-CURRENT at Jan 31.
 I try to upgrade it to -current (5-current),
 but I get the following breakage.
 
 Is my system environment broken?

I think so.
 
-- 
-- David  ([EMAIL PROTECTED])
  Disclaimer: Not speaking for FreeBSD, just expressing my own opinion.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: modules

2000-05-17 Thread Sheldon Hearn



On Wed, 17 May 2000 18:41:29 +0100, Brian Somers wrote:

 1. To update things, I was under the impression that ``make buildworld 
buildkernel'' then ``make installworld installkernel'' was the idea.  
This doesn't build modules, but building from sys/compile/whatever 
builds another kernel...  Is anybody going to finish what was started 
and make buildkernel/installkernel do the modules too ?

The work on buildkernel/installkernel was done by different folks from
the guy(s) who've moved the modules build.  I was about to check in new
stuff for the installkernel target when the modules stuff happened.
Although the buildkernel/installkernel targets were Marcel's brainchild,
I'm looking at it.

Gimme some time (assuming nobody else gets stuck in there first); I've
had unbelievable hassles trying to sell a car.

Ciao,
Sheldon.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message