* drop 'packages/contents' from base paths again (we are back to

using /boot/system, /boot/common and /boot/home/config
  as packagefs mount-points)

git-svn-id: file:///srv/svn/repos/haiku/buildtools/branches/package-management@40804 a95241bf-73f2-0310-859d-f6bbb57e9c96
This commit is contained in:
Oliver Tappe 2011-03-04 13:35:25 +00:00 committed by Ingo Weinhold
parent 419eb668e4
commit cb66866b95
10 changed files with 787 additions and 807 deletions

View File

@ -1,4 +1,4 @@
How to build gcc-2.95.3 for BeOS:
How to build gcc-2.95.3 for Haiku:
cd into the buildtools/legacy folder
@ -13,7 +13,7 @@ compile binutils:
mkdir binutils-obj
cd binutils-obj
CFLAGS="-O2" CXXFLAGS="-O2" ../binutils/configure \
--prefix=/boot/develop/abi/x86/gcc2/tools/gcc-2.95.3-haiku-${GCCDATE} \
--prefix=/boot/common/develop/tools/gcc-2.95.3-${GCCDATE} \
--disable-nls --enable-shared=yes
make
cd ..
@ -24,14 +24,14 @@ compile gcc:
mkdir gcc-obj
cd gcc-obj
CFLAGS="-O2" CXXFLAGS="-O2" ../gcc/configure \
--prefix=/boot/develop/abi/x86/gcc2/tools/gcc-2.95.3-haiku-${GCCDATE} \
--prefix=/boot/common/develop/tools/gcc-2.95.3-${GCCDATE} \
--disable-nls --enable-shared=yes --enable-languages=c,c++
make bootstrap
# the above will fail when compiling builtinbuf.cc, but we can ignore that
# since it's trying to build libstdc++.so, which haiku provides anyway
cd ..
Ok, now everything is compiled and ready, waiting to be installed:
Ok, now everything is compiled and ready, waiting to be packaged:
mkdir /boot/develop/abi/x86/gcc2/tools/gcc-2.95.3-haiku-${GCCDATE}
cd binutils-obj

View File

@ -1,7 +1,7 @@
#!/bin/sh
# Builds a GCC package from the installation specified by $GCCDATE (or via the
# arguments).
# Usage: build-gcc2-optional-package-Haiku.sh [gcc-base-dir] [version]
# Usage: build-gcc2-package-Haiku.sh [gcc-base-dir] [version]
packages_build=/boot/common/packages/build
@ -28,7 +28,7 @@ else
fi
current_dir=$(pwd)
base=/boot/common/packages/contents/develop/tools/gcc-2.95.3-$GCCDATE
base=/boot/common/develop/tools/gcc-2.95.3-$GCCDATE
if [ ! -d "$base" ]; then
echo GCC directory \"$base\" does not exist!
exit
@ -98,9 +98,10 @@ rm -f $base/lib/gcc-lib/i586-pc-haiku/2.95.3-haiku-$GCCDATE/include/math.h
echo "Install C++ includes & library"
rm -rf $base/include/g++
ln -snf /boot/system/packages/contents/develop/headers/c++/2.95.3 $base/include/g++
ln -snf /boot/system/develop/headers/c++/2.95.3 $base/include/g++
ln -snf /boot/system/packages/contents/lib/libstdc++.r4.so $base/lib/
ln -snf /boot/system/lib/libstdc++.r4.so $base/lib/
ln -snf /boot/system/lib/libstdc++.so $base/lib/
### package ###########################################

View File

@ -1,7 +1,4 @@
This is
/home/bonefish/develop/haiku/buildtools/legacy/binutils/bfd/doc/bfd.info,
produced by makeinfo version 4.9 from
/home/bonefish/develop/haiku/buildtools/legacy/binutils/bfd/doc/bfd.texinfo.
This is /home/zooey/Sources/haiku/buildtools.pm/legacy/binutils/bfd/doc/bfd.info, produced by makeinfo version 4.13 from /home/zooey/Sources/haiku/buildtools.pm/legacy/binutils/bfd/doc/bfd.texinfo.
START-INFO-DIR-ENTRY
* Bfd: (bfd). The Binary File Descriptor library.
@ -14,8 +11,8 @@ END-INFO-DIR-ENTRY
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.1
or any later version published by the Free Software Foundation;
with no Invariant Sections, with no Front-Cover Texts, and with no
Back-Cover Texts. A copy of the license is included in the
with no Invariant Sections, with no Front-Cover Texts, and with no
Back-Cover Texts. A copy of the license is included in the
section entitled "GNU Free Documentation License".

@ -6841,9 +6838,9 @@ The linker proper will call the `_bfd_link_add_symbols' entry point for
each object file or archive which is to be linked (typically these are
the files named on the command line, but some may also come from the
linker script). The entry point is responsible for examining the file.
For an object file, BFD must add any relevant symbol information to
the hash table. For an archive, BFD must determine which elements of
the archive should be used and adding them to the link.
For an object file, BFD must add any relevant symbol information to the
hash table. For an archive, BFD must determine which elements of the
archive should be used and adding them to the link.
The a.out version of this entry point is
`NAME(aout,link_add_symbols)'.
@ -8728,20 +8725,19 @@ Appendix A GNU Free Documentation License
H. Include an unaltered copy of this License.
I. Preserve the section entitled "History", and its title, and add
to it an item stating at least the title, year, new authors, and
publisher of the Modified Version as given on the Title Page.
If there is no section entitled "History" in the Document,
create one stating the title, year, authors, and publisher of
the Document as given on its Title Page, then add an item
publisher of the Modified Version as given on the Title Page. If
there is no section entitled "History" in the Document, create
one stating the title, year, authors, and publisher of the
Document as given on its Title Page, then add an item
describing the Modified Version as stated in the previous
sentence.
J. Preserve the network location, if any, given in the Document for
public access to a Transparent copy of the Document, and
likewise the network locations given in the Document for
previous versions it was based on. These may be placed in the
"History" section. You may omit a network location for a work
that was published at least four years before the Document
itself, or if the original publisher of the version it refers
to gives permission.
public access to a Transparent copy of the Document, and likewise
the network locations given in the Document for previous versions
it was based on. These may be placed in the "History" section.
You may omit a network location for a work that was published at
least four years before the Document itself, or if the original
publisher of the version it refers to gives permission.
K. In any section entitled "Acknowledgements" or "Dedications",
preserve the section's title, and preserve in the section all the
substance and tone of each of the contributor acknowledgements
@ -10241,67 +10237,67 @@ Index

