1========================================
2Known problems in GPRBUILD version 1.3.0
3========================================
4
5Copyright (c) 2009, AdaCore
6
7The following is a listing of known problems in release 1.3.0. Except where
8specifically noted, all these problems have been corrected in the development
9tree of the 1.4 technology. This means they are corrected in any 1.3.0w
10wavefront issued subsequent to the date specified (in ISO format YYYY-MM-DD) in
11the status line. This can be used to determine if a given wavefront has the fix
12identified in the entry.
13
14KP-130-IA09-020 Wrong run path option for shared libs on Darwin
15
16  Problem:    On Darwin, where there should be one run path option per
17              directory, a single run path option for all the directory is
18              issued when linking a shared library.
19
20  Status:     This was fixed in 1.4.0 on 2009-10-09
21
22  Workaround: Use static libraries
23
24KP-130-IA01-027 Incorrect linking of shared library on Windows
25
26  Problem:    When gprbuild is invoked with --unchecked-shared-lib-imports
27              and a shared library imports a static ibrary, the linking of
28              the shared library may fail in Windows with undefined references.
29
30  Status:     This was fixed in 1.4.0 on 2009-10-02
31
32  Workaround: Add the necessary Library_Options
33
34KP-130-I904-011 Incorrect compilation in extending projects
35
36  Problem:    gprbuild incorrectly compiles up to date inherited sources
37              in extending projects and does not recompile non up-to-date
38              sources in projects extending externally built projects.
39
40  Status:     This was fixed in 1.4.0 on 2009-09-05
41
42  Workaround: Make the project being extended not externally built.
43
44KP-130-I828-007 Crash when using attribute Included_Switches
45
46  Problem:    When there are several languages in a project files and for
47              one of these languages attribute Included_Switches is declared,
48              gprbuild may crash.
49
50  Status:     This was fixed in 1.4.0 on 2009-08-29
51
52  Workaround: Use one project file for each language
53
54KP-130-I828-004 Failure to bind with a cross with no prefix
55
56  Problem:    When a cross-compiler with no prefix is used, gprbind fails as
57              it does not recognize "gnatbind_prefix=" as a special option.
58
59  Status:     This was fixed in 1.4.0 on 2009-09-01
60
61  Workaround: Remove the lines in package Binder of the configuration project
62              file that specify the option "gnatbind_prefix=".
63
64KP-130-I722-017 Systematic binding and linking when using extending projects
65
66  Problem:    If you are using extending projects, gprbuild will systematically
67              bind and link your application, even when everything is up to
68              date.
69
70  Status:     This was fixed in 1.4.0 on 2009-07-21
71
72  Workaround: The compilation still performs correctly, and is just a bit
73              slower
74
75KP-130-I713-011 gprclean does not remove binder files
76
77  Problem:    When the main unit's name is less than 3 characters long,
78              gprclean does not remove the binder generated files (b__*.ads,
79              b__*.adb and *.bexch files)
80
81  Status:     This was fixed in 1.4.0 on 2009-07-13
82
83  Workaround: Remove the files manually.
84
85KP-130-I525-017 gprbuild incompatible with option -r of gnatbind
86
87  Problem:    When a binder option such as -r that adds output to the
88              invocation of gnatbind is used, linking fails.
89
90  Status:     This was fixed in 1.4.0 on 2009-08-12
91
92  Workaround: Remove binder option -r
93
94KP-130-I507-019 Spec not compiled when body has been excluded
95
96  Problem:    When the body of a spec has been locally removed, the spec that
97              does not need a completion is not compiled.
98
99  Status:     This was fixed in 1.4.0 on 2009-05-19
100
101  Workaround: Use a spec with a dummy completion and a dummy body
102
103KP-130-I505-015 Extending library project not built
104
105  Problem:    When gprbuild is invoked for a library project that extends
106              another one, the library may not be built.
107
108  Status:     This was fixed in 1.4.0 on 2009-05-06
109
110  Workaround: Use only non extending library projects
111
112KP-130-I421-020 First compiler on the path not automatically used
113
114  Problem:    If the directory where gprbuild resides is not first on the path,
115              compilers that are in front of this directory in the path will
116              not be chosen in autoconfiguration.
117
118  Status:     This was fixed in 1.4.0 on 2009-09-08
119
120  Workaround: Create a configuration project file using gprconfig before
121              invoking gprbuild.
122