delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/1997/01/17/18:23:12

From: dahms AT ifk20 DOT mach DOT uni-karlsruhe DOT de
Subject: RE: string.h problems
17 Jan 1997 18:23:12 -0800 :
Approved: cygnus DOT gnu-win32 AT cygnus DOT com
Distribution: cygnus
Message-ID: <009AE84C.6D6F24C0.7465.cygnus.gnu-win32@ifk20.mach.uni-karlsruhe.de>
Original-To: cabr85 AT ccsun DOT strath DOT ac DOT uk
Original-CC: gnu-win32 AT cygnus DOT com, dahms AT ifk20 DOT mach DOT uni-karlsruhe DOT de
Original-Sender: owner-gnu-win32 AT cygnus DOT com

Hi, you wrote:

: I've had trouble with a number of functions that should be defined in
: string.h: strncpy, bcopy and bcopy

bzero?

: Also, it may be somewhat related to this, mostly ridiculous, thread on
: "why cygwin.dll" but I've noticed the resulting executables are enormous.
: I am including debugging information but still a file that compiled with
: cygnus/g++ takes around 1Mb takes only 300Kb on my unix machines
: (HP-UX/g++). That's less than a third!!

About 1MB source of 30000 lines compiled gcc -g -O under hp-ux gives me an
executable of ca. 1MB nonstripped, the same under NT is less than 50% larger. 
I use strncpy, memcpy and memset without problems.
And the thread is partially ridiculous, IMHO.


Bye, Heribert (dahms AT ifk20 DOT mach DOT uni-karlsruhe DOT de)
-
For help on using this list, send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019