Tag Table:
Node: Top820
Node: Overview1152
Node: History2203
Node: How It Works3149
Node: What BFD Version 2 Can Do4691
Node: BFD information loss6006
Node: Canonical format8538
Node: BFD front end12910
Node: Memory Usage38524
Node: Initialization39752
Node: Sections40211
Node: Section Input40694
Node: Section Output42059
Node: typedef asection44545
Node: section prototypes69502
Node: Symbols79182
Node: Reading Symbols80777
Node: Writing Symbols81884
Node: Mini Symbols83593
Node: typedef asymbol84567
Node: symbol handling functions89485
Node: Archives94827
Node: Formats98553
Node: Relocations101501
Node: typedef arelent102228
Node: howto manager118039
Node: Core Files180319
Node: Targets182136
Node: bfd_target184106
Node: Architectures204186
Node: Opening and Closing225618
Node: Internal236620
Node: File Caching242953
Node: Linker Functions244867
Node: Creating a Linker Hash Table246540
Node: Adding Symbols to the Hash Table248278
Node: Differing file formats249178
Node: Adding symbols from an object file250926
Node: Adding symbols from an archive253077
Node: Performing the Final Link255491
Node: Information provided by the linker256733
Node: Relocating the section contents257887
Node: Writing the symbol table259638
Node: Hash Tables262631
Node: Creating and Freeing a Hash Table263829
Node: Looking Up or Entering a String265079
Node: Traversing a Hash Table266332
Node: Deriving a New Hash Table Type267121
Node: Define the Derived Structures268187
Node: Write the Derived Creation Routine269268
Node: Write Other Derived Routines271892
Node: BFD back ends273207
Node: What to Put Where273477
Node: aout273615
Node: coff279933
Node: elf304410
Node: mmo305273
Node: File layout306201
Node: Symbol-table311848
Node: mmo section mapping315617
Node: GNU Free Documentation License319269
Node: Index338994
Node: Top818
Node: Overview1150
Node: History2201
Node: How It Works3147
Node: What BFD Version 2 Can Do4689
Node: BFD information loss6004
Node: Canonical format8536
Node: BFD front end12908
Node: Memory Usage38522
Node: Initialization39750
Node: Sections40209
Node: Section Input40692
Node: Section Output42057
Node: typedef asection44543
Node: section prototypes69500
Node: Symbols79180
Node: Reading Symbols80775
Node: Writing Symbols81882
Node: Mini Symbols83591
Node: typedef asymbol84565
Node: symbol handling functions89483
Node: Archives94825
Node: Formats98551
Node: Relocations101499
Node: typedef arelent102226
Node: howto manager118037
Node: Core Files180317
Node: Targets182134
Node: bfd_target184104
Node: Architectures204184
Node: Opening and Closing225616
Node: Internal236618
Node: File Caching242951
Node: Linker Functions244865
Node: Creating a Linker Hash Table246538
Node: Adding Symbols to the Hash Table248276
Node: Differing file formats249176
Node: Adding symbols from an object file250924
Node: Adding symbols from an archive253075
Node: Performing the Final Link255489
Node: Information provided by the linker256731
Node: Relocating the section contents257885
Node: Writing the symbol table259636
Node: Hash Tables262629
Node: Creating and Freeing a Hash Table263827
Node: Looking Up or Entering a String265077
Node: Traversing a Hash Table266330
Node: Deriving a New Hash Table Type267119
Node: Define the Derived Structures268185
Node: Write the Derived Creation Routine269266
Node: Write Other Derived Routines271890
Node: BFD back ends273205
Node: What to Put Where273475
Node: aout273613
Node: coff279931
Node: elf304408
Node: mmo305271
Node: File layout306199
Node: Symbol-table311846
Node: mmo section mapping315615
Node: GNU Free Documentation License319267
Node: Index338980

End Tag Table

View File

