中国DOS联盟

Dear English experts:

Hello! I know nothing about English, but I really want to use DJGPP for programming. However, its installation is very complicated, so I want you all to help me translate its installation instructions. Here is the link:
http://www2.zzu.edu.cn/ie/newdos/dispbbs.asp?boardID=6&ID=2604

Don't say I'm stupid. I really want to use DJGPP for programming. Thank you all in advance!

I know there are a few English experts in the forum, please take a look at me! :(

Guide: Install DJGPP

Okay, you need a ZIP compressed file with a sound directory structure. Many files are dozens of megabytes, and it's not clear where to start.

The first step is to decide what you want to do with DJGPP. This step allows you to selectively extract.

For each ZIP file, use UNZIP or PKUNZIP with the -D parameter to extract. If you forget to use the -D parameter, then each file will be extracted directly into one directory, which is certainly not what you expect.

Once you have chosen the files to extract, you should extract them all into the same directory.

For instructional purposes, we assume you choose c:\djgpp as the extraction directory. After correct extraction, you can see the following directory structure:

bin
Executable files

include
INCLUDE files

lib
Library files

manifest
Directory containing lists describing the contents of each ZIP file

zoneinfo
Time zone definitions (you may not need them, can be deleted)

There may also be the following directories:

src
Source files for DJGPP

gnu
Source files for GNU

contrib
Distributed tools

You have extracted all the files, but this is not the end. There are two more things you need to prepare before using DJGPP:

In the DJGPP directory, there is a BIN directory containing all the programs. You must modify your environment variables to include the path to this BIN directory in the PATH variable.

Here is an example of adding the BIN path in AUTOEXEC.BAT:

set PATH=C:\DJGPP\BIN;%PATH%


In the DJGPP directory, there is a file DJGPP.ENV. Do not modify it unless the installation package specifies to do so. You must add a new environment variable to tell the system to point to this file.

It should be noted that here you can use upper and lower case at will, and you can use / or \ symbols at will. (Most DJGPP programs support both expressions, but it is recommended to use \ as in the example.)

--------------------------------------------------------------------------------

The next stage lists the most popular (or often forgotten) parts of DJGPP installation.

Your own description version may contain many other ZIP package files (when I was writing this document, there were already more than 06 separate ZIP packages). Most have README files, so you can just open them and see what they can bring :)

Basic functions part

Every programmer should install these basic packages, whether they need them or not. Why? Because although they don't seem to be so urgent, they are often cited in newsgroups. Also, pay attention to the version numbers of these parts, and always use the latest ones, which is always better.

v2/readme.1st
A big file that every programmer must read, including important upgrade information and a brief introduction to getting started

v2/djdev201.zip
Absolutely necessary ZIP package, this is the basic runtime and development package, including INCLUDE files, C library, standard tools, FPU emulator, time zone definition files.

v2/faq210b.zip
FAQ file. Before you ask questions on the forum, read it first.

v2gnu/txi390b.zip
Contains the INFO.EXE program, which can be used to read online document materials. (Such as online help)

v2gnu/gcc2721b.zip
C language compiler and preprocessor, almost all programs need it.

v2gnu/bnu27b.zip
It is an assembly compiler and linker, and some other programs (like library files). All languages need the support of this assembly program.

v2gnu/mak375b.zip
MAKE is the program that tracks your program construction.

v2misc/csdpmi3b.zip
If you need your program to run in pure DOS, you need the CWSDPMI service? Then there are these things here.

Other Languages

The most basic function is to implement C programs, but don't be surprised. DJGPP supports more.

v2gnu/bsn124b.zip
DISON is a YACC replacement program (???). If you need to compile *.y language, you need it.

v2gnu/flx252b.zip
FLEX is a LEX preprocessor.

v2gnu/gpc20b.zip
PASCAL compiler.

v2gnu/gpp2721b.zip
C++ compiler.

v2gnu/lgp271b.zip
C++ library. If you use streams, you need it.

v2gnu/obc2721b.zip
Objective C compiler.

Programming tools and help files:

v2apps/rhide13b.zip
IDE programming package, consisting of editor, compiler, online help system, debugger, unified interface. If you are unfamiliar with the command line-based compilation mode, this may be the best starting point.

v2gnu/em1934*.zip
GNU Emacs. This is the preferred text editor for many hardcore Unix programmers. You can also invoke the compiler or make from within, as well as read the online documentation and play games. You'll need to install all these zips; read the emacs.README first.
GNU Emacs. (Omitted, no need to translate here.)

