This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
ada/8941: Binding for non-Ada main uses flags in non-standard ways
- From: simon at pushface dot org
- To: gcc-gnats at gcc dot gnu dot org
- Date: 14 Dec 2002 17:00:05 -0000
- Subject: ada/8941: Binding for non-Ada main uses flags in non-standard ways
- Reply-to: simon at pushface dot org
>Number: 8941
>Category: ada
>Synopsis: Binding for non-Ada main uses flags in non-standard ways
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: unassigned
>State: open
>Class: change-request
>Submitter-Id: net
>Arrival-Date: Sat Dec 14 09:06:00 PST 2002
>Closed-Date:
>Last-Modified:
>Originator: Simon Wright
>Release: gcc version 3.2
>Organization:
>Environment:
Linux (Mandrake 8.2)
>Description:
When gnatbind creates b~main.adb, it uses -static or -shared in the Object file/option list with meanings different from gcc's meaning.
If you are using a non-Ada main, you need to extract the Object file/option list in order to know what to submit to the final link.
If you do this and leave the -static in, all following libraries must be available in lib.a form. If you leave -shared in, gcc tries to build a shared object.
>How-To-Repeat:
Too complicated to post.
>Fix:
(suggestion 1) Use -gnat-shared, -gnat-static so that extraction can detect this specific use.
(suggestion 2) Provide a special option to gnatlink/gnatbind which just outputs the processed Object file/option list.
>Release-Note:
>Audit-Trail:
>Unformatted: