-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathREADME
38 lines (33 loc) · 1.56 KB
/
README
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
Building and installing GCC4TI from Git:
========================================
* After cloning the repository, building and installing GCC4TI is a matter of
executing the "updatesrc" script located in the trunk/tigcc-linux/scripts
folder, and then executing the install script:
$ cd trunk/tigcc-linux/scripts
$ ./updatesrc
(abort now and create a ticket if errors mentioning e.g. cp, rm, tar appear
during the execution of updatesrc)
$ cd ../gcc4ti-0.96b11
$ scripts/Install
Caution: the Win32 cross-build of the patched GCC 4.1.2 under Linux is known to
yield a working GCC executable under Debian 7 "Wheezy" (GCC 4.6), but a broken
GCC executable under Debian 8 "Jessie" (GCC 4.9) - floating-point values
generated by the compiler are simply wrong.
However, the native Linux build of the _same_ patched GCC 4.1.2, under Debian
Jessie and April 2016 Sid / Stretch, yields an executable which generates the
correct floating-point values.
Seems like the 10+-year-old (pre-GCC4TI) code of the GCC patch is broken in
(at least) one more way.
* You may also want to build a tarball that you can transfer to another
computer and install later. It's the "gcc4ti_src.tar.bz2" file mentioned in
the trunk/tigcc-linux/INSTALL file:
$ cd trunk/tigcc-linux/scripts
$ ./updatesrc
$ ./package_src
Then, on the target computer, you can proceed as described in the
trunk/tigcc-linux/INSTALL file, which is, basically:
* copy, or symlink, to the build directory, the files whose path in the
GCC4TI repository is:
pool/b/binutils-2.16.1.tar.bz2
pool/g/gcc-core-4.1.2.tar.bz2
* run scripts/Install