@ -1,7 +1,4 @@
This is
/home/bonefish/develop/haiku/buildtools/legacy/binutils/binutils/doc/binutils.info,
produced by makeinfo version 4.9 from
/home/bonefish/develop/haiku/buildtools/legacy/binutils/binutils/doc/binutils.texi.
This is /home/zooey/Sources/haiku/buildtools.pm/legacy/binutils/binutils/doc/binutils.info, produced by makeinfo version 4.13 from /home/zooey/Sources/haiku/buildtools.pm/legacy/binutils/binutils/doc/binutils.texi.
START-INFO-DIR-ENTRY
* Binutils: (binutils). The GNU binary utilities.
@ -507,7 +504,7 @@ object files are listed as arguments, `nm' assumes the file `a.out'.
same name. If the symbol is defined anywhere, the common
symbols are treated as undefined references. For more
details on common symbols, see the discussion of -warn-common
in *Note Linker options: (ld.info)Options.
in *note Linker options: (ld.info)Options.
`D'
The symbol is in the initialized data section.
@ -561,7 +558,7 @@ object files are listed as arguments, `nm' assumes the file `a.out'.
this case, the next values printed are the stabs other field,
the stabs desc field, and the stab type. Stabs symbols are
used to hold debugging information. For more information,
see *Note Stabs: (stabs.info)Top.
see *note Stabs: (stabs.info)Top.
`?'
The symbol type is unknown, or object file format specific.
@ -1575,7 +1572,7 @@ equivalent. At least one option from the list
ELF section. In most other file formats, debugging symbol-table
entries are interleaved with linkage symbols, and are visible in
the `--syms' output. For more information on stabs symbols, see
*Note Stabs: (stabs.info)Top.
*note Stabs: (stabs.info)Top.
`--start-address=ADDRESS'
Start displaying data at the specified address. This affects the
@ -2244,7 +2241,7 @@ file language used in header files, see the `linkers' section,
`NLMLINK' in particular, of the `NLM Development and Tools Overview',
which is part of the NLM Software Developer's Kit ("NLM SDK"),
available from Novell, Inc. `nlmconv' uses the GNU Binary File
Descriptor library to read INFILE; see *Note BFD: (ld.info)BFD, for
Descriptor library to read INFILE; see *note BFD: (ld.info)BFD, for
more information.
`nlmconv' can perform a link step. In other words, you can list
@ -2379,7 +2376,7 @@ available to Windows.
This is a BFD target name; you can use the `--help' option to see
a list of supported targets. Normally `windres' will use the
default format, which is the first one listed by the `--help'
option. *Note Target Selection::.
option. *note Target Selection::.
`--preprocessor PROGRAM'
When `windres' reads an `rc' file, it runs it through the C
@ -3473,20 +3470,19 @@ Appendix A GNU Free Documentation License
H. Include an unaltered copy of this License.
I. Preserve the section entitled "History", and its title, and add
to it an item stating at least the title, year, new authors, and
publisher of the Modified Version as given on the Title Page.
If there is no section entitled "History" in the Document,
create one stating the title, year, authors, and publisher of
the Document as given on its Title Page, then add an item
publisher of the Modified Version as given on the Title Page. If
there is no section entitled "History" in the Document, create
one stating the title, year, authors, and publisher of the
Document as given on its Title Page, then add an item
describing the Modified Version as stated in the previous
sentence.
J. Preserve the network location, if any, given in the Document for
public access to a Transparent copy of the Document, and
likewise the network locations given in the Document for
previous versions it was based on. These may be placed in the
"History" section. You may omit a network location for a work
that was published at least four years before the Document
itself, or if the original publisher of the version it refers
to gives permission.
public access to a Transparent copy of the Document, and likewise
the network locations given in the Document for previous versions
it was based on. These may be placed in the "History" section.
You may omit a network location for a work that was published at
least four years before the Document itself, or if the original
publisher of the version it refers to gives permission.
K. In any section entitled "Acknowledgements" or "Dedications",
preserve the section's title, and preserve in the section all the
substance and tone of each of the contributor acknowledgements
@ -3805,33 +3801,33 @@ Index

Tag Table:
Node: Top1847
Node: ar3400
Node: ar cmdline5578
Node: ar scripts13721
Node: nm19409
Node: objcopy27605
Node: objdump50657
Node: ranlib65570
Node: size66325
Node: strings69172
Node: strip71522
Node: c++filt77001
Ref: c++filt-Footnote-181929
Node: addr2line82035
Node: nlmconv85306
Node: windres87912
Node: dlltool93645
Node: def file format104483
Node: readelf106221
Node: Common Options110929
Node: Selecting The Target System111969
Node: Target Selection112901
Node: Architecture Selection114883
Node: Reporting Bugs115711
Node: Bug Criteria116490
Node: Bug Reporting117043
Node: GNU Free Documentation License124137
Node: Index143869
Node: Top1848
Node: ar3401
Node: ar cmdline5579
Node: ar scripts13722
Node: nm19410
Node: objcopy27606
Node: objdump50658
Node: ranlib65571
Node: size66326
Node: strings69173
Node: strip71523
Node: c++filt77002
Ref: c++filt-Footnote-181930
Node: addr2line82036
Node: nlmconv85307
Node: windres87913
Node: dlltool93646
Node: def file format104484
Node: readelf106222
Node: Common Options110930
Node: Selecting The Target System111970
Node: Target Selection112902
Node: Architecture Selection114884
Node: Reporting Bugs115712
Node: Bug Criteria116491
Node: Bug Reporting117044
Node: GNU Free Documentation License124138
Node: Index143858

End Tag Table

File diff suppressed because it is too large Load Diff

View File

