complearn 0.6.2
Sign up to get free protection for your applications and to get access to all the features.
- data/AUTHORS +13 -0
- data/COPYING +340 -0
- data/ChangeLog +0 -0
- data/INSTALL +231 -0
- data/Makefile +352 -0
- data/Makefile.am +76 -0
- data/Makefile.in +352 -0
- data/NEWS +7 -0
- data/README +0 -0
- data/aclocal.m4 +104 -0
- data/bin/Makefile +209 -0
- data/bin/Makefile.am +8 -0
- data/bin/Makefile.in +209 -0
- data/bin/labeltree +68 -0
- data/bin/labeltree.in +68 -0
- data/bin/makesvm +70 -0
- data/bin/makesvm.in +70 -0
- data/bin/maketree +98 -0
- data/bin/maketree.in +98 -0
- data/bin/ncd +43 -0
- data/bin/ncd.in +43 -0
- data/bin/ncdmatrix +54 -0
- data/bin/ncdmatrix.in +54 -0
- data/bin/ncdvector +50 -0
- data/bin/ncdvector.in +50 -0
- data/complearn-0.6.2.gem +0 -0
- data/complearn.gemspec +57 -0
- data/config.log +597 -0
- data/config.status +1082 -0
- data/configure +4922 -0
- data/configure.ac +91 -0
- data/confstat5FpLBf/config.h +65 -0
- data/confstat5FpLBf/subs-1.sed +50 -0
- data/confstat5FpLBf/subs-2.sed +13 -0
- data/confstat5FpLBf/subs.frag +0 -0
- data/confstat5FpLBf/subs.sed +59 -0
- data/confstat5FpLBf/undefs.sed +24 -0
- data/doc/FAQ.txt +67 -0
- data/doc/Makefile +286 -0
- data/doc/Makefile.am +11 -0
- data/doc/Makefile.in +286 -0
- data/doc/devguide.txt +15 -0
- data/doc/example.complearnrc +14 -0
- data/doc/examples.txt +35 -0
- data/doc/man/Makefile +255 -0
- data/doc/man/Makefile.am +11 -0
- data/doc/man/Makefile.in +255 -0
- data/doc/man/complearn.5 +91 -0
- data/doc/man/labeltree.1 +35 -0
- data/doc/man/makesvm.1 +60 -0
- data/doc/man/maketree.1 +58 -0
- data/doc/man/ncd.1 +51 -0
- data/doc/man/ncdmatrix.1 +40 -0
- data/doc/man/ncdvector.1 +42 -0
- data/doc/readme.txt +101 -0
- data/doc/userguide.txt +46 -0
- data/examples/genes/blueWhale.txt +1 -0
- data/examples/genes/cat.txt +1 -0
- data/examples/genes/chimpanzee.txt +1 -0
- data/examples/genes/finWhale.txt +1 -0
- data/examples/genes/graySeal.txt +1 -0
- data/examples/genes/harborSeal.txt +1 -0
- data/examples/genes/horse.txt +1 -0
- data/examples/genes/human.txt +1 -0
- data/examples/genes/mouse.txt +1 -0
- data/examples/genes/rat.txt +1 -0
- data/ext/Makefile +167 -0
- data/ext/Quartet.c +399 -0
- data/ext/Quartet.h +62 -0
- data/ext/TreeScore.c +244 -0
- data/ext/TreeScore.h +3 -0
- data/ext/config.h +65 -0
- data/ext/config.h.in +64 -0
- data/ext/extconf.rb +3 -0
- data/ext/lib/CompLearnLib/CLConfig.rb +241 -0
- data/ext/lib/CompLearnLib/CompressionObject.rb +59 -0
- data/ext/lib/CompLearnLib/CompressionTask.rb +99 -0
- data/ext/lib/CompLearnLib/DistMatrix.rb +18 -0
- data/ext/lib/CompLearnLib/FoundComp.rb +10 -0
- data/ext/lib/CompLearnLib/FoundComp.rb.in +10 -0
- data/ext/lib/CompLearnLib/Ncd.rb +248 -0
- data/ext/lib/CompLearnLib/RunEnv.rb +150 -0
- data/ext/lib/CompLearnLib/Task.rb +39 -0
- data/ext/lib/CompLearnLib/TaskMaster.rb +13 -0
- data/ext/lib/CompLearnLib/TaskMasterMPI.rb +112 -0
- data/ext/lib/CompLearnLib/TaskMasterSingle.rb +39 -0
- data/ext/lib/CompLearnLib/Tree.rb +300 -0
- data/install-sh +294 -0
- data/missing +336 -0
- data/mkinstalldirs +111 -0
- data/o +24 -0
- data/scripts/CompLearn.iss +89 -0
- data/scripts/CompLearn.iss.in +89 -0
- data/scripts/debian/changelog +6 -0
- data/scripts/debian/control +14 -0
- data/scripts/makeSetup.sh +23 -0
- data/scripts/makeSetup.sh.in +23 -0
- data/scripts/makedeb.zsh +46 -0
- data/scripts/makedeb.zsh.in +46 -0
- data/tests/alltests.rb +2 -0
- data/tests/bz2test.rb +516 -0
- data/tests/sshagent-test.rb +48 -0
- data/tests/tests.rb +275 -0
- metadata +164 -0
data/AUTHORS
ADDED
@@ -0,0 +1,13 @@
|
|
1
|
+
CompLearnLib
|
2
|
+
|
3
|
+
A toolkit for compression-based learning by Rudi Cilibrasi
|
4
|
+
|
5
|
+
Contact cilibrar@ofb.net for more information.
|
6
|
+
|
7
|
+
Please see the doc/ directory for more info, and enjoy!
|
8
|
+
|
9
|
+
Thanks also to:
|
10
|
+
|
11
|
+
julio b. (juliob@juliob.com) for Website Design
|
12
|
+
Stephanie Wehner (_@r4k.net) for programming and CVS help
|
13
|
+
|
data/COPYING
ADDED
@@ -0,0 +1,340 @@
|
|
1
|
+
GNU GENERAL PUBLIC LICENSE
|
2
|
+
Version 2, June 1991
|
3
|
+
|
4
|
+
Copyright (C) 1989, 1991 Free Software Foundation, Inc.
|
5
|
+
59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
|
6
|
+
Everyone is permitted to copy and distribute verbatim copies
|
7
|
+
of this license document, but changing it is not allowed.
|
8
|
+
|
9
|
+
Preamble
|
10
|
+
|
11
|
+
The licenses for most software are designed to take away your
|
12
|
+
freedom to share and change it. By contrast, the GNU General Public
|
13
|
+
License is intended to guarantee your freedom to share and change free
|
14
|
+
software--to make sure the software is free for all its users. This
|
15
|
+
General Public License applies to most of the Free Software
|
16
|
+
Foundation's software and to any other program whose authors commit to
|
17
|
+
using it. (Some other Free Software Foundation software is covered by
|
18
|
+
the GNU Library General Public License instead.) You can apply it to
|
19
|
+
your programs, too.
|
20
|
+
|
21
|
+
When we speak of free software, we are referring to freedom, not
|
22
|
+
price. Our General Public Licenses are designed to make sure that you
|
23
|
+
have the freedom to distribute copies of free software (and charge for
|
24
|
+
this service if you wish), that you receive source code or can get it
|
25
|
+
if you want it, that you can change the software or use pieces of it
|
26
|
+
in new free programs; and that you know you can do these things.
|
27
|
+
|
28
|
+
To protect your rights, we need to make restrictions that forbid
|
29
|
+
anyone to deny you these rights or to ask you to surrender the rights.
|
30
|
+
These restrictions translate to certain responsibilities for you if you
|
31
|
+
distribute copies of the software, or if you modify it.
|
32
|
+
|
33
|
+
For example, if you distribute copies of such a program, whether
|
34
|
+
gratis or for a fee, you must give the recipients all the rights that
|
35
|
+
you have. You must make sure that they, too, receive or can get the
|
36
|
+
source code. And you must show them these terms so they know their
|
37
|
+
rights.
|
38
|
+
|
39
|
+
We protect your rights with two steps: (1) copyright the software, and
|
40
|
+
(2) offer you this license which gives you legal permission to copy,
|
41
|
+
distribute and/or modify the software.
|
42
|
+
|
43
|
+
Also, for each author's protection and ours, we want to make certain
|
44
|
+
that everyone understands that there is no warranty for this free
|
45
|
+
software. If the software is modified by someone else and passed on, we
|
46
|
+
want its recipients to know that what they have is not the original, so
|
47
|
+
that any problems introduced by others will not reflect on the original
|
48
|
+
authors' reputations.
|
49
|
+
|
50
|
+
Finally, any free program is threatened constantly by software
|
51
|
+
patents. We wish to avoid the danger that redistributors of a free
|
52
|
+
program will individually obtain patent licenses, in effect making the
|
53
|
+
program proprietary. To prevent this, we have made it clear that any
|
54
|
+
patent must be licensed for everyone's free use or not licensed at all.
|
55
|
+
|
56
|
+
The precise terms and conditions for copying, distribution and
|
57
|
+
modification follow.
|
58
|
+
|
59
|
+
GNU GENERAL PUBLIC LICENSE
|
60
|
+
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
|
61
|
+
|
62
|
+
0. This License applies to any program or other work which contains
|
63
|
+
a notice placed by the copyright holder saying it may be distributed
|
64
|
+
under the terms of this General Public License. The "Program", below,
|
65
|
+
refers to any such program or work, and a "work based on the Program"
|
66
|
+
means either the Program or any derivative work under copyright law:
|
67
|
+
that is to say, a work containing the Program or a portion of it,
|
68
|
+
either verbatim or with modifications and/or translated into another
|
69
|
+
language. (Hereinafter, translation is included without limitation in
|
70
|
+
the term "modification".) Each licensee is addressed as "you".
|
71
|
+
|
72
|
+
Activities other than copying, distribution and modification are not
|
73
|
+
covered by this License; they are outside its scope. The act of
|
74
|
+
running the Program is not restricted, and the output from the Program
|
75
|
+
is covered only if its contents constitute a work based on the
|
76
|
+
Program (independent of having been made by running the Program).
|
77
|
+
Whether that is true depends on what the Program does.
|
78
|
+
|
79
|
+
1. You may copy and distribute verbatim copies of the Program's
|
80
|
+
source code as you receive it, in any medium, provided that you
|
81
|
+
conspicuously and appropriately publish on each copy an appropriate
|
82
|
+
copyright notice and disclaimer of warranty; keep intact all the
|
83
|
+
notices that refer to this License and to the absence of any warranty;
|
84
|
+
and give any other recipients of the Program a copy of this License
|
85
|
+
along with the Program.
|
86
|
+
|
87
|
+
You may charge a fee for the physical act of transferring a copy, and
|
88
|
+
you may at your option offer warranty protection in exchange for a fee.
|
89
|
+
|
90
|
+
2. You may modify your copy or copies of the Program or any portion
|
91
|
+
of it, thus forming a work based on the Program, and copy and
|
92
|
+
distribute such modifications or work under the terms of Section 1
|
93
|
+
above, provided that you also meet all of these conditions:
|
94
|
+
|
95
|
+
a) You must cause the modified files to carry prominent notices
|
96
|
+
stating that you changed the files and the date of any change.
|
97
|
+
|
98
|
+
b) You must cause any work that you distribute or publish, that in
|
99
|
+
whole or in part contains or is derived from the Program or any
|
100
|
+
part thereof, to be licensed as a whole at no charge to all third
|
101
|
+
parties under the terms of this License.
|
102
|
+
|
103
|
+
c) If the modified program normally reads commands interactively
|
104
|
+
when run, you must cause it, when started running for such
|
105
|
+
interactive use in the most ordinary way, to print or display an
|
106
|
+
announcement including an appropriate copyright notice and a
|
107
|
+
notice that there is no warranty (or else, saying that you provide
|
108
|
+
a warranty) and that users may redistribute the program under
|
109
|
+
these conditions, and telling the user how to view a copy of this
|
110
|
+
License. (Exception: if the Program itself is interactive but
|
111
|
+
does not normally print such an announcement, your work based on
|
112
|
+
the Program is not required to print an announcement.)
|
113
|
+
|
114
|
+
These requirements apply to the modified work as a whole. If
|
115
|
+
identifiable sections of that work are not derived from the Program,
|
116
|
+
and can be reasonably considered independent and separate works in
|
117
|
+
themselves, then this License, and its terms, do not apply to those
|
118
|
+
sections when you distribute them as separate works. But when you
|
119
|
+
distribute the same sections as part of a whole which is a work based
|
120
|
+
on the Program, the distribution of the whole must be on the terms of
|
121
|
+
this License, whose permissions for other licensees extend to the
|
122
|
+
entire whole, and thus to each and every part regardless of who wrote it.
|
123
|
+
|
124
|
+
Thus, it is not the intent of this section to claim rights or contest
|
125
|
+
your rights to work written entirely by you; rather, the intent is to
|
126
|
+
exercise the right to control the distribution of derivative or
|
127
|
+
collective works based on the Program.
|
128
|
+
|
129
|
+
In addition, mere aggregation of another work not based on the Program
|
130
|
+
with the Program (or with a work based on the Program) on a volume of
|
131
|
+
a storage or distribution medium does not bring the other work under
|
132
|
+
the scope of this License.
|
133
|
+
|
134
|
+
3. You may copy and distribute the Program (or a work based on it,
|
135
|
+
under Section 2) in object code or executable form under the terms of
|
136
|
+
Sections 1 and 2 above provided that you also do one of the following:
|
137
|
+
|
138
|
+
a) Accompany it with the complete corresponding machine-readable
|
139
|
+
source code, which must be distributed under the terms of Sections
|
140
|
+
1 and 2 above on a medium customarily used for software interchange; or,
|
141
|
+
|
142
|
+
b) Accompany it with a written offer, valid for at least three
|
143
|
+
years, to give any third party, for a charge no more than your
|
144
|
+
cost of physically performing source distribution, a complete
|
145
|
+
machine-readable copy of the corresponding source code, to be
|
146
|
+
distributed under the terms of Sections 1 and 2 above on a medium
|
147
|
+
customarily used for software interchange; or,
|
148
|
+
|
149
|
+
c) Accompany it with the information you received as to the offer
|
150
|
+
to distribute corresponding source code. (This alternative is
|
151
|
+
allowed only for noncommercial distribution and only if you
|
152
|
+
received the program in object code or executable form with such
|
153
|
+
an offer, in accord with Subsection b above.)
|
154
|
+
|
155
|
+
The source code for a work means the preferred form of the work for
|
156
|
+
making modifications to it. For an executable work, complete source
|
157
|
+
code means all the source code for all modules it contains, plus any
|
158
|
+
associated interface definition files, plus the scripts used to
|
159
|
+
control compilation and installation of the executable. However, as a
|
160
|
+
special exception, the source code distributed need not include
|
161
|
+
anything that is normally distributed (in either source or binary
|
162
|
+
form) with the major components (compiler, kernel, and so on) of the
|
163
|
+
operating system on which the executable runs, unless that component
|
164
|
+
itself accompanies the executable.
|
165
|
+
|
166
|
+
If distribution of executable or object code is made by offering
|
167
|
+
access to copy from a designated place, then offering equivalent
|
168
|
+
access to copy the source code from the same place counts as
|
169
|
+
distribution of the source code, even though third parties are not
|
170
|
+
compelled to copy the source along with the object code.
|
171
|
+
|
172
|
+
4. You may not copy, modify, sublicense, or distribute the Program
|
173
|
+
except as expressly provided under this License. Any attempt
|
174
|
+
otherwise to copy, modify, sublicense or distribute the Program is
|
175
|
+
void, and will automatically terminate your rights under this License.
|
176
|
+
However, parties who have received copies, or rights, from you under
|
177
|
+
this License will not have their licenses terminated so long as such
|
178
|
+
parties remain in full compliance.
|
179
|
+
|
180
|
+
5. You are not required to accept this License, since you have not
|
181
|
+
signed it. However, nothing else grants you permission to modify or
|
182
|
+
distribute the Program or its derivative works. These actions are
|
183
|
+
prohibited by law if you do not accept this License. Therefore, by
|
184
|
+
modifying or distributing the Program (or any work based on the
|
185
|
+
Program), you indicate your acceptance of this License to do so, and
|
186
|
+
all its terms and conditions for copying, distributing or modifying
|
187
|
+
the Program or works based on it.
|
188
|
+
|
189
|
+
6. Each time you redistribute the Program (or any work based on the
|
190
|
+
Program), the recipient automatically receives a license from the
|
191
|
+
original licensor to copy, distribute or modify the Program subject to
|
192
|
+
these terms and conditions. You may not impose any further
|
193
|
+
restrictions on the recipients' exercise of the rights granted herein.
|
194
|
+
You are not responsible for enforcing compliance by third parties to
|
195
|
+
this License.
|
196
|
+
|
197
|
+
7. If, as a consequence of a court judgment or allegation of patent
|
198
|
+
infringement or for any other reason (not limited to patent issues),
|
199
|
+
conditions are imposed on you (whether by court order, agreement or
|
200
|
+
otherwise) that contradict the conditions of this License, they do not
|
201
|
+
excuse you from the conditions of this License. If you cannot
|
202
|
+
distribute so as to satisfy simultaneously your obligations under this
|
203
|
+
License and any other pertinent obligations, then as a consequence you
|
204
|
+
may not distribute the Program at all. For example, if a patent
|
205
|
+
license would not permit royalty-free redistribution of the Program by
|
206
|
+
all those who receive copies directly or indirectly through you, then
|
207
|
+
the only way you could satisfy both it and this License would be to
|
208
|
+
refrain entirely from distribution of the Program.
|
209
|
+
|
210
|
+
If any portion of this section is held invalid or unenforceable under
|
211
|
+
any particular circumstance, the balance of the section is intended to
|
212
|
+
apply and the section as a whole is intended to apply in other
|
213
|
+
circumstances.
|
214
|
+
|
215
|
+
It is not the purpose of this section to induce you to infringe any
|
216
|
+
patents or other property right claims or to contest validity of any
|
217
|
+
such claims; this section has the sole purpose of protecting the
|
218
|
+
integrity of the free software distribution system, which is
|
219
|
+
implemented by public license practices. Many people have made
|
220
|
+
generous contributions to the wide range of software distributed
|
221
|
+
through that system in reliance on consistent application of that
|
222
|
+
system; it is up to the author/donor to decide if he or she is willing
|
223
|
+
to distribute software through any other system and a licensee cannot
|
224
|
+
impose that choice.
|
225
|
+
|
226
|
+
This section is intended to make thoroughly clear what is believed to
|
227
|
+
be a consequence of the rest of this License.
|
228
|
+
|
229
|
+
8. If the distribution and/or use of the Program is restricted in
|
230
|
+
certain countries either by patents or by copyrighted interfaces, the
|
231
|
+
original copyright holder who places the Program under this License
|
232
|
+
may add an explicit geographical distribution limitation excluding
|
233
|
+
those countries, so that distribution is permitted only in or among
|
234
|
+
countries not thus excluded. In such case, this License incorporates
|
235
|
+
the limitation as if written in the body of this License.
|
236
|
+
|
237
|
+
9. The Free Software Foundation may publish revised and/or new versions
|
238
|
+
of the General Public License from time to time. Such new versions will
|
239
|
+
be similar in spirit to the present version, but may differ in detail to
|
240
|
+
address new problems or concerns.
|
241
|
+
|
242
|
+
Each version is given a distinguishing version number. If the Program
|
243
|
+
specifies a version number of this License which applies to it and "any
|
244
|
+
later version", you have the option of following the terms and conditions
|
245
|
+
either of that version or of any later version published by the Free
|
246
|
+
Software Foundation. If the Program does not specify a version number of
|
247
|
+
this License, you may choose any version ever published by the Free Software
|
248
|
+
Foundation.
|
249
|
+
|
250
|
+
10. If you wish to incorporate parts of the Program into other free
|
251
|
+
programs whose distribution conditions are different, write to the author
|
252
|
+
to ask for permission. For software which is copyrighted by the Free
|
253
|
+
Software Foundation, write to the Free Software Foundation; we sometimes
|
254
|
+
make exceptions for this. Our decision will be guided by the two goals
|
255
|
+
of preserving the free status of all derivatives of our free software and
|
256
|
+
of promoting the sharing and reuse of software generally.
|
257
|
+
|
258
|
+
NO WARRANTY
|
259
|
+
|
260
|
+
11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
|
261
|
+
FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
|
262
|
+
OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
|
263
|
+
PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
|
264
|
+
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
|
265
|
+
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
|
266
|
+
TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
|
267
|
+
PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
|
268
|
+
REPAIR OR CORRECTION.
|
269
|
+
|
270
|
+
12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
|
271
|
+
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
|
272
|
+
REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
|
273
|
+
INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
|
274
|
+
OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
|
275
|
+
TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
|
276
|
+
YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
|
277
|
+
PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
|
278
|
+
POSSIBILITY OF SUCH DAMAGES.
|
279
|
+
|
280
|
+
END OF TERMS AND CONDITIONS
|
281
|
+
|
282
|
+
How to Apply These Terms to Your New Programs
|
283
|
+
|
284
|
+
If you develop a new program, and you want it to be of the greatest
|
285
|
+
possible use to the public, the best way to achieve this is to make it
|
286
|
+
free software which everyone can redistribute and change under these terms.
|
287
|
+
|
288
|
+
To do so, attach the following notices to the program. It is safest
|
289
|
+
to attach them to the start of each source file to most effectively
|
290
|
+
convey the exclusion of warranty; and each file should have at least
|
291
|
+
the "copyright" line and a pointer to where the full notice is found.
|
292
|
+
|
293
|
+
<one line to give the program's name and a brief idea of what it does.>
|
294
|
+
Copyright (C) <year> <name of author>
|
295
|
+
|
296
|
+
This program is free software; you can redistribute it and/or modify
|
297
|
+
it under the terms of the GNU General Public License as published by
|
298
|
+
the Free Software Foundation; either version 2 of the License, or
|
299
|
+
(at your option) any later version.
|
300
|
+
|
301
|
+
This program is distributed in the hope that it will be useful,
|
302
|
+
but WITHOUT ANY WARRANTY; without even the implied warranty of
|
303
|
+
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
304
|
+
GNU General Public License for more details.
|
305
|
+
|
306
|
+
You should have received a copy of the GNU General Public License
|
307
|
+
along with this program; if not, write to the Free Software
|
308
|
+
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
|
309
|
+
|
310
|
+
|
311
|
+
Also add information on how to contact you by electronic and paper mail.
|
312
|
+
|
313
|
+
If the program is interactive, make it output a short notice like this
|
314
|
+
when it starts in an interactive mode:
|
315
|
+
|
316
|
+
Gnomovision version 69, Copyright (C) year name of author
|
317
|
+
Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
|
318
|
+
This is free software, and you are welcome to redistribute it
|
319
|
+
under certain conditions; type `show c' for details.
|
320
|
+
|
321
|
+
The hypothetical commands `show w' and `show c' should show the appropriate
|
322
|
+
parts of the General Public License. Of course, the commands you use may
|
323
|
+
be called something other than `show w' and `show c'; they could even be
|
324
|
+
mouse-clicks or menu items--whatever suits your program.
|
325
|
+
|
326
|
+
You should also get your employer (if you work as a programmer) or your
|
327
|
+
school, if any, to sign a "copyright disclaimer" for the program, if
|
328
|
+
necessary. Here is a sample; alter the names:
|
329
|
+
|
330
|
+
Yoyodyne, Inc., hereby disclaims all copyright interest in the program
|
331
|
+
`Gnomovision' (which makes passes at compilers) written by James Hacker.
|
332
|
+
|
333
|
+
<signature of Ty Coon>, 1 April 1989
|
334
|
+
Ty Coon, President of Vice
|
335
|
+
|
336
|
+
This General Public License does not permit incorporating your program into
|
337
|
+
proprietary programs. If your program is a subroutine library, you may
|
338
|
+
consider it more useful to permit linking proprietary applications with the
|
339
|
+
library. If this is what you want to do, use the GNU Library General
|
340
|
+
Public License instead of this License.
|
data/ChangeLog
ADDED
File without changes
|
data/INSTALL
ADDED
@@ -0,0 +1,231 @@
|
|
1
|
+
Please see the doc/ directory for more specific installation instructions.
|
2
|
+
|
3
|
+
Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002 Free Software
|
4
|
+
Foundation, Inc.
|
5
|
+
|
6
|
+
This file is free documentation; the Free Software Foundation gives
|
7
|
+
unlimited permission to copy, distribute and modify it.
|
8
|
+
|
9
|
+
Basic Installation
|
10
|
+
==================
|
11
|
+
|
12
|
+
These are generic installation instructions.
|
13
|
+
|
14
|
+
The `configure' shell script attempts to guess correct values for
|
15
|
+
various system-dependent variables used during compilation. It uses
|
16
|
+
those values to create a `Makefile' in each directory of the package.
|
17
|
+
It may also create one or more `.h' files containing system-dependent
|
18
|
+
definitions. Finally, it creates a shell script `config.status' that
|
19
|
+
you can run in the future to recreate the current configuration, and a
|
20
|
+
file `config.log' containing compiler output (useful mainly for
|
21
|
+
debugging `configure').
|
22
|
+
|
23
|
+
It can also use an optional file (typically called `config.cache'
|
24
|
+
and enabled with `--cache-file=config.cache' or simply `-C') that saves
|
25
|
+
the results of its tests to speed up reconfiguring. (Caching is
|
26
|
+
disabled by default to prevent problems with accidental use of stale
|
27
|
+
cache files.)
|
28
|
+
|
29
|
+
If you need to do unusual things to compile the package, please try
|
30
|
+
to figure out how `configure' could check whether to do them, and mail
|
31
|
+
diffs or instructions to the address given in the `README' so they can
|
32
|
+
be considered for the next release. If you are using the cache, and at
|
33
|
+
some point `config.cache' contains results you don't want to keep, you
|
34
|
+
may remove or edit it.
|
35
|
+
|
36
|
+
The file `configure.ac' (or `configure.in') is used to create
|
37
|
+
`configure' by a program called `autoconf'. You only need
|
38
|
+
`configure.ac' if you want to change it or regenerate `configure' using
|
39
|
+
a newer version of `autoconf'.
|
40
|
+
|
41
|
+
The simplest way to compile this package is:
|
42
|
+
|
43
|
+
1. `cd' to the directory containing the package's source code and type
|
44
|
+
`./configure' to configure the package for your system. If you're
|
45
|
+
using `csh' on an old version of System V, you might need to type
|
46
|
+
`sh ./configure' instead to prevent `csh' from trying to execute
|
47
|
+
`configure' itself.
|
48
|
+
|
49
|
+
Running `configure' takes awhile. While running, it prints some
|
50
|
+
messages telling which features it is checking for.
|
51
|
+
|
52
|
+
2. Type `make' to compile the package.
|
53
|
+
|
54
|
+
3. Optionally, type `make check' to run any self-tests that come with
|
55
|
+
the package.
|
56
|
+
|
57
|
+
4. Type `make install' to install the programs and any data files and
|
58
|
+
documentation.
|
59
|
+
|
60
|
+
5. You can remove the program binaries and object files from the
|
61
|
+
source code directory by typing `make clean'. To also remove the
|
62
|
+
files that `configure' created (so you can compile the package for
|
63
|
+
a different kind of computer), type `make distclean'. There is
|
64
|
+
also a `make maintainer-clean' target, but that is intended mainly
|
65
|
+
for the package's developers. If you use it, you may have to get
|
66
|
+
all sorts of other programs in order to regenerate files that came
|
67
|
+
with the distribution.
|
68
|
+
|
69
|
+
Compilers and Options
|
70
|
+
=====================
|
71
|
+
|
72
|
+
Some systems require unusual options for compilation or linking that
|
73
|
+
the `configure' script does not know about. Run `./configure --help'
|
74
|
+
for details on some of the pertinent environment variables.
|
75
|
+
|
76
|
+
You can give `configure' initial values for configuration parameters
|
77
|
+
by setting variables in the command line or in the environment. Here
|
78
|
+
is an example:
|
79
|
+
|
80
|
+
./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
|
81
|
+
|
82
|
+
*Note Defining Variables::, for more details.
|
83
|
+
|
84
|
+
Compiling For Multiple Architectures
|
85
|
+
====================================
|
86
|
+
|
87
|
+
You can compile the package for more than one kind of computer at the
|
88
|
+
same time, by placing the object files for each architecture in their
|
89
|
+
own directory. To do this, you must use a version of `make' that
|
90
|
+
supports the `VPATH' variable, such as GNU `make'. `cd' to the
|
91
|
+
directory where you want the object files and executables to go and run
|
92
|
+
the `configure' script. `configure' automatically checks for the
|
93
|
+
source code in the directory that `configure' is in and in `..'.
|
94
|
+
|
95
|
+
If you have to use a `make' that does not support the `VPATH'
|
96
|
+
variable, you have to compile the package for one architecture at a
|
97
|
+
time in the source code directory. After you have installed the
|
98
|
+
package for one architecture, use `make distclean' before reconfiguring
|
99
|
+
for another architecture.
|
100
|
+
|
101
|
+
Installation Names
|
102
|
+
==================
|
103
|
+
|
104
|
+
By default, `make install' will install the package's files in
|
105
|
+
`/usr/local/bin', `/usr/local/man', etc. You can specify an
|
106
|
+
installation prefix other than `/usr/local' by giving `configure' the
|
107
|
+
option `--prefix=PATH'.
|
108
|
+
|
109
|
+
You can specify separate installation prefixes for
|
110
|
+
architecture-specific files and architecture-independent files. If you
|
111
|
+
give `configure' the option `--exec-prefix=PATH', the package will use
|
112
|
+
PATH as the prefix for installing programs and libraries.
|
113
|
+
Documentation and other data files will still use the regular prefix.
|
114
|
+
|
115
|
+
In addition, if you use an unusual directory layout you can give
|
116
|
+
options like `--bindir=PATH' to specify different values for particular
|
117
|
+
kinds of files. Run `configure --help' for a list of the directories
|
118
|
+
you can set and what kinds of files go in them.
|
119
|
+
|
120
|
+
If the package supports it, you can cause programs to be installed
|
121
|
+
with an extra prefix or suffix on their names by giving `configure' the
|
122
|
+
option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
|
123
|
+
|
124
|
+
Optional Features
|
125
|
+
=================
|
126
|
+
|
127
|
+
Some packages pay attention to `--enable-FEATURE' options to
|
128
|
+
`configure', where FEATURE indicates an optional part of the package.
|
129
|
+
They may also pay attention to `--with-PACKAGE' options, where PACKAGE
|
130
|
+
is something like `gnu-as' or `x' (for the X Window System). The
|
131
|
+
`README' should mention any `--enable-' and `--with-' options that the
|
132
|
+
package recognizes.
|
133
|
+
|
134
|
+
For packages that use the X Window System, `configure' can usually
|
135
|
+
find the X include and library files automatically, but if it doesn't,
|
136
|
+
you can use the `configure' options `--x-includes=DIR' and
|
137
|
+
`--x-libraries=DIR' to specify their locations.
|
138
|
+
|
139
|
+
Specifying the System Type
|
140
|
+
==========================
|
141
|
+
|
142
|
+
There may be some features `configure' cannot figure out
|
143
|
+
automatically, but needs to determine by the type of machine the package
|
144
|
+
will run on. Usually, assuming the package is built to be run on the
|
145
|
+
_same_ architectures, `configure' can figure that out, but if it prints
|
146
|
+
a message saying it cannot guess the machine type, give it the
|
147
|
+
`--build=TYPE' option. TYPE can either be a short name for the system
|
148
|
+
type, such as `sun4', or a canonical name which has the form:
|
149
|
+
|
150
|
+
CPU-COMPANY-SYSTEM
|
151
|
+
|
152
|
+
where SYSTEM can have one of these forms:
|
153
|
+
|
154
|
+
OS KERNEL-OS
|
155
|
+
|
156
|
+
See the file `config.sub' for the possible values of each field. If
|
157
|
+
`config.sub' isn't included in this package, then this package doesn't
|
158
|
+
need to know the machine type.
|
159
|
+
|
160
|
+
If you are _building_ compiler tools for cross-compiling, you should
|
161
|
+
use the `--target=TYPE' option to select the type of system they will
|
162
|
+
produce code for.
|
163
|
+
|
164
|
+
If you want to _use_ a cross compiler, that generates code for a
|
165
|
+
platform different from the build platform, you should specify the
|
166
|
+
"host" platform (i.e., that on which the generated programs will
|
167
|
+
eventually be run) with `--host=TYPE'.
|
168
|
+
|
169
|
+
Sharing Defaults
|
170
|
+
================
|
171
|
+
|
172
|
+
If you want to set default values for `configure' scripts to share,
|
173
|
+
you can create a site shell script called `config.site' that gives
|
174
|
+
default values for variables like `CC', `cache_file', and `prefix'.
|
175
|
+
`configure' looks for `PREFIX/share/config.site' if it exists, then
|
176
|
+
`PREFIX/etc/config.site' if it exists. Or, you can set the
|
177
|
+
`CONFIG_SITE' environment variable to the location of the site script.
|
178
|
+
A warning: not all `configure' scripts look for a site script.
|
179
|
+
|
180
|
+
Defining Variables
|
181
|
+
==================
|
182
|
+
|
183
|
+
Variables not defined in a site shell script can be set in the
|
184
|
+
environment passed to `configure'. However, some packages may run
|
185
|
+
configure again during the build, and the customized values of these
|
186
|
+
variables may be lost. In order to avoid this problem, you should set
|
187
|
+
them in the `configure' command line, using `VAR=value'. For example:
|
188
|
+
|
189
|
+
./configure CC=/usr/local2/bin/gcc
|
190
|
+
|
191
|
+
will cause the specified gcc to be used as the C compiler (unless it is
|
192
|
+
overridden in the site shell script).
|
193
|
+
|
194
|
+
`configure' Invocation
|
195
|
+
======================
|
196
|
+
|
197
|
+
`configure' recognizes the following options to control how it
|
198
|
+
operates.
|
199
|
+
|
200
|
+
`--help'
|
201
|
+
`-h'
|
202
|
+
Print a summary of the options to `configure', and exit.
|
203
|
+
|
204
|
+
`--version'
|
205
|
+
`-V'
|
206
|
+
Print the version of Autoconf used to generate the `configure'
|
207
|
+
script, and exit.
|
208
|
+
|
209
|
+
`--cache-file=FILE'
|
210
|
+
Enable the cache: use and save the results of the tests in FILE,
|
211
|
+
traditionally `config.cache'. FILE defaults to `/dev/null' to
|
212
|
+
disable caching.
|
213
|
+
|
214
|
+
`--config-cache'
|
215
|
+
`-C'
|
216
|
+
Alias for `--cache-file=config.cache'.
|
217
|
+
|
218
|
+
`--quiet'
|
219
|
+
`--silent'
|
220
|
+
`-q'
|
221
|
+
Do not print messages saying which checks are being made. To
|
222
|
+
suppress all normal output, redirect it to `/dev/null' (any error
|
223
|
+
messages will still be shown).
|
224
|
+
|
225
|
+
`--srcdir=DIR'
|
226
|
+
Look for the package's source code in directory DIR. Usually
|
227
|
+
`configure' can determine that directory automatically.
|
228
|
+
|
229
|
+
`configure' also accepts some other, not widely useful, options. Run
|
230
|
+
`configure --help' for more details.
|
231
|
+
|