Re: [Oorexx-devel] The nostartfiles option on unixes

[Mark M. <mie...@gm...>]

Thanks David.

I knew the option was to not include the start up files, I just wasn't
sure why we were using it.

I thought maybe it had to do with preventing the C++ memory management
from interfering with the interpreter's memory management.

--
Mark Miesfeld

On Wed, Aug 11, 2010 at 6:26 AM, David Ashley
<dav...@gm...> wrote:
>  This option refers to including the C library startup files (they are included
> by default, don't ask me why as this seems backwards to me). They are are needed
> when the library uses C library functions or certain other
> startup/initialization functions. Since we always invoke ooRexx library
> functions with the C library already initialized, including the object files
> again will cause duplicate references.
>
> David Ashley
>
> On 08/10/2010 05:25 PM, Mark Miesfeld wrote:
>> David, Rick,
>>
>> Why do we use the nostartfiles for linking in the unix build?
>>
>> I.e ORX_LDFLAGS_PACKAGE="-Xcomplier nostartfiles" in configure.ac
>> --
>> Mark Miesfeld
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by
>>
>> Make an app they can't live without
>> Enter the BlackBerry Developer Challenge
>> http://p.sf.net/sfu/RIM-dev2dev
>> _______________________________________________
>> Oorexx-devel mailing list
>> Oor...@li...
>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>>
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by
>
> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> http://p.sf.net/sfu/RIM-dev2dev
> _______________________________________________
> Oorexx-devel mailing list
> Oor...@li...
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>