@ -1,7 +1,4 @@
This is
/home/bonefish/develop/haiku/buildtools/legacy/binutils/ld/ld.info,
produced by makeinfo version 4.9 from
/home/bonefish/develop/haiku/buildtools/legacy/binutils/ld/ld.texinfo.
This is /home/zooey/Sources/haiku/buildtools.pm/legacy/binutils/ld/ld.info, produced by makeinfo version 4.13 from /home/zooey/Sources/haiku/buildtools.pm/legacy/binutils/ld/ld.texinfo.
START-INFO-DIR-ENTRY
* Ld: (ld). The GNU linker.
@ -216,14 +213,14 @@ GNU linker:
The default format is taken from the environment variable
`GNUTARGET'. *Note Environment::. You can also define the input
format from a script, using the command `TARGET'; see *Note Format
format from a script, using the command `TARGET'; see *note Format
Commands::.
`-c MRI-COMMANDFILE'
`--mri-script=MRI-COMMANDFILE'
For compatibility with linkers produced by MRI, `ld' accepts script
files written in an alternate, restricted command language,
described in *Note MRI Compatible Script Files: MRI. Introduce
described in *note MRI Compatible Script Files: MRI. Introduce
MRI script files with the option `-c'; use the `-T' option to run
linker scripts written in the general-purpose `ld' scripting
language. If MRI-CMDFILE does not exist, `ld' looks for it in the
@ -276,7 +273,7 @@ GNU linker:
You can also use the version script to control what symbols should
be added to the dynamic symbol table if the output format supports
it. See the description of `--version-script' in *Note VERSION::.
it. See the description of `--version-script' in *note VERSION::.
`-EB'
Link big-endian objects. This affects the default output format.
@ -461,7 +458,7 @@ GNU linker:
[0x0000000c] foo = (foo * 0x4)
[0x0000000c] foo = (foo + 0x8)
See *Note Expressions:: for more information about
See *note Expressions:: for more information about
expressions in linker scripts.
`-n'
@ -712,10 +709,10 @@ GNU linker:
Tells the linker to accept input files whose architecture cannot be
recognised. The assumption is that the user knows what they are
doing and deliberately wants to link in these unknown input files.
This was the default behaviour of the linker, before release
2.14. The default behaviour from release 2.14 onwards is to
reject such input files, and so the `--accept-unknown-input-arch'
option has been added to restore the old behaviour.
This was the default behaviour of the linker, before release 2.14.
The default behaviour from release 2.14 onwards is to reject such
input files, and so the `--accept-unknown-input-arch' option has
been added to restore the old behaviour.
`--as-needed'
`--no-as-needed'
@ -2049,7 +2046,7 @@ Several linker script commands deal with files.
the "sysroot prefix". Otherwise, the linker will try to open the
file in the current directory. If it is not found, the linker
will search through the archive library search path. See the
description of `-L' in *Note Command Line Options: Options.
description of `-L' in *note Command Line Options: Options.
If you use `INPUT (-lFILE)', `ld' will transform the name to
`libFILE.a', as with the command line argument `-l'.
@ -2063,7 +2060,7 @@ Several linker script commands deal with files.
The `GROUP' command is like `INPUT', except that the named files
should all be archives, and they are searched repeatedly until no
new undefined references are created. See the description of `-('
in *Note Command Line Options: Options.
in *note Command Line Options: Options.
`AS_NEEDED(FILE, FILE, ...)'
`AS_NEEDED(FILE FILE ...)'
@ -2237,14 +2234,14 @@ only use this within a `SECTIONS' command. *Note Location Counter::.
The semicolon after EXPRESSION is required.
Expressions are defined below; see *Note Expressions::.
Expressions are defined below; see *note Expressions::.
You may write symbol assignments as commands in their own right, or
as statements within a `SECTIONS' command, or as part of an output
section description in a `SECTIONS' command.
The section of the symbol will be set from the section of the
expression; for more information, see *Note Expression Section::.
expression; for more information, see *note Expression Section::.
Here is an example showing the three different places that symbol
assignments may be used:
@ -2501,7 +2498,7 @@ the name should be supplied as a quoted numeric string. A section name
may consist of any sequence of characters, but a name which contains
any unusual characters such as commas must be quoted.
The output section name `/DISCARD/' is special; *Note Output Section
The output section name `/DISCARD/' is special; *note Output Section
Discarding::.

