Changeset cdf30aba in rtems


Ignore:
Timestamp:
Oct 27, 1998, 7:28:20 PM (21 years ago)
Author:
Joel Sherrill <joel.sherrill@…>
Branches:
4.10, 4.11, 4.8, 4.9, master
Children:
c19a4847
Parents:
71e1207
Message:

Update from David Fiddes.

Location:
doc/started
Files:
4 edited

Legend:

Unmodified
Added
Removed
  • doc/started/Makefile

    r71e1207 rcdf30aba  
    4242# run texi2dvi twice to generate the xref's properly.
    4343$(PROJECT).dvi: $(FILES)
    44         $(TEXI2DVI) -v $(PROJECT).texi
    45         texi2dvi -v $(PROJECT).texi
     44        $(TEXI2DVI) $(PROJECT).texi
     45        texi2dvi $(PROJECT).texi
    4646
    4747intro.texi: intro.t versions.texi
  • doc/started/buildc.t

    r71e1207 rcdf30aba  
    222222@code{/bin/ksh} shell instead.
    223223
     224@subsection Linux
     225
     226@subsubsection Broken install Program
     227
     228Certain versions of GNU fileutils include a version of @code{install} which
     229does not work properly.  Please perform the following test to see if you
     230need to upgrade:
     231
     232@example
     233install -c -d /tmp/foo/bar
     234@end example
     235
     236If this does not create the specified directories your install
     237program will not install RTEMS properly.   You will need to upgrade
     238to at least GNU fileutile version 3.16 to resolve this problem.
     239
    224240@c
    225241@c  Reading the Documentation
  • doc/started/nt.t

    r71e1207 rcdf30aba  
    88
    99@set CYGWIN-VERSION B19
    10 @set CYGWIN-FTP http://www.cygnus.com/misc/gnu-win32
     10@set CYGWIN-FTP http://www.cygnus.com/misc/gnu-win32/
     11@set CYGWIN-COOLVIEW http://www.lexa.ru/sos/
    1112@set DOS2UNIX-FTP ftp://ftp.micros.hensa.ac.uk/platforms/ibm-pc/ms-dos/simtelnet/txtutl/dos2unix.zip
    1213@set PFE-FTP http://www.lancs.ac.uk/people/cpaap/pfe/
     
    1516
    1617This chapter discusses the installation of the GNU tool chain
    17 on a computer running either the Microsoft Windows95
    18 or WindowsNT operating system.
     18on a computer running the Microsoft Windows NT operating system.
    1919
    2020This chapter is based on a draft provided by
    2121Geoffroy Montel <g_montel@@yahoo.com>.  Geoffroy's
    2222procedure was based on information from
    23 David Fiddes <D.J.Fiddes@@hw.ac.uk>.
     23David Fiddes <D.J@@fiddes.surfaid.org>.
    2424Their input and feedback is greatly appreciated.
    2525
     
    3030
    3131This installation process works well under Windows NT.
    32 It is said to also work under Windows95 (although it
    33 did not work with B18). Anyway, the resulting code works
    34 under both NT and 95.
     32Using Windows 95 or 98 is not recommended although it
     33should be possible with version 3.77 of gmake and an updated
     34cygwinb19.dll.
    3535
    3636This procedure should also work with newer version of
     
    5050You will have to uncompress many archives during this
    5151process.  You must @b{NOT} use @code{WinZip} or
    52 @code{PKZip}.  Instead the un-achiving process uses
     52@code{PKZip}.  Instead the un-archiving process uses
    5353the GNU @code{zip} and @code{tar} programs as shown below:
    5454
     
    9797@end ifclear
    9898
     99You @b{must} change the format of every patched file
     100for the toolset build to work correctly.
    99101
    100102@subsection Files Needed
     
    118120@end ifclear
    119121
    120 @item usertools.exe
     122@item coolview.tar.gz
    121123@ifset use-html
    122 @href{@value{CYGWIN-FTP},,@value{CYGWIN-FTP}}
     124@href{@value{CYGWIN-COOLVIEW},,@value{CYGWIN-COOLVIEW}}
    123125@end ifset
    124126@ifclear use-html
    125 @value{CYGWIN-FTP}
     127@value{CYGWIN-COOLVIEW}
    126128@end ifclear
    127129
    128130@end table
     131
     132@subsection System Requirements
     133
     134Although the finished cross-compiler is fairly easy on resources
     135building it can take a significant amount of processing power and
     136disk space. The recommended build system spec is:
     137
     138@itemize @bullet
     139
     140@item An AMD K6-300, Pentium II-300 or better processor. GNU C and Cygwin32 are
     141@b{very} CPU hungry.
     142
     143@item At least 64MB of RAM.
     144
     145@item At least 400MB of FAT16 disk space or 250MB if you have an NTFS partition.
     146
     147@end itemize
     148
     149Even with this spec of machine expect the full suite to take over 2 hours to
     150build with a further hour for RTEMS itself.
     151
    129152
    130153@section Installing Cygwin32 B19
     
    138161
    139162@item Execute cdk.exe. These instructions assume that you
    140 install Cygwin32 under the <RTOS>\GnuWin32\b19 directory.
    141 
    142 @item Execute usertools.exe.  These instructions assume that you
    143 install Cygwin32 under the <RTOS>\GnuWin32\b19 directory.
     163install Cygwin32 under the <RTOS>\cygnus\b19 directory.
    144164
    145165@item Execute Cygwin.bat (either on the start menu or
    146 under <RTOS>\GnuWin32\b19).
     166under <RTOS>\cygnus\b19).
    147167
    148168@item At this point, you are at the command line of @code{bash},
     
    154174@end example
    155175
    156 For example, the following sequence creates an MS-DOS virtual
    157 drive @code{O:} using an MS-DOS command window and then mounts
    158 that virtual drive as the root directory for the Cygwin32 environment:
    159 
    160 @example
    161 subst o: <RTOS>
     176For example, the following sequence mounts the @code{E:\unix} as the
     177root directory for the Cygwin32 environment. Note the use of two @code{\}s
     178when specifying DOS paths in bash:
     179
     180@example
    162181umount /
    163 mount -b o: /
    164 @end example
    165 
    166 @item Create the /bin, /tmp, /build and /usr directories.
     182mount -b e:\\unix /
     183@end example
     184
     185@item Create the /bin, /tmp, /source and /build directories.
    167186
    168187@example
    169188mkdir /bin
    170189mkdir /tmp
     190mkdir /source
    171191mkdir /build
    172 mkdir /usr
     192mkdir /build/binutils
     193mkdir /build/egcs
    173194@end example
    174195
     
    177198
    178199@example
    179 cd <RTOS>/GnuWin32/b19/bin
     200cd <RTOS>/cygnus/b19/H-i386-cygwin32/bin
    180201mv sh.exe old_sh.exe
    181202cp bash.exe sh.exe
    182203@end example
    183204
    184 The Bourne shell often has to be present in /bin directory when installing
    185 new packages.
     205The Bourne shell has to be present in /bin directory to run shell scripts properly:
     206
     207@example
     208cp <RTOS>/cygnus/b19/H-i386-cygwin32/bin/sh.exe /bin
     209cp <RTOS>/cygnus/b19/H-i386-cygwin32/bin/bash.exe /bin
     210@end example
     211
    186212
    187213@item Open the file
    188 @code{/gnuwin32/b19/H-i386-cygwin32/lib/gcc-lib/i386-cygwin32/2.7-b19/specs},
     214@code{/cygnus/b19/H-i386-cygwin32/lib/gcc-lib/i386-cygwin32/2.7-b19/specs},
    189215and change the following line:
    190216
     
    213239
    214240@item Unarchive @value{BINUTILS-TAR} following the
    215 instructions in @ref{Unarchiving the Tools}.   Apply the
    216 appropriate RTEMS specific patch as detailed in
     241instructions in @ref{Unarchiving the Tools} into the /source directory.
     242Apply the appropriate RTEMS specific patch as detailed in
    217243@ref{Apply RTEMS Patch to binutils}.
    218244
    219245@b{NOTE}: See @ref{Bug in Patch Utility}.
    220246
    221 @item In the @code{/build} directory, execute the following
     247@item In the @code{/build/binutils} directory, execute the following
    222248command to configure @value{BINUTILS-VERSION}:
    223249
    224250@example
    225 @value{BINUTILS-UNTAR}/configure --verbose --target=m68k-rtems \
    226     --prefix=/gcc-m68k-rtems --with-gnu-as \
    227     --with-gnu-ld --with-targets=all --with-newlib --with-multilib
     251/source/@value{BINUTILS-UNTAR}/configure --verbose --target=m68k-rtems \
     252    --prefix=/gcc-m68k-rtems --with-gnu-as --with-gnu-ld
    228253@end example
    229254
     
    238263@end example
    239264
    240 @item With B19, an error will occur. Remove the ".exe" suffix
    241 from the tools by finding them all and renaming them
    242 as shown below:
    243 
    244 @example
    245 find . -name *.exe -print
    246 mv XXX/gas.exe XXX/gas
    247        ....
    248 @end example
    249 
    250265@item Install the full package with the following command:
    251266
    252267@example
    253 make install
    254 @end example
    255 
    256 @item There is a problem with the gnu info package
    257 which may prevent it from building correctly.  To
    258 get around this try again with:
    259 
    260 @example
    261268make -k install
    262269@end example
    263270
    264 @item Once the executables are installed,
    265 you can restore the ".exe" suffix to the files in
    266 the @code{/gcc-m68k-rtems/bin} and
    267 @code{/gcc-m68k-rtems/m68k-rtems/bin} directories again.
     271There is a problem with the gnu info package which will cause an
     272error during installation. Telling make to keep going with -k allows
     273the install to complete.
    268274
    269275@item In the @code{cygnus.bat} file, add the directory
    270 to the cross-compiler executables to your search path
    271 by adding the following line:
    272 
    273 @example
    274 PATH=O:\gcc-m68k-rtems\bin;%PATH%
    275 @end example
    276 
    277 @item You can erase the /build directory content.
     276containing the cross-compiler executables to your search path
     277by inserting the following line:
     278
     279@example
     280PATH=E:\unix\gcc-m68k-rtems\bin;%PATH%
     281@end example
     282
     283@item You can erase the /build/binutils directory content if
     284disk space is tight.
    278285
    279286@item Exit bash and run @code{cygnus.bat} to restart
    280 the Cygwin32 environment.
     287the Cygwin32 environment with the new path.
    281288
    282289@end enumerate
     
    296303@b{NOTE}: See @ref{Bug in Patch Utility}.
    297304
    298 @item Remove the following directories (we do not need Fortran
    299 or Objective-C):
    300 
    301 @example
    302 · /build/@value{GCC-UNTAR}/libf2c
    303 · /build/@value{GCC-UNTAR}/gcc/objc
    304 · /build/@value{GCC-UNTAR}/gcc/f
     305@item Remove the following directories (we cannot use Fortran
     306or Objective-C as Cygwin32 cross-compilers):
     307
     308@example
     309/source/@value{GCC-UNTAR}/libf2c
     310/source/@value{GCC-UNTAR}/gcc/objc
     311/source/@value{GCC-UNTAR}/gcc/f
    305312@end example
    306313
    307314@b{NOTE}: See @ref{Bug in Patch Utility}.
    308315
    309 @item Copy to /build/@value{GCC-UNTAR}/ the following directories:
     316@item Link the following directories from Newlib to the main EGCS directory,
     317/source/@value{GCC-UNTAR}/ :
    310318
    311319@itemize @bullet
    312 @item /build/@value{NEWLIB-UNTAR}/newlib
    313 @item /build/@value{NEWLIB-UNTAR}/libgloss
     320@item ln -s ../@value{NEWLIB-UNTAR}/newlib newlib
     321@item ln -s ../@value{NEWLIB-UNTAR}/libgloss libgloss
    314322@end itemize
    315323
    316 @item Go under /build directory and run:
    317 
    318 @example
    319 ../@value{GCC-UNTAR}/configure --verbose --target=m68k-rtems \
     324@item Change to the /build/egcs directory to configure the compiler:
     325
     326@example
     327/source/@value{GCC-UNTAR}/configure --verbose --target=m68k-rtems \
    320328    --prefix=/gcc-m68k --with-gnu-as --with-gnu-ld \
    321     --with-targets=all --with-newlib --with-multilib
     329    --with-newlib
    322330@end example
    323331
     
    326334list of the targets available.
    327335
    328 @item Then run your favourite Unix format compaatible file editor,
    329 and edit /build/@value{GCC-UNTAR}/gcc/Makefile
    330 Search for the section:
    331 
    332 @example
    333 # libgcc1-test target (must also be overridable for a target)
    334 LIBGCC1_TEST = libgcc1-test
    335 @end example
    336 
    337 and change it to read:
    338 
    339 @example
    340 LIBGCC1_TEST =
    341 @end example
    342 
    343 @item Search for the section:
    344 
    345 @example
    346 # Set this to `ld' to enable use of collect2.
    347 USE_COLLECT2 =
    348 MAYBE_USE_COLLECT2 =
    349 # It is convenient for configure to add the assignment at the beginning,
    350 # so don't override it here.
    351 USE_COLLECT2 = ld
    352 @end example
    353 
    354 and change it to read:
    355 
    356 @example
    357 USE_COLLECT2 =
    358 @end example
    359 
    360 This changes are needed due to a @code{collect2} problem in B19.
    361 
    362336@item Compile the toolset as follows:
    363337
     
    368342You must do a @code{make cross} (not a simple @code{make})
    369343to insure that the different packages are built in the correct
    370 order.   This command could take a long time to run depending on
    371 the speed of the computer you are using.
     344order.   Making the compiler can take several hours even on
     345fairly fast machines, beware
    372346
    373347@item Install with the following command:
     
    378352
    379353@item Just as with binutils package, a problem with the gnu
    380 info package not building correctly may occur, so try again with:
     354info package not building correctly requires that you use -k to
     355keep going.
    381356
    382357@example
  • doc/started/versions.texi

    r71e1207 rcdf30aba  
    7777@c
    7878
    79 @set RTEMS-VERSION   RTEMS 4.0.0-beta4
    80 @set RTEMS-TAR       rtems-4.0.0-beta4.tgz
    81 @set RTEMS-UNTAR     rtems-4.0.0-beta4
     79@set RTEMS-VERSION   RTEMS 4.0.0-beta4b
     80@set RTEMS-TAR       rtems-4.0.0-beta4b.tgz
     81@set RTEMS-UNTAR     rtems-4.0.0-beta4b
    8282@set RTEMS-FTPSITE   ftp.OARcorp.com
    8383@set RTEMS-FTPDIR    /oarcorp/private/beta4
Note: See TracChangeset for help on using the changeset viewer.