v2gnu/gdb416b.zip
The GNU debugger. This is an extremely powerful full symbolic debugger, but you'd best read the docs before trying to use it.
GNU debugger.

v2gnu/bsh1147b.zip

BASH (the most famous UNIX shell, no need to translate here)
Ports of Unix programs

v2gnu/fil313b.zip
UNIX-style document tools. If you want to run SHELL scripts, you need these basic commands, LS, RM, CP, MV, etc.

......
......
Omitted, all are some UNIX tool packages.

Tools

These ZIP packages contain various libraries and pre-compiled functions (functions). You don't need these, but they can speed up development. If there is something useful to you in them.

v2tk/alleg21.zip
ALLEGRO is a popular game library, including support for sound, games, mouse, video playback.

v2tk/bccgrx20.zip
Use Borland's graphics function interface.

v2tk/grx20.zip
DJGPP's own graphics function interface.

v2tk/jptui37d.zip
Text user interface library.

v2tk/pdc22.zip
Public domain simulation, interface of UNIX programs.

v2tk/rsxntdj1.zip
Use this package to write WIN95, WINNT programs.

v2tk/sw21_dj2.zip
v2tk/sw21_doc.zip
v2tk/sw21_p1.zip
v2tk/sw21_p2.zip
C++ GUI provides NeXT-like interface.

Source code

All ZIP packages contain sub-packages, and those ending with S are source file packages.

v2/djlsr201.zip
DJGPP C library source file package. (A good tutorial for learning)

v2/djtst201.zip
Sources for programs that are used to test the C library; not general purpose test programs but they to demostrate much of the functionality.
Some source file packages for testing the C library. Not general-purpose tests, but they are very good EXAMPLE files.

This file has little to do with DJGPP. Even if you understand it, you may not be able to install it. I think you'd better look at that README--1ST, which seems more useful. It's short in time, and the translation is not good, don't mind it.

lemonhall, thank you so much!

You're welcome. It also inspired me a lot. I'm translating that readme.1st, and I'll post it here in a few days. That article is more universal.

Then I have to trouble "lemonhall". I'm waiting! :)

lemonhall, thank you~

###### # ##### ###### ######
# # # # # # # # #
# # # # # # # #
# # # # #### ###### ######
# # # # # # # #
# # # # # # # #
###### ##### ##### # #

DJ Delorie


This is the README.1ST file for DJGPP Version 2.03
This is the Chinese edition of the README.1ST file for DJGPP Version 2.03
（This is the README.1ST file for DJGPP Version 2.03 in Chinese Edition）


This file was translated and cataloged by LEMONHALL in July 2003
Email: lemonhall@vip.sina.com
QQ number: 313813. Welcome to correct errors.
Copyright@1989-1999 DJ Delorie All rights reserved
Chinese (in simplified character only) translation rights
arranged with DJ Delorie

Table of Contents

Distribution Package

Getting Started

What to Download
Installation
Compilation
Development Environment
Debugging
Online Documentation
Reading Online Documentation, Using Info
Compatibility with Version 2.00
Compatibility with Version 1.x

Copyright



************************************************************************
* This file contains information on obtaining, installing, and using *
* This file contains information on obtaining, installing, and using DJGPP. Please read it *completely* before asking for help. *
* DJGPP. Please read it *completely* before asking for help. *
* Please read it completely before asking for help. *
************************************************************************

DJGPP is a royalty-free environment for developing 32-bit protected-mode software under MS-DOS. The homepage of DJGPP on the World Wide Web is:
http://www.delorie.com/djgpp/

Software status and other information (online documentation, FAQs, mailing lists) can be viewed through web pages. Discussions about DJGPP and some questions about its use or features can be participated in through newsgroups (sent to comp.os.msdos.djgpp) and the DJGPP mailing list (send emails to ). Also, please pay attention to the various latest DJGPP development packages on the website.

Information about versions is marked in the *.ver file in the root directory of each compressed package, and the content is marked in the *.mft file in the root directory of each compressed package.

Of course, users can also obtain interactive (usually better) tutorials on installing and using djgpp on the World Wide Web:
http://www.delorie.com/djgpp/doc/



Distribution Package
****************

The DJGPP distribution package contains many subdirectories divided by content, and each subdirectory has a file called 00_index.txt that describes the files in the directory.