@ -2532,7 +2529,7 @@ output section to the current value of the location counter. The
second will set it to the current value of the location counter aligned
to the strictest alignment of a `.text' input section.
The ADDRESS may be an arbitrary expression; *Note Expressions::.
The ADDRESS may be an arbitrary expression; *note Expressions::.
For example, if you want to align the section on a 0x10 byte boundary,
so that the lowest four bits of the section address are zero, you could
do something like this:
@ -2979,9 +2976,8 @@ like this:
OUTPUT-SECTION-COMMAND
...
} [>REGION] [AT>LMA_REGION] [:PHDR :PHDR ...] [=FILLEXP]
We've already described SECTION, ADDRESS, and
OUTPUT-SECTION-COMMAND. In this section we will describe the remaining
section attributes.
We've already described SECTION, ADDRESS, and OUTPUT-SECTION-COMMAND.
In this section we will describe the remaining section attributes.
* Menu:
@ -3033,7 +3029,7 @@ File: ld.info, Node: Output Section LMA, Next: Forced Output Alignment, Prev:
..........................
Every section has a virtual address (VMA) and a load address (LMA); see
*Note Basic Script Concepts::. The address expression which may appear
*note Basic Script Concepts::. The address expression which may appear
in an output section description sets the VMA (*note Output Section
Address::).
@ -3231,11 +3227,11 @@ section.
.text0 { o1/*.o(.text) }
.text1 { o2/*.o(.text) }
}
This will define both `.text0' and `.text1' to start at address
0x1000. `.text0' will be loaded at address 0x4000, and `.text1' will
be loaded immediately after `.text0'. The following symbols will be
defined: `__load_start_text0', `__load_stop_text0',
`__load_start_text1', `__load_stop_text1'.
This will define both `.text0' and `.text1' to start at address 0x1000.
`.text0' will be loaded at address 0x4000, and `.text1' will be loaded
immediately after `.text0'. The following symbols will be defined:
`__load_start_text0', `__load_stop_text0', `__load_start_text1',
`__load_stop_text1'.
C code to copy overlay `.text1' into the overlay area might look
like the following.
@ -3274,8 +3270,8 @@ regions that become too full. The linker will not shuffle sections
around to fit into the available regions.
A linker script may contain at most one use of the `MEMORY' command.
However, you can define as many blocks of memory within it as you
wish. The syntax is:
However, you can define as many blocks of memory within it as you wish.
The syntax is:
MEMORY
{
NAME [(ATTR)] : ORIGIN = ORIGIN, LENGTH = LEN
@ -3290,7 +3286,7 @@ have a distinct name.
The ATTR string is an optional list of attributes that specify
whether to use a particular memory region for an input section which is
not explicitly mapped in the linker script. As described in *Note
not explicitly mapped in the linker script. As described in *note
SECTIONS::, if you do not specify an output section for some input
section, the linker will create an output section with the same name as
the input section. If you define region attributes, the linker will use
@ -4022,11 +4018,10 @@ use in linker script expressions.
variable = ALIGN(0x8000);
}
... }
The first use of `ALIGN' in this example specifies the
location of a section because it is used as the optional ADDRESS
attribute of a section definition (*note Output Section
Address::). The second use of `ALIGN' is used to defines the
value of a symbol.
The first use of `ALIGN' in this example specifies the location of
a section because it is used as the optional ADDRESS attribute of
a section definition (*note Output Section Address::). The second
use of `ALIGN' is used to defines the value of a symbol.
The builtin function `NEXT' is closely related to `ALIGN'.
@ -4595,7 +4590,7 @@ File: ld.info, Node: WIN32, Next: Xtensa, Prev: TI COFF, Up: Machine Depende
==================================
This section describes some of the win32 specific `ld' issues. See
*Note Command Line Options: Options. for detailed decription of the
*note Command Line Options: Options. for detailed decription of the
command line options mentioned here.
_import libraries_
@ -5306,13 +5301,12 @@ leave it out, state it!
Often people omit facts because they think they know what causes the
problem and assume that some details do not matter. Thus, you might
assume that the name of a symbol you use in an example does not matter.
Well, probably it does not, but one cannot be sure. Perhaps the bug
is a stray memory reference which happens to fetch from the location
where that name is stored in memory; perhaps, if the name were
different, the contents of that location would fool the linker into
doing the right thing despite the bug. Play it safe and give a
specific, complete example. That is the easiest thing for you to do,
and the most helpful.
Well, probably it does not, but one cannot be sure. Perhaps the bug is
a stray memory reference which happens to fetch from the location where
that name is stored in memory; perhaps, if the name were different, the
contents of that location would fool the linker into doing the right
thing despite the bug. Play it safe and give a specific, complete
example. That is the easiest thing for you to do, and the most helpful.
Keep in mind that the purpose of a bug report is to enable us to fix
the bug if it is new to us. Therefore, always write your bug reports
@ -5444,7 +5438,7 @@ Appendix A MRI Compatible Script Files
To aid users making the transition to GNU `ld' from the MRI linker,
`ld' can use MRI compatible linker scripts as an alternative to the
more general-purpose linker scripting language described in *Note
more general-purpose linker scripting language described in *note
Scripts::. MRI compatible linker scripts have a much simpler command
set than the scripting language otherwise used with `ld'. GNU `ld'
supports the most commonly used MRI linker commands; these commands are
@ -5746,20 +5740,19 @@ Appendix B GNU Free Documentation License
H. Include an unaltered copy of this License.
I. Preserve the section entitled "History", and its title, and add
to it an item stating at least the title, year, new authors, and
publisher of the Modified Version as given on the Title Page.
If there is no section entitled "History" in the Document,
create one stating the title, year, authors, and publisher of
the Document as given on its Title Page, then add an item
publisher of the Modified Version as given on the Title Page. If
there is no section entitled "History" in the Document, create
one stating the title, year, authors, and publisher of the
Document as given on its Title Page, then add an item
describing the Modified Version as stated in the previous
sentence.
J. Preserve the network location, if any, given in the Document for
public access to a Transparent copy of the Document, and
likewise the network locations given in the Document for
previous versions it was based on. These may be placed in the
"History" section. You may omit a network location for a work
that was published at least four years before the Document
itself, or if the original publisher of the version it refers
to gives permission.
public access to a Transparent copy of the Document, and likewise
the network locations given in the Document for previous versions
it was based on. These may be placed in the "History" section.
You may omit a network location for a work that was published at
least four years before the Document itself, or if the original
publisher of the version it refers to gives permission.
K. In any section entitled "Acknowledgements" or "Dedications",
preserve the section's title, and preserve in the section all the
substance and tone of each of the contributor acknowledgements
@ -6209,7 +6202,7 @@ Index
* BFD requirements: BFD. (line 16)
* big-endian objects: Options. (line 198)
* binary input format: Options. (line 115)
* BLOCK(EXP): Builtin Functions. (line 62)
* BLOCK(EXP): Builtin Functions. (line 61)
* bug criteria: Bug Criteria. (line 6)
* bug reports: Bug Reporting. (line 6)
* bugs in ld: Reporting Bugs. (line 6)
@ -6245,14 +6238,14 @@ Index
* data: Output Section Data.
(line 6)
* DATA_SEGMENT_ALIGN(MAXPAGESIZE, COMMONPAGESIZE): Builtin Functions.
(line 67)
* DATA_SEGMENT_END(EXP): Builtin Functions. (line 88)
* DATA_SEGMENT_RELRO_END(OFFSET, EXP): Builtin Functions. (line 94)
(line 66)
* DATA_SEGMENT_END(EXP): Builtin Functions. (line 87)
* DATA_SEGMENT_RELRO_END(OFFSET, EXP): Builtin Functions. (line 93)
* dbx: Options. (line 1074)
* DEF files, creating: Options. (line 1470)
* default emulation: Environment. (line 21)
* default input format: Environment. (line 9)
* DEFINED(SYMBOL): Builtin Functions. (line 105)
* DEFINED(SYMBOL): Builtin Functions. (line 104)
* deleting local symbols: Options. (line 513)
* demangling, default: Environment. (line 29)
* demangling, from command line: Options. (line 752)
@ -6317,7 +6310,7 @@ Index
* grouping input files: File Commands. (line 44)
* groups of archives: Options. (line 609)
* H8/300 support: H8/300. (line 6)
* header size: Builtin Functions. (line 170)
* header size: Builtin Functions. (line 169)
* heap size: Options. (line 1412)
* help: Options. (line 792)
* holes: Location Counter. (line 12)
@ -6366,7 +6359,7 @@ Index
* LDEMULATION: Environment. (line 21)
* len =: MEMORY. (line 72)
* LENGTH =: MEMORY. (line 72)
* LENGTH(MEMORY): Builtin Functions. (line 122)
* LENGTH(MEMORY): Builtin Functions. (line 121)
* library search path in linker script: File Commands. (line 71)
* link map: Options. (line 347)
* link-time runtime library search path: Options. (line 967)
@ -6383,7 +6376,7 @@ Index
* little-endian objects: Options. (line 201)
* LOAD (MRI): MRI. (line 84)
* load address: Output Section LMA. (line 6)
* LOADADDR(SECTION): Builtin Functions. (line 125)
* LOADADDR(SECTION): Builtin Functions. (line 124)
* loading, preventing: Output Section Type.
(line 22)
* local symbols, deleting: Options. (line 517)
@ -6395,14 +6388,14 @@ Index
(line 46)
* machine dependencies: Machine Dependent. (line 6)
* mapping input sections to output sections: Input Section. (line 6)
* MAX: Builtin Functions. (line 130)
* MAX: Builtin Functions. (line 129)
* MEMORY: MEMORY. (line 6)
* memory region attributes: MEMORY. (line 32)
* memory regions: MEMORY. (line 6)
* memory regions and sections: Output Section Region.
(line 6)
* memory usage: Options. (line 804)
* MIN: Builtin Functions. (line 133)
* MIN: Builtin Functions. (line 132)
* MRI compatibility: MRI. (line 6)
* MSP430 extra sections: MSP430. (line 11)
* NAME (MRI): MRI. (line 90)
@ -6410,13 +6403,13 @@ Index
(line 6)
* names: Symbols. (line 6)
* naming the output file: Options. (line 404)
* NEXT(EXP): Builtin Functions. (line 137)
* NEXT(EXP): Builtin Functions. (line 136)
* NMAGIC: Options. (line 384)
* NOCROSSREFS(SECTIONS): Miscellaneous Commands.
(line 30)
* NOLOAD: Output Section Type.
(line 22)
* not enough room for program headers: Builtin Functions. (line 175)
* not enough room for program headers: Builtin Functions. (line 174)
* o =: MEMORY. (line 67)
* objdump -i: BFD. (line 6)
* object file management: BFD. (line 6)
@ -6430,7 +6423,7 @@ Index
* ORDER (MRI): MRI. (line 95)
* org =: MEMORY. (line 67)
* ORIGIN =: MEMORY. (line 67)
* ORIGIN(MEMORY): Builtin Functions. (line 143)
* ORIGIN(MEMORY): Builtin Functions. (line 142)
* orphan: Orphan Sections. (line 6)
* output file after errors: Options. (line 870)
* output file format in linker script: Format Commands. (line 10)
@ -6473,7 +6466,7 @@ Index
* program headers: PHDRS. (line 6)
* program headers and sections: Output Section Phdr.
(line 6)
* program headers, not enough room: Builtin Functions. (line 175)
* program headers, not enough room: Builtin Functions. (line 174)
* program segments: PHDRS. (line 6)
* PROVIDE: PROVIDE. (line 6)
* PROVIDE_HIDDEN: PROVIDE_HIDDEN. (line 6)
@ -6521,12 +6514,12 @@ Index
* section fill pattern: Output Section Fill.
(line 6)
* section load address: Output Section LMA. (line 6)
* section load address in expression: Builtin Functions. (line 125)
* section load address in expression: Builtin Functions. (line 124)
* section name: Output Section Name.
(line 6)
* section name wildcard patterns: Input Section Wildcards.
(line 6)
* section size: Builtin Functions. (line 154)
* section size: Builtin Functions. (line 153)
* section, assigning to memory region: Output Section Region.
(line 6)
* section, assigning to program header: Output Section Phdr.
@ -6535,13 +6528,13 @@ Index
* sections, discarding: Output Section Discarding.
(line 6)
* segment origins, cmd line: Options. (line 1090)
* SEGMENT_START(SEGMENT, DEFAULT): Builtin Functions. (line 146)
* SEGMENT_START(SEGMENT, DEFAULT): Builtin Functions. (line 145)
* segments, ELF: PHDRS. (line 6)
* shared libraries: Options. (line 1022)
* SHORT(EXPRESSION): Output Section Data.
(line 6)
* SIZEOF(SECTION): Builtin Functions. (line 154)
* SIZEOF_HEADERS: Builtin Functions. (line 170)
* SIZEOF(SECTION): Builtin Functions. (line 153)
* SIZEOF_HEADERS: Builtin Functions. (line 169)
* small common symbols: Input Section Common.
(line 20)
* SORT: Input Section Wildcards.
@ -6562,7 +6555,7 @@ Index
* SUBALIGN(SUBSECTION_ALIGN): Forced Input Alignment.
(line 6)
* suffixes for integers: Constants. (line 12)
* symbol defaults: Builtin Functions. (line 105)
* symbol defaults: Builtin Functions. (line 104)
* symbol definition, scripts: Assignments. (line 6)
* symbol names: Symbols. (line 6)
* symbol tracing: Options. (line 522)
@ -6579,7 +6572,7 @@ Index
* thumb entry point: ARM. (line 17)
* TI COFF versions: TI COFF. (line 6)
* traditional format: Options. (line 1069)
* unallocated address, next: Builtin Functions. (line 137)
* unallocated address, next: Builtin Functions. (line 136)
* undefined symbol: Options. (line 480)
* undefined symbol in linker script: Miscellaneous Commands.
(line 13)
@ -6613,10 +6606,10 @@ Index

