ada/8941: Binding for non-Ada main uses flags in non-standard ways

ada/8941: Binding for non-Ada main uses flags in non-standard ways

[simon]

>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:

Re: ada/8941: Binding for non-Ada main uses flags in non-standard ways

[bosch]

Synopsis: Binding for non-Ada main uses flags in non-standard ways

State-Changed-From-To: open->closed
State-Changed-By: bosch
State-Changed-When: Sat Dec 14 12:37:13 2002
State-Changed-Why:
    The -O option outputs the processed list of object files required in the link. This mostly implements suggestion 2. Value of other Linker_Options specified in Ada sources is questionable for non-Ada main program anyway.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8941