| RE: [cdt-dev] GNU Tool-chain for Solaris |
|
I think it was because we had one variant
that couldn’t handle the space (macosx comes to mind). I actually think
we have more variants that need the space than can’t handle it. From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Treggiari, Leo I think that the
“generic” GNU compiler definition has never had a space after the
–o. I don’t know the reason. Leo From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of This issue has always bugged me. Do we
know/remember why we don’t have a space after the ‘-o’? From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Treggiari, Leo I have heard from a few people with a problem using
the built-in GNU tool-chain on Solaris because a space is required after the
–o output flag. Currently, they have to modify the tool-chain to
get it to work. Is there anyone using Solaris who has not had to modify
the tool-chain? I will create Solaris specific project types with a space
after the output flag if no one speaks up. What I don’t want to do
is make the change and then find that a different implementation of the GNU
tool-chain on Solaris requires that a space not be present. Thanks, Leo |