Tag Table:
Node: Top449
Node: Overview1211
Node: Invocation2325
Node: Options2733
Node: Top450
Node: Overview1212
Node: Invocation2326
Node: Options2734
Node: Environment77388
Node: Scripts79148
Node: Basic Script Concepts80882
@ -6646,48 +6639,48 @@ Node: Output Section Data120371
Node: Output Section Keywords123148
Node: Output Section Discarding126717
Node: Output Section Attributes127673
Node: Output Section Type128677
Node: Output Section LMA129831
Node: Forced Output Alignment132102
Node: Forced Input Alignment132370
Node: Output Section Region132755
Node: Output Section Phdr133185
Node: Output Section Fill133849
Node: Overlay Description134991
Node: MEMORY139239
Node: PHDRS143439
Node: VERSION148478
Node: Expressions156269
Node: Constants157147
Node: Symbols157708
Node: Orphan Sections158446
Node: Location Counter159209
Node: Operators163513
Node: Evaluation164435
Node: Expression Section165799
Node: Builtin Functions167288
Node: Implicit Linker Scripts174780
Node: Machine Dependent175555
Node: H8/300176416
Node: i960178041
Node: ARM179726
Node: HPPA ELF32182642
Node: MMIX184265
Node: MSP430185482
Node: PowerPC ELF32186530
Node: PowerPC64 ELF64188821
Node: TI COFF193235
Node: WIN32193767
Node: Xtensa211841
Node: BFD214963
Node: BFD outline216418
Node: BFD information loss217704
Node: Canonical format220221
Node: Reporting Bugs224578
Node: Bug Criteria225272
Node: Bug Reporting225971
Node: MRI232996
Node: GNU Free Documentation License237639
Node: Index257353
Node: Output Section Type128676
Node: Output Section LMA129830
Node: Forced Output Alignment132101
Node: Forced Input Alignment132369
Node: Output Section Region132754
Node: Output Section Phdr133184
Node: Output Section Fill133848
Node: Overlay Description134990
Node: MEMORY139237
Node: PHDRS143436
Node: VERSION148475
Node: Expressions156266
Node: Constants157144
Node: Symbols157705
Node: Orphan Sections158443
Node: Location Counter159206
Node: Operators163510
Node: Evaluation164432
Node: Expression Section165796
Node: Builtin Functions167285
Node: Implicit Linker Scripts174772
Node: Machine Dependent175547
Node: H8/300176408
Node: i960178033
Node: ARM179718
Node: HPPA ELF32182634
Node: MMIX184257
Node: MSP430185474
Node: PowerPC ELF32186522
Node: PowerPC64 ELF64188813
Node: TI COFF193227
Node: WIN32193759
Node: Xtensa211833
Node: BFD214955
Node: BFD outline216410
Node: BFD information loss217696
Node: Canonical format220213
Node: Reporting Bugs224570
Node: Bug Criteria225264
Node: Bug Reporting225963
Node: MRI232988
Node: GNU Free Documentation License237631
Node: Index257333

