Your message dated Sun, 13 Jul 2014 01:38:55 +
with message-id
and subject line Bug#714577: Removed package(s) from unstable
has caused the Debian Bug report #380260,
regarding [Fixed in 4.6] gnat-4.1: Bug box in referenced_var_lookup, at
tree-dfa.c:581 at -O1, -O2
to be marked as done
Your message dated Fri, 5 Dec 2008 20:09:25 GMT
with message-id <[EMAIL PROTECTED]>
and subject line gnat-4.1 has been removed from Debian, closing #472974
has caused the Debian Bug report #472974,
regarding gnat-4.1: Depends on Tcl/Tk 8.3 which is subject to removal
to be marked as done.
Your message dated Fri, 5 Dec 2008 20:09:26 GMT
with message-id <[EMAIL PROTECTED]>
and subject line gnat-4.1 has been removed from Debian, closing #459390
has caused the Debian Bug report #459390,
regarding gnat-4.1: watch file should not specify current version
to be marked as done.
This
FYI: The status of the gnat-4.1 source package
in Debian's testing distribution has changed.
Previous version: 4.1.2-8
Current version: (not in testing)
Hint: <http://release.debian.org/britney/hints/adeodato>
# 2008-11-20; done 2008-11-21
# RM bug: #502423
The
Processing commands for controlbugs.debian.org:
> reassign 58329 gnat-4.3
Bug#58329: gnat library compiled with bad path to sources
Bug reassigned from package `gnat-4.1' to `gnat-4.3'.
> reassign 182359 gnat-4.3
Bug#182359: gnat: Erroneous warning given for some correct program
Your message dated Thu, 26 Jun 2008 13:45:15 +0400
with message-id <[EMAIL PROTECTED]>
and subject line This is already fixed
has caused the Debian Bug report #486525,
regarding gnat-doc depends on gnat-4.1-doc
to be marked as done.
This means that you claim that the problem has been deal
Package: gnat-doc
Version: 4:4.2.3.nf1
Severity: normal
gnat package depends on gnat-4.3, while gnat-doc still depends on
gnat-4.1-doc.
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'stable'), (50, 'unsta
#
# bts-link upstream status pull for source package gnat-4.1
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user [EMAIL PROTECTED]
# remote status report for #248173
# * http://gcc.gnu.org/PR16087
# * remote status changed: ASSIGNED -> RESOLVED
# * rem
Processing commands for [EMAIL PROTECTED]:
> #
> # bts-link upstream status pull for source package gnat-4.1
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user [EMAIL PROTECTED]
Setting user to [EMAIL PROTECTED] (was [EMAIL PROTECTED]).
> # re
#
# bts-link upstream status pull for source package gnat-4.1
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user [EMAIL PROTECTED]
# remote status report for #248173
# * http://gcc.gnu.org/PR16087
# * remote status changed: NEW -> ASSIGNED
usertags 248173 - sta
#
# bts-link upstream status pull for source package gnat-4.1
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user [EMAIL PROTECTED]
# remote status report for #247560
# * http://gcc.gnu.org/PR15915
# * remote status changed: NEW -> ASSIGNED
usertags 247560 - sta
Processing commands for [EMAIL PROTECTED]:
> tags 471614 wontfix
Bug#471614: gnat-4.1: FTBFS: b~gnatfind.adb:(.text+0x225): undefined reference
to `xr_tabls___elabs'
There were no tags set.
Tags added: wontfix
> thanks
Stopping processing here.
Please contact me if you need assistan
Source: gnat-4.1
Severity: important
Hi!
Your package currently build-depend on expect-tcl8.3 which in turn
depends on tcl8.3.
Debian Tcl/Tk packaging team is about to remove tcl8.3 (and tk8.3)
from Debian because it's really outdated (more than five years) and
imposes unnecessary burd
Your message dated Sun, 13 Jan 2008 15:36:51 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#459101: gnat-4.1: FTBFS with dash: CANNOT FIND debian/*FFI*
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
I
The problem is that debian/rules.conf assumes there are lib*FFI* files
that need to produce lib*ffi4* files, but that is not true. Instead,
the lib*ffi4* files are already there and are not generated.
I don't know precisely what triggers this bug, but this is somewhere
in the generation of debian
Package: gnat-4.1
version: 4.1.2-17
User: [EMAIL PROTECTED]
Usertags: qa-ftbfs-dash-20080103 qa-ftbfs-dash
Hi,
During a rebuild of all packages in sid using /bin/dash as /bin/sh, your
package failed to build.
Relevant part:
rm -f debian/substvars.local.tmp
( \
echo
#
# bts-link upstream status pull for source package gnat-4.1
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user [EMAIL PROTECTED]
# remote status report for #246385
# * http://gcc.gnu.org/PR15803
# * remote status changed: ASSIGNED -> RESOLVED
# * rem
#
# bts-link upstream status pull for source package gnat-4.1
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user [EMAIL PROTECTED]
# remote status report for #246186
# * http://gcc.gnu.org/PR15799
# * remote status changed: WAITING -> NEW
usertags 246186 - sta
Processing commands for [EMAIL PROTECTED]:
> #
> # bts-link upstream status pull for source package gnat-4.1
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user [EMAIL PROTECTED]
Setting user to [EMAIL PROTECTED] (was [EMAIL PROTECTED]).
> # re
Processing commands for [EMAIL PROTECTED]:
> #
> # bts-link upstream status pull for source package gnat-4.1
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user [EMAIL PROTECTED]
Setting user to [EMAIL PROTECTED] (was [EMAIL PROTECTED]).
> # re
#
# bts-link upstream status pull for source package gnat-4.1
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user [EMAIL PROTECTED]
# remote status report for #246184
# * http://gcc.gnu.org/PR15616
# * remote status changed: NEW -> RESOLVED
# * remote resolut
fixed 170352 4.1.2-17
close 170352
thanks
GNAT 4.1 properly issues the warning.
Processing commands for [EMAIL PROTECTED]:
> fixed 170352 4.1.2-17
Bug#170352: gnat: No warning when uninitialised variables used in record
aggregates
Bug marked as fixed in version 4.1.2-17.
> close 170352
Bug#170352: gnat: No warning when uninitialised variables used in record
aggregates
'clo
#
# bts-link upstream status pull for source package gnat-4.1
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user [EMAIL PROTECTED]
# remote status report for #446470
# * http://gcc.gnu.org/PR29283
# * remote status changed: (?) -> RESOLVED
# * remote resolut
too late, will fix in the next upload.
Ludovic Brenta writes:
> The recent upload of gcc-defaults introduces gnat (= 4.2.0-1) which is
> wrong for two reasons:
>
> - I do not want to make gnat-4.2 the default yet; neither in unstable
> nor in experimental.
>
> - The gnat package should not hav
The recent upload of gcc-defaults introduces gnat (= 4.2.0-1) which is
wrong for two reasons:
- I do not want to make gnat-4.2 the default yet; neither in unstable
nor in experimental.
- The gnat package should not have a minor version number, because it
might get out of sync with the version
FYI: The status of the gnat-4.1 source package
in Debian's testing distribution has changed.
Previous version: 4.1.1-22
Current version: 4.1.2-8
--
This email is automatically generated; [EMAIL PROTECTED] is responsible.
See http://people.debian.org/~henning/trille/ for more inform
#
# bts-link upstream status pull for source package gnat-4.1
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user [EMAIL PROTECTED]
# remote status report for #416973
# * http://gcc.gnu.org/PR31415
# * remote status changed: UNCONFIRMED -> RESOLVED
# * rem
Processing commands for [EMAIL PROTECTED]:
> retitle 416973 [Fixed in 4.3] Illegal program not detected, Ada 2005,
> 3.9.4(12/2) and 7.5(6.1/2)
Bug#416973: gnat-4.1: Illegal program not detected, Ada 2005, 3.9.4(12/2) and
7.5(6.1/2)
Changed Bug title to `[Fixed in 4.3] Illegal progr
Package: gnat-4.1
Version: 4.1.1-22
Severity: normal
Tags: confirmed, upstream
In the test case below, GCC emits correct type information for
Debugging.A but the type information for Extenal.B is incorrect.
package External is
type External_Type is array (1 .. 4) of Float;
B
system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: gnat-4.1
Version: 4.1.1-22
Severity: grave
Justification: renders package unusable (uninstallable)
Could you please upload GNAT 4.1.2 to unstable ASAP? As it stands,
cpp-4.1's conflict with gnat-4.1 (
> > > I see the listmasters have straightened this message out. I'm building
> > > gcj-4.1 on vivaldi.
> >
> > I'll try gnat-4.1 on washi.
>
> that doesn't make sense unless you did port gnat-4.1 for m68k.
That was a fast 'build', then
Michael Schmitz writes:
> > > While having built and uploaded things correctly for experimental, I
> > > didn't do the same for unstable, which now needs some manual
> > > intervention building gnat-4.1 and gcj-4.1.
> >
> > > gcj-4.1 (alpha arm m68
> > While having built and uploaded things correctly for experimental, I
> > didn't do the same for unstable, which now needs some manual
> > intervention building gnat-4.1 and gcj-4.1.
>
> > gcj-4.1 (alpha arm m68k mips mipsel s390 sparc):
> >
> > - n
On Thu, May 03, 2007 at 10:55:56AM +0200, Matthias Klose wrote:
> While having built and uploaded things correctly for experimental, I
> didn't do the same for unstable, which now needs some manual
> intervention building gnat-4.1 and gcj-4.1.
> gcj-4.1 (alpha arm m68k mips
#
# bts-link upstream status pull for source package gnat-4.1
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user [EMAIL PROTECTED]
# remote status report for #427107
# * http://gcc.gnu.org/PR32164
# * remote status changed: (?) -> NEW
usertags 427107 + status-
Package: gnat-4.1
Version: 4.1.1-22
Severity: normal
The following program prints FAILED; it should print PASSED
as per RM 3.4(27), which states:
-- "For the execution of a call on an inherited subprogram,
-- a call on the corresponding primitive subprogram of the
-- parent or progenitor ty
Package: gnat-4.1
Version: 4.1.1-22
Severity: normal
package Pak1 is
type T1 is tagged null record;
function Eq(X, Y : T1) return Boolean renames "=";
function Neq(X, Y : T1) return Boolean renames "/="; -- line 4
end Pak1;
gnatmake pak1 yields
gnatmake pak1
#
# bts-link upstream status pull for source package gnat-4.1
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user [EMAIL PROTECTED]
# remote status report for #329694
# * http://gcc.gnu.org/PR24019
# * remote status changed: UNCONFIRMED -> RESOLVED
# * rem
Processing commands for [EMAIL PROTECTED]:
> #
> # bts-link upstream status pull for source package gnat-4.1
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user [EMAIL PROTECTED]
Setting user to [EMAIL PROTECTED] (was [EMAIL PROTECTED]).
> # re
#
# bts-link upstream status pull for source package gnat-4.1
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user [EMAIL PROTECTED]
# remote status report for #244936
# * http://gcc.gnu.org/PR15606
# * remote status changed: NEW -> REOPENED
usertags 244936 - sta
Your message dated Wed, 09 May 2007 22:36:18 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug #421309: gnat-4.1: please upload 4.1.2 to resync with
gcc-4.1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt wi
Processing commands for [EMAIL PROTECTED]:
> #
> # bts-link upstream status pull for source package gnat-4.1
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user [EMAIL PROTECTED]
Setting user to [EMAIL PROTECTED] (was [EMAIL PROTECTED]).
> # re
While having built and uploaded things correctly for experimental, I
didn't do the same for unstable, which now needs some manual
intervention building gnat-4.1 and gcj-4.1.
gnat-4.1 (mips mipsel s390 sparc):
- work in a sid chroot
- install gnat-4.1-base libgnat-4.1 libgnatp
Matthias Klose writes:
> Ludovic, I forgot to update gnat-4.1 in unstable before updating
> gcc-4.1; building gnat-4.1_4.1.2 will require some manual
> action. Does something else in gnat-4.1 needs an update, or should I
> go ahead with current SVN?
You can go ahead. At your option
Ludovic, I forgot to update gnat-4.1 in unstable before updating
gcc-4.1; building gnat-4.1_4.1.2 will require some manual
action. Does something else in gnat-4.1 needs an update, or should I
go ahead with current SVN?
Matthias
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
Package: gnat-4.1
Version: 4.1.1-22
Severity: grave
Justification: renders package unusable (uninstallable)
Could you please upload GNAT 4.1.2 to unstable ASAP? As it stands,
cpp-4.1's conflict with gnat-4.1 (<= 4.1.1-22) makes gnat-4.1
uninstallable on systems that don't still have
#
# bts-link upstream status pull for source package gnat-4.1
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user [EMAIL PROTECTED]
# remote status report for #416973
# * http://gcc.gnu.org/PR31415
# * remote status changed: (?) -> UNCONFIRMED
usertags 416
Package: gnat-4.1
Version: 4.1.1-22
Severity: normal
In the program below, the full views (in the private part) of T2 and
T3 are both illegal because the value of the discriminant, x2, is not
static. RM 7.3(13) states that the parent subtype of T2 and T3
(i.e. T1) must impose a statically
Package: gnat-4.1
Version: 4.1.1-22
Severity: normal
In the program below, the full declaration of T2 (in the private part
of the package) is illegal because it conflicts with the public
declaration. The public declaration defines the discriminant, d1, to
have the value 3 whereas the private
Package: gnat-4.1
Version: 4.1.1-22
Severity: normal
In the following program, the declaration of T3 is illegal because it
extends a limited type (T1) and a nonlimited interface (T2).
-- compiled -gnat05
-- error not detected
package pak1 is
-- RM 3.9.4(12/2) and 7.5(6.1/2)
-- check that
Your message dated Sun, 18 Mar 2007 15:42:55 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#396609: gnat-4.1: Link fails (Message: gnatlink.adb:1731
range check failed)
has caused the attached Bug report to be marked as done.
This means that you claim that the problem ha
Ludovic Brenta <[EMAIL PROTECTED]> writes:
> Hi Matthieu,
>
> I have not been able to reproduce this bug, but it appears to be in a
> Windows-specific part of gnatlink which we can safely remove. Could
> you please try to recompile gnatlink with the following patch and see
> if it solves your pro
#
# bts-link upstream status pull for source package gnat-4.1
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user [EMAIL PROTECTED]
# remote status report for #395406
# * http://gcc.gnu.org/PR29623
# * remote status changed: (?) -> NEW
usertags 395406 + status-
FYI: The status of the gnat-4.1 source package
in Debian's testing distribution has changed.
Previous version: 4.1.1-19
Current version: 4.1.1-22
--
This email is automatically generated; [EMAIL PROTECTED] is responsible.
See http://people.debian.org/~henning/trille/ for more inform
tags 395406 confirmed upstream
forwarded 395406 http://gcc.gnu.org/PR29623
thanks
Sorry for replying so late, but I forwarded the bug upstream on
2006-10-17 and they confirmed it with a reduced test case.
--
Ludovic Brenta.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "uns
Processing commands for [EMAIL PROTECTED]:
> tags 395406 confirmed upstream
Bug#395406: gnat-4.1: Assert_Failure sinfo.adb:649
There were no tags set.
Tags added: confirmed, upstream
> forwarded 395406 http://gcc.gnu.org/PR29623
Bug#395406: gnat-4.1: Assert_Failure sinfo.adb:649
Note
Processing commands for [EMAIL PROTECTED]:
> #
> # bts-link upstream status pull for source package gnat-4.1
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user [EMAIL PROTECTED]
Setting user to [EMAIL PROTECTED] (was [EMAIL PROTECTED]).
> # re
#
# bts-link upstream status pull for source package gnat-4.1
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user [EMAIL PROTECTED]
# remote status report for #390101
# * http://gcc.gnu.org/PR29283
# * remote status changed: WAITING -> RESOLVED
# * rem
Processing commands for [EMAIL PROTECTED]:
> #
> # bts-link upstream status pull for source package gnat-4.1
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user [EMAIL PROTECTED]
Setting user to [EMAIL PROTECTED] (was [EMAIL PROTECTED]).
> # re
#
# bts-link upstream status pull for source package gnat-4.1
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user [EMAIL PROTECTED]
# remote status report for #244935
# * http://gcc.gnu.org/PR15605
# * remote status changed: NEW -> RESOLVED
# * remote resolut
Hi Matthieu,
I have not been able to reproduce this bug, but it appears to be in a
Windows-specific part of gnatlink which we can safely remove. Could
you please try to recompile gnatlink with the following patch and see
if it solves your problem?
--
Ludovic Brenta.
--- /tmp/ediff15040_Tp 200
FYI: The status of the gnat-4.1 source package
in Debian's testing distribution has changed.
Previous version: 4.1.1-16
Current version: 4.1.1-19
--
This email is automatically generated; [EMAIL PROTECTED] is responsible.
See http://people.debian.org/~henning/trille/ for more inform
Package: gnat-4.1
Version: 4.1.1-16
Severity: important
(Unfortunately, the program on which the error occurs can not be
published)
I'm getting the following error message:
$ gnatlink /path/to/file.ali
Exception name: CONSTRAINT_ERROR
Message: gnatlink.adb:1731 range check failed
gna
Subject: gnat-4.1: Assert_Failure sinfo.adb:649
Package: gnat-4.1
Version: 4.1.1-16
Severity: normal
*** Please type your report below this line ***
Trying to compile an Ada program, I have this bug with gnatmake :
$ gnatmake -gnat05 rv.adb
gcc-4.1 -c
FYI: The status of the gnat-4.1 source package
in Debian's testing distribution has changed.
Previous version: 4.1.1-15
Current version: 4.1.1-16
--
This email is automatically generated; [EMAIL PROTECTED] is responsible.
See http://people.debian.org/~henning/trille/ for more inform
FYI: The status of the gnat-4.1 source package
in Debian's testing distribution has changed.
Previous version: 4.1.1-10
Current version: 4.1.1-15
--
This email is automatically generated; [EMAIL PROTECTED] is responsible.
See http://people.debian.org/~henning/trille/ for more inform
#
# bts-link upstream status pull for source package gnat-4.1
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user [EMAIL PROTECTED]
# remote status report for #390101
# * http://gcc.gnu.org/PR29283
# * remote status changed: (?) -> WAITING
usertags 390101 + sta
Package: gnat-4.1
Version: 4.1.1-14
Severity: normal
While builing libtexttools on alpha:
gcc-4.1 -c -I./ -g -O2 -gnatafno -gnatVa -I.. -I-
/build/buildd/libtexttools-2.0.3/windows.adb
windows.adb:273:14: warning: "x" may be referenced before it has a value
windows.adb:273:17: warnin
Aurelien Jarno writes:
> Ludovic Brenta a écrit :
> > I'm baffled.
> >
> > gnat-4.1 has built on all archs except powerpc, where it says:
> >
> > Running configure in multilib subdir 64
> > pwd: /build/buildd/gnat-4.1-4.1.1/build/powerpc-linux-gnu
Ludovic Brenta a écrit :
I'm baffled.
gnat-4.1 has built on all archs except powerpc, where it says:
Running configure in multilib subdir 64
pwd: /build/buildd/gnat-4.1-4.1.1/build/powerpc-linux-gnu
configure: creating cache ./config.cache
checking whether to enable maintainer-spe
I'm baffled.
gnat-4.1 has built on all archs except powerpc, where it says:
Running configure in multilib subdir 64
pwd: /build/buildd/gnat-4.1-4.1.1/build/powerpc-linux-gnu
configure: creating cache ./config.cache
checking whether to enable maintainer-specific portions of Makefiles.
#
# bts-link upstream status pull for source package gnat-4.1
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user [EMAIL PROTECTED]
# remote status report for #388560
# * http://gcc.gnu.org/PR15305
# * remote status changed: (?) -> RESOLVED
# * remote resolut
#
# bts-link upstream status pull for source package gnat-4.1
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user [EMAIL PROTECTED]
# remote status report for #246384
# * http://gcc.gnu.org/PR15802
# * remote status changed: ASSIGNED -> RESOLVED
# * rem
Processing commands for [EMAIL PROTECTED]:
> reassign 58329 gnat-4.1
Bug#58329: gnat library compiled with bad path to sources
Bug reassigned from package `gnat' to `gnat-4.1'.
> reassign 170352 gnat-4.1
Bug#170352: gnat: No warning when uninitialised variables used in record
FYI: The status of the gnat-4.1 source package
in Debian's testing distribution has changed.
Previous version: (not in testing)
Current version: 4.1.1-10
--
This email is automatically generated; [EMAIL PROTECTED] is responsible.
See http://people.debian.org/~henning/trille/ for
Package: gnat-4.1
Severity: normal
Version: 4.1.1-9ada1
gcc-4.1 -c -O2 -gnatafno -gnatVa -g -I- -gnatA
/home/lbrenta/src/debian/libtemplates-parser-10.0+20060522/src/templates_parser.adb
+===GNAT BUG DETECTED==+
| 4.1.2 20060715 (prerelease
Matthias Klose wrote at 2006-06-17T22:48:26+0200:
> checked in the changelog entry, the patch was already committed.
I checked the web interface to the Subversion repository at
2006-06-18T14:49:00+0200. It indicates that, as of the last revision
(1295), neither the changelog entry nor the patch a
checked in the changelog entry, the patch was already committed.
Matthias
Ludovic Brenta writes:
> With this patch, the transition to gnat-4.1 as the default Ada
> compiler will be complete; I will start uploading packages that
> build-depend on gnat (>= 4.1) after both gcc-def
With this patch, the transition to gnat-4.1 as the default Ada
compiler will be complete; I will start uploading packages that
build-depend on gnat (>= 4.1) after both gcc-defaults (=1.37) and
gcc-4.1 (>= 4.1.1-6) are uploaded.
--
Ludovic Brenta.
[Ludovic Brenta]
* debian/cont
[Ludovic Brenta]
* Do not provide the symbolic link /usr/bin/gnatgcc; this will now
be provided by package gnat from the source package gcc-defaults.
--- rules.d/binary-ada.mk 05796b96bf16fc19f86b5a08a5bddf7d534a1c1e
+++ rules.d/binary-ada.mk d7afc76e0ca7744532f02056cf5d8e3ae5e
Xavier Grave <[EMAIL PROTECTED]> writes:
> Hi everybody,
>
> Since two days I have found how to compile gnat-4.1 under ppc
> architecture, but I struggle with the debian package building procedure.
> I don't find which files to modify in order to compile a few files
>
Hi everybody,
Since two days I have found how to compile gnat-4.1 under ppc
architecture, but I struggle with the debian package building procedure.
I don't find which files to modify in order to compile a few files
without optimisation option. In fact a-except.adb compilation crash the
s
Hi,
I will try to compile gnat-4.1 under a powerpc environment.
I have debootstraped an unstable debian + experimental sources.
I have already succedded in recompiling gnat gpl based on gcc-3.4 (asis,
aws and glade seem to run).
In the same environment, I will try to recompile gnat-4.1 with the
84 matches
Mail list logo
