Summary: | [TRACKER] Ada reorganization tracker bug | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | George Shapovalov (RETIRED) <george> |
Component: | New packages | Assignee: | Gentoo Linux ADA team <ada> |
Status: | CONFIRMED --- | ||
Severity: | enhancement | CC: | esigra, fmdf66, jon, reznikmm, sylvchev, vgodunko |
Priority: | High | Keywords: | Tracker |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 133140, 158408, 167000, 111340, 136689, 151343 | ||
Bug Blocks: | 547358 |
Description
George Shapovalov (RETIRED)
2006-06-19 08:49:34 UTC
Hi George. I would like to know whether you have already decided on the issue that has been discussed in comments #96 and #97 from bug #111340 (which this bug depends on). Besides what is there discussed I would like you, please, to pay attention to another fact that has happened to me and that it speaks in favour to the adoption of the "keep the present profile active" (gcc-like behaviour). Before you provided the newest gnat-gpl-3.4.6 I had installed both gnat-gpl-3.4.5 and gnat-gcc-4.1 and set this latest compiler as the active one. My only reason behind installing gnat-gpl releases is just to check if they work and eventually reporting bugs, while I normally use the latest gnat-gcc for learning and production. Some weeks ago an unattended "emerge -vu world" installed the newest gnat-gpl-3.4.6 and set the active compiler to be that one. I forgot I still had the old gnat-gpl-3.4.5 in the production machine where I usually delete it after checking it succeeding in compiling a bunch of Ada libraries. The result is that I have been working with gnat-gpl-3.4.6 instead of gnat-gcc-4.1 for weeks until yesterday when I discovered that. Fortunatelly I also found out that the simple code I had sent to an italian magazine, that is publishing an article of mine on the Ada language with some illustrative programs, is able to compile with gnat-gcc-4.1 too as I had reported in the same article. fabio Hm, looks like I did not respond here, while I seem to remember that I did. Probably that was to that other bug. Actually yes, see comment #114 in bug #111340 :). Anyway - the issue is resolved now. George |