End Tag Table

View File

@ -5,12 +5,12 @@ if [ -z $GCCDATE ]; then
exit 1
fi
export BELIBRARIES=/boot/common/packages/contents/lib:/boot/system/packages/contents/develop/lib
export BELIBRARIES=/boot/common/lib:/boot/system/develop/lib
mkdir -p binutils-obj
cd binutils-obj
CFLAGS="-O2" CXXFLAGS="-O2" ../binutils/configure \
--prefix=/boot/common/packages/contents/develop/tools/gcc-2.95.3-${GCCDATE} \
--prefix=/boot/common/develop/tools/gcc-2.95.3-${GCCDATE} \
--disable-nls --enable-shared=yes
make
cd ..

View File

@ -5,12 +5,12 @@ if [ -z $GCCDATE ]; then
exit 1
fi
export BELIBRARIES=/boot/common/packages/contents/lib:/boot/system/packages/contents/develop/lib
export BELIBRARIES=/boot/common/lib:/boot/system/develop/lib
mkdir -p gcc-obj
cd gcc-obj
CFLAGS="-O2" CXXFLAGS="-O2" ../gcc/configure \
--prefix=/boot/common/packages/contents/develop/tools/gcc-2.95.3-${GCCDATE} \
--prefix=/boot/common/develop/tools/gcc-2.95.3-${GCCDATE} \
--disable-nls --enable-shared=yes --enable-languages=c,c++
make bootstrap
cd ..

View File