Compressed packages ending with 'b' contain compiled binary files and online documentation. At the moment this document is written, these packages are:

FAQ A file that guides you which other documents you should read (itself also includes a comprehensive FAQ list)

v2/
unzip32 A free tool to extract ZIP files (like PKUNZIP)
djdev203 DJGPP V2 development package and dynamic link library required for runtime
djlsr203 Source code of the basic library of DJGPP V2
djtst203 Test programs for DJGPP V2 (only used to test the C library)
djcrx203 DOS compiler support file package for DJGPP V2
djtzn203 Time zone file for DJGPP V2
djtzs203 Time zone source code for DJGPP V2
faq*b All FAQ lists (written in various formats, Info, ASCII, HTML...)
faq*s The Texinfo sources of the FAQ and tools to generate all the different formats of the FAQ
frfaq* French DJGPP FAQ

v2apps/
(Collection of various programs that cooperate or work for DJGPP, like RHIDE, TeX)

v2gnu/
(Interfaces to work with various FSF/GNU programs, such as gcc and binutils)

v2tk/
(Various development tools, development libraries, such as Allegro and libsocket)

v2misc/
csdpmi* CWSDPMI, Charles Sandmann's free DPMI server program and instruction file
mlp* ML executable file packer
pmode* PMODE stub for djgpp V2
wmemu* Optional 387 emulator for WM
(There are many miscellaneous tools for DJGPP)



Getting Started
***************

The following information is for users with minimal requirements, introducing how to get started quickly. Of course, for a new user, we hope and encourage you to get more detailed information by actively reading the FAQ list.


What to Download
----------------

Go to http://www.delorie.com/djgpp/zip-picker.html to see a form-based description, which lists in detail the distribution packages you need to download. Usually, users do not need source files, so if you just use DJGPP, it is enough to download the binary package.

To compile a C program, you need to download djdev203.zip, gcc*b.zip, and bnu*b.zip. If you want to use C++, you also need to download gpp*b.zip.

If you need to find online manuals, you need to download txi*b.zip and run the tool "info". If you are using pure 16-bit DOS, you need to install a DPMI server program. The installation package is csdpmi*b.zip (Windows, QDPMI, 386Max, NWDOS, OpenDOS, OS/2, Win/NT and Linux's DOSEmu have provided good DPMI services, so installing and running DJGPP in these environments does not require CWSDPMI). For detailed information, please refer to Chapter 4 of the FAQ list (download faq*b.zip and make sure it is a complete FAQ list) - "Where and What to Downlaod (Where and What to Download)".

If you are using Windows ME, 2000 or XP, the mirror files before November 2001 are very likely not to work properly. So if you are using the above operating system to run DJGPP, make sure you download the latest distribution package.


Installation
------------

1. Create a DJGPP working directory, for example, C:\DJGPP. (Warning: Do not install DJGPP in directories or subdirectories such as C:\DEV, D:\DEV: that will cause it not to work. For detailed reasons, see the FAQ list.) Do not use long directory names or any special characters, such as spaces.

If you have installed version 1.x before, it is best to give up using it or simply delete them. Of course, you can also just move them to other directories, but make sure that the target directory of the move does not appear in your PATH environment variable. (According to investigations, some bug reports are caused by mixing two versions of DJGPP. In fact, the only file that can be retained in version 1.x is 'go32.exe')

If you are using Windows NT 4.0 to run DJGPP, before installation, you need to decide whether you want to use long file names or only use the DOS 8.3 file name format. If long file name support is required, you need to download and install the TSR driver package (ntlfn*b.zip) before extracting the DJGPP distribution package.
(Translator's note: It is recommended not to use WinNT 4.0 to run DJGPP)

2. Unzip all compressed packages while preserving the directory structure. For example:

pkunzip -d djdev203
or
unzip32 djdev203

In Windows 9x, Windows/ME, Windows 2000 and Windows XP, use the unzip tool that supports long file names. The latest InfoZip's UnZip, PKUnzip and WinZip all support long file names. The unzip32.exe decompression tool on the DJGPP site also supports long file names very well. A way to ensure that you correctly extract long file name files is to check include/sys/sysmacros.h: if you only see sysmacro.h, then your decompression tool does not support long file names, and you need to find another decompression tool that really supports it.

You must ensure that the directory structure is correctly preserved when decompressing. If you are using WinZip, check the checkbox "Use folder names". If you are using pkunzip, make sure you use the -d parameter switch.

In Windows/NT (NT version 4 or lower, not WIN2000), if the TSR long file name driver LFN is not mounted, unzip will not correctly extract long file name files, and DJGPP will not be able to access long file name files. So here, we recommend using unzip32.exe, which will decompress correctly.


3. After correctly decompressing, set the environment variable to point to the DJGPP.ENV file in the DJGPP installation directory and add the BIN directory of DJGPP to the PATH environment variable queue.

The exact method of setting environment variables depends on the operating system you are using:

* For Windows 98 system:

- Click Start;
- Select Program->Settings->System Tools->System Information;
- Click the tool on the menu bar and select "System Configuration";
- Edit AUTOEXEC.BAT as follows

* For Windows ME system:

- Click Start, select Run, enter msconfig.exe; click OK
- Click the "Environment" page;
- Edit the PATH system variable to add the bin subdirectory of DJGPP;
- Add a new variable DJGPP and set its value to the full path name of DJGPP.ENV.
(More detailed introduction follows)

* For Windows NT system:

- Right-click "My Computer" and select "Properties";
- Click the Environment page;
- Edit the PATH system variable to add the bin subdirectory of DJGPP;
(If you are not an administrator, add the bin directory to the current user's PATH variable)
- Add a new variable DJGPP and set its value to the full path name of DJGPP.ENV.
(More detailed introduction follows)

* For Windows 2000 or Windows XP system:

- Right-click "My Computer" and select "Properties";
- Click the Advanced page; then click the "Environment Variables" button
- Edit the PATH system variable to add the bin subdirectory of DJGPP;
(If you are not an administrator, add the bin directory to the current user's PATH variable)
- Add a new variable DJGPP and set its value to the full path name of DJGPP.ENV.
(More detailed introduction follows)

* For other systems (DOS, Windows 3.x and Windows 95): Use the standard EDIT program to edit AUTOEXEC.BAT in the root directory of the boot disk.

As an alternative to editing AUTOEXEC or global variables, you may want to create a shortcut for DJGPP. If you do this, you need to create a batch file (*.bat) and include the command line introduced below. This method is suitable for computers with multiple compilation systems installed.

In any case, we assume that you have installed DJGPP in the C:\DJGPP directory, so the commands to set the two environment variables are as follows:

set DJGPP=C:\DJGPP\DJGPP.ENV
set PATH=C:\DJGPP\BIN;%PATH%

4. Restart. This can enable the two commands (In Windows NT, Windows 2000 and Windows XP, the environment variables take effect immediately, so if you use the above systems, you do not need to restart. But you still need to close the running DOS window and then run a new DOS window again)

5. Run the program go32-v2.exe without any parameters:

go32-v2

It will report the size of the DPMI memory and virtual space (swap) available for DJGPP, like this:

DPMI memory available: 8020 Kb
DPMI swap space available: 39413 Kb

The exact numbers depend on how much physical memory you have installed, how much hard disk space you have, and the capabilities of the DPMI server program. However, if the sum of the two spaces reported by go32-v2 is less than 4MB, please read section 3.9 of the FAQ list. "How to configure your system for DJGPP" (How to configure your system for DJGPP) (If you want to optimize the operation when it is already greater than 8MB, you can also refer to this part of the FAQ)


Compilation
-----------


GCC is a command-line-based compiler that can be used on the DOS command line. You can use the following command to compile and link a single C program source file:

gcc myfile.c -o myfile.exe -lm

The -lm parameter requires the compiler to link with the lib/libm.a library (trigonometric functions). (Linking requires explicit declaration. This means that if you need to use libm.a, you must add the parameter '-lm' at the end of the command line when compiling)

Use the following command to compile C or C++ source code into OBJ files:

gcc -c -Wall myfile.c (for C source)
or
gcc -c -Wall myfile.cc (for C++ source)

This compiles the file myfile.o. The parameter switch '-Wall' turns on the warning mode of the GCC compiler, and these warning messages are very useful for new users. (GCC also supports other many extensions, such as .cpp. For these, please refer to section 8.4 of the FAQ "How does GCC recognize the source language")

Use the following command line to compile multiple object files (OBJ) into an executable file:

gcc -o myprog.exe mymain.o mysub1.o mysub2.o

This compiles the executable file `myprog.exe' under DOS.

You can link C++ programs like this:

gxx -o myprog.exe mymain.o mysub1.o mysub2.o

At this time, the program will automatically search for C++ libraries, so you don't have to worry about setting parameters related to C++ libraries like above.

You can also perform these two steps of compilation and linking together:

gcc -Wall -o myprog.exe mymain.c mysub1.c mysub2.c

For more information about GCC running parameters, please refer to the online documentation. Before reading, you must confirm whether the Texinfo online documentation reading tool is correctly installed. (Find txi*b.zip and read the section about online documentation below)

After successful installation, you can find relevant information like this:

info gcc invoking



Development Environment (aka IDE)
---------------------------------

Admittedly, DJGPP does not have its own integrated environment. But this also means that you can freely choose any editor that can run DOS programs and view the output after running as an IDE. Many programmers use a DOS-based GNU Emacs to work with DJGPP. (You can find it in the v2gnu subdirectory) Emacs is a very powerful editor (for example, it has built-in Info reading function, so you can read DJGPP's online documentation without exiting the editor), and of course many other free editors can also be used as IDEs. The only thing that these quasi-IDEs (including Emacs) cannot do is to perform full-screen debugging.

A DJGPP-specific IDE called RHIDE was recently released to all DJGPP users. It has a Turbo C-style IDE interface, automatic indentation, statement coloring, highlighting of statements, automatic invocation of the DJGPP compiler, automatic generation of Makefile, and convenient reading of online documentation. And more excitingly, RHIDE also integrates a highly integrated debugging environment as powerful as the GNU Debugger (gdb). Because RHIDE is still a new software, there are still many bugs waiting to be debugged. So if you are interested, please visit:
http://www.tu-chemnitz.de/~sho/rho/rhide.html
to get the latest information.
(Translator's note: RIHID has become a widely used tool package. It is recommended that everyone download and master its use)


Debugging
---------

If you need to debug the program, you must add the parameter switch '-g' during compilation:

gcc -c -Wall -g mymain.c
gcc -c -Wall -g mysub1.c
gcc -c -Wall -g mysub2.c

Of course, you can also add the parameter `-g' when linking:

gcc -g -o myprog.exe mymain.o mysub1.o mysub2.o

(Note: When using DJGPP v2.01, there is no need to output the program as COFF for debugging purposes. (Omission of the `.exe' suffix in the file name can achieve this purpose). The debuggers of version 2.01 and later versions are fully capable of directly reading executable files for debugging, just like debugging COFF format files. Of course, if you can't fully understand what this means, don't worry.)

Then run your program under the debugger:

fsdb myprog.exe
or
gdb myprog.exe
or
edebug32 myprog.exe

(If you want to use GDB to debug the program, then you need to download gdb*b.zip)
FSDB has its own help screen, and you can press F1 to call the help. The help file of GDB can only be read using Info. Edebug32 is a rarely used integrated debugger, and press 'h' to call help after running.

Online Documentation
------------

Most online files are stored in a special hypertext format used by the GNU project. Each package has its own Info format document, which is a file with the suffix .iNN. Unzip it into the subdirectory info/ of the main installation directory of DJGPP. To browse these documents, you need to download txi*b.zip and then run info.exe. If you don't know how to use Info, you can read the following sections.

Reading Online Documentation with Info
----------------------------------------------------

The following instructions cannot be regarded as a complete tutorial for using Info, but only as a preliminary guide. So you need to refer to more documents and pay attention to the special sections.

To run Info to read the online manual, you need to add the manual name after the info command. For example:

- Enter "info libc" to read the support documentation about C library functions;
- Enter "info libc alphabetical printf" to look up the description of the function 'printf'
- Enter "info gcc" to read the GCC user manual (the GNU C compiler);
- Enter "info faq" to view the DJGPP FAQ list;
- Enter "info make" to read the user manual of the Make tool;
- Enter "info" to list the menu list of the manual.

Press 'q' to exit Info.

Once Info runs successfully, you can use the up and down arrows or PgDn, PgUp to browse the file.

After reading a screen, press the 'SPACE' key to turn the page. Through this function key, you can browse the chapters of the manual.

There is a mark "* Menu:" before the menu item. Each line starting with "*" is called a menu item. You can select a menu item by moving the cursor under the asterisk and pressing the Enter key.

The mark of the hypertext link is "* Note". If you need to refer to a link, as mentioned above. Move the cursor under the asterisk and press Enter. If you need to return, you can type the lowercase 'l' key. (Meaning Last)

If you need to quickly query the index information, you can type 'i' (meaning Index), and then type the topic you want to query, and end with Enter. You can type only part of the topic to be found, and then press the Tab key to automatically complete the topic. (Provided that you have entered part of the word of the complete topic). If after pressing the Tab key, the system beeps or the text starts to flash, it means that there is no topic matching the word you entered. Delete the word you just entered (using the BackSpace key) and try to type other words related to the content you want to find. Then, if the system successfully completes the topic you typed, and it happens to be the information you need, then type Enter to view it. Of course, finding the topic you want requires multiple attempts, and you need to be patient in searching.

For example, you want to find the exact meaning of the error message "ld.exe: cannot open -lstdcxx: No such file or directory" for output. Then, start the Info system, type `i' and enter `c a n TAB' (without those spaces). The first TAB key typed only changes can to Can, but this indicates that there are index items starting with Can, so type the TAB key again, and many possible entries are displayed. Don't get excited, there is no one you need in the index list starting with Can. So, only delete the word Can, then try to type '-lstd' and press Tab to complete, now Info only lists one entry, and coincidentally, that is exactly the information you need. Finally, type Enter and read carefully the description of that error message in the FAQ.

If you want to manually find the items in the index, then find the entry containing the word 'Index' in the top-level menu item, enter it, and then you can browse all the indexes at will.

There is no index for library references, so you can only find in the function table or query related content using the type of the function. For example, the library function'mktime' belongs to the time function (Time Functions), 'random' belongs to the "random number function" (Random Number Functions), etc.
(Translator's note: That is to say, you can query Time Functions to find the mktime function)

In some cases, looking up the index will not help you find the information you need (because not all questions can be listed), so type's' (meaning Search query), type the information you want to query, and then type Enter. Info will perform a full-text search and list the first matching item. If you want to find the next matching item, you can type's' and Enter again. The system will search again.

Finally, if you are looking for the information you want in any manual, you can use the "--apropos" parameter switch to force Info to traverse all installed manuals to find the information you need for you. For example, you heard that DJGPP programs support wildcards, but you don't know which manual the description is in. The following command can command the Info system to list the chapters about wildcards ("wildcards") in all manuals.

info --apropos=wildcard

Of course, this will take some time, and the system will list a list similar to the following content:

"(kb)Features" -- Wildcards
"(kb)Changes in 2.01" -- wildcards
"(djgppfaq)Filename globbing" -- Filename wildcards expansion

The manual name in quotes (in parentheses) and the chapter name (such as Features). If you want to view the listed chapter, you can type the following command:

info --node="(kb)Features"

Info has many commands and switches. If you want to view these, type "info info". If you need more information, you can type "info info-standalone"

Compatibility with Version 2.00
------------------------

If you are upgrading from version V2.00, then you need to completely reinstall all the packages you need to use. Because version 2.01 and later versions handle long command lines (and handle long filenames under WIN95), mixing version 2.00 with the new version will cause many debugging problems. For details, see section 16.6 of the FAQ list.

Compatibility with Version V1.x
-----------------------

Any compiled V1.x DJGPP can work independently well. The programs of V1 version cannot run the programs of V2 (but the programs of V2 can run the programs of V1), so do not try to use the Make program of V1.x to run the compiler of v2.x.

--- Copyright ---

DJGPP V2 is Copyright (C) 1989-1999 by DJ Delorie. Some parts of libc.a are Copyright (C) Regents of the University of California at Berkeley.

GNU software (gcc, make, libg++, etc) is Copyright by the Free Software Foundation.

The copyright of DJGPP V2 allows it to be used for commercial purposes. However, if you refer to the library files that are not DJGPP (such as GNU's libg++), then you need to abide by their copyright agreements. For more information, see Chapter 19 of the FAQ list.

There was a period of discussion on the newsgroup about the copyright of some C function libraries. To obtain this copyright, it is necessary to mention the University of California, Berkeley. So, even in your compiled version, you have to include the copyright notice. Fortunately, the copyright of Berkeley expired in July 1999. You no longer need to care about the copyright issue of that part in your distribution package.

Here, list these functions and files related to the Berkeley copyright:

libc/ansi/time/ctime.c: asctime ctime gmtime localtime mktime
tzset tzsetwall

libc/compat/stdlib/random.c: initstate random setstate srandom

==============================================================================


Enjoy!



DJ Delorie
dj@delorie.com
http://www.delorie.com/

Ah, finally finished translating. : )
Finally, the chapter on the online document is mostly a free translation, please bear with it.

lemonhall, thank you very much~