@ -350,9 +350,9 @@ extern union tree_node *i386_pe_merge_decl_attributes ();
#undef SMALL_STACK
/* For native compiler, use standard Haiku include file search paths
rooted in /boot/system/packages/contents/develop/headers. For a cross
compiler, don't expect the host to use the Haiku directory scheme, and
instead look for the Haiku include files relative to TOOL_INCLUDE_DIR. */
rooted in /boot/system/develop/headers. For a cross compiler, don't expect
the host to use the Haiku directory scheme, and instead look for the Haiku
include files relative to TOOL_INCLUDE_DIR. */
#ifndef CROSS_COMPILE
#undef INCLUDE_DEFAULTS
@ -360,36 +360,36 @@ extern union tree_node *i386_pe_merge_decl_attributes ();
{ \
{ GPLUSPLUS_INCLUDE_DIR, "G++", 1, 1 },\
{ GCC_INCLUDE_DIR, "GCC", 0, 0 },\
{ "/boot/common/packages/contents/include", 0, 0, 0 },\
{ "/boot/system/packages/contents/develop/headers/os", 0, 0, 1 },\
{ "/boot/system/packages/contents/develop/headers/os/app", 0, 0, 1 },\
{ "/boot/system/packages/contents/develop/headers/os/device", 0, 0, 1 },\
{ "/boot/system/packages/contents/develop/headers/os/drivers", 0, 0, 1 },\
{ "/boot/system/packages/contents/develop/headers/os/game", 0, 0, 1 },\
{ "/boot/system/packages/contents/develop/headers/os/interface", 0, 0, 1 },\
{ "/boot/system/packages/contents/develop/headers/os/kernel", 0, 0, 1 },\
{ "/boot/system/packages/contents/develop/headers/os/locale", 0, 0, 1 },\
{ "/boot/system/packages/contents/develop/headers/os/mail", 0, 0, 1 },\
{ "/boot/system/packages/contents/develop/headers/os/media", 0, 0, 1 },\
{ "/boot/system/packages/contents/develop/headers/os/midi", 0, 0, 1 },\
{ "/boot/system/packages/contents/develop/headers/os/midi2", 0, 0, 1 },\
{ "/boot/system/packages/contents/develop/headers/os/net", 0, 0, 1 },\
{ "/boot/system/packages/contents/develop/headers/os/opengl", 0, 0, 1 },\
{ "/boot/system/packages/contents/develop/headers/os/storage", 0, 0, 1 },\
{ "/boot/system/packages/contents/develop/headers/os/support", 0, 0, 1 },\
{ "/boot/system/packages/contents/develop/headers/os/translation", 0, 0, 1 },\
{ "/boot/system/packages/contents/develop/headers/os/add-ons/graphics", 0, 0, 1 },\
{ "/boot/system/packages/contents/develop/headers/os/add-ons/input_server", 0, 0, 1 },\
{ "/boot/system/packages/contents/develop/headers/os/add-ons/screen_saver", 0, 0, 1 },\
{ "/boot/system/packages/contents/develop/headers/os/add-ons/tracker", 0, 0, 1 },\
{ "/boot/system/packages/contents/develop/headers/os/be_apps/Deskbar", 0, 0, 1 },\
{ "/boot/system/packages/contents/develop/headers/os/be_apps/NetPositive", 0, 0, 1 },\
{ "/boot/system/packages/contents/develop/headers/os/be_apps/Tracker", 0, 0, 1 },\
{ "/boot/system/packages/contents/develop/headers/3rdparty", 0, 0, 0 },\
{ "/boot/system/packages/contents/develop/headers/bsd", 0, 0, 0 },\
{ "/boot/system/packages/contents/develop/headers/glibc", 0, 0, 0 },\
{ "/boot/system/packages/contents/develop/headers/posix", 0, 0, 0 },\
{ "/boot/system/packages/contents/develop/headers", 0, 0, 0 }, \
{ "/boot/common/develop/headers", 0, 0, 0 },\
{ "/boot/system/develop/headers/os", 0, 0, 1 },\
{ "/boot/system/develop/headers/os/app", 0, 0, 1 },\
{ "/boot/system/develop/headers/os/device", 0, 0, 1 },\
{ "/boot/system/develop/headers/os/drivers", 0, 0, 1 },\
{ "/boot/system/develop/headers/os/game", 0, 0, 1 },\
{ "/boot/system/develop/headers/os/interface", 0, 0, 1 },\
{ "/boot/system/develop/headers/os/kernel", 0, 0, 1 },\
{ "/boot/system/develop/headers/os/locale", 0, 0, 1 },\
{ "/boot/system/develop/headers/os/mail", 0, 0, 1 },\
{ "/boot/system/develop/headers/os/media", 0, 0, 1 },\
{ "/boot/system/develop/headers/os/midi", 0, 0, 1 },\
{ "/boot/system/develop/headers/os/midi2", 0, 0, 1 },\
{ "/boot/system/develop/headers/os/net", 0, 0, 1 },\
{ "/boot/system/develop/headers/os/opengl", 0, 0, 1 },\
{ "/boot/system/develop/headers/os/storage", 0, 0, 1 },\
{ "/boot/system/develop/headers/os/support", 0, 0, 1 },\
{ "/boot/system/develop/headers/os/translation", 0, 0, 1 },\
{ "/boot/system/develop/headers/os/add-ons/graphics", 0, 0, 1 },\
{ "/boot/system/develop/headers/os/add-ons/input_server", 0, 0, 1 },\
{ "/boot/system/develop/headers/os/add-ons/screen_saver", 0, 0, 1 },\
{ "/boot/system/develop/headers/os/add-ons/tracker", 0, 0, 1 },\
{ "/boot/system/develop/headers/os/be_apps/Deskbar", 0, 0, 1 },\
{ "/boot/system/develop/headers/os/be_apps/NetPositive", 0, 0, 1 },\
{ "/boot/system/develop/headers/os/be_apps/Tracker", 0, 0, 1 },\
{ "/boot/system/develop/headers/3rdparty", 0, 0, 0 },\
{ "/boot/system/develop/headers/bsd", 0, 0, 0 },\
{ "/boot/system/develop/headers/glibc", 0, 0, 0 },\
{ "/boot/system/develop/headers/posix", 0, 0, 0 },\
{ "/boot/system/develop/headers", 0, 0, 0 }, \
{ 0, 0, 0, 0 } \
};
#else /* CROSS_COMPILE */

View File

@ -4,7 +4,7 @@ CROSS_LIBGCC1 =
# There are system headers elsewhere, but these are the ones that
# we are most likely to want to apply any fixes to.
SYSTEM_HEADER_DIR = /boot/system/packages/contents/develop/headers/posix
SYSTEM_HEADER_DIR = /boot/system/develop/headers/posix
CROSS_SYSTEM_HEADER_DIR := $(CROSS_SYSTEM_HEADER_DIR)/posix
# Use the system assert.h