244607 - build failure:incorrect argument passed to Solaris ld when building with SunPro/Forte

Status: RESOLVED EXPIRED

(Firefox Build System :: General, defect)

Description

[grant beattie]

User-Agent:       Mozilla/5.0 (X11; U; NetBSD i386; en-US; rv:1.8a2) Gecko/20040523 Firefox/0.8.0+
Build Identifier: Mozilla/5.0 (X11; U; NetBSD i386; en-US; rv:1.8a2) Gecko/20040523 Firefox/0.8.0+

when using SunPro/Forte, DSO_LDOPTS contains "-Qoption ld" which isn't
recognised by the native Solaris linker. when calling the compiler to link,
"-Qoption ld" is functionally equivalent to "-Wl,", but it isn't necessary and
should not be used when calling the linker directly.

Reproducible: Always
Steps to Reproduce:
1. ./configure on Solaris with SunPro
2. gmake
3.

Comment 1

[grant beattie]

Attachment: patch to fix -Qoption breaking the build

Comment 2

[Olivier Cahagne]

It seems like this should work as per bug 235381 for e.g. The mozilla.org
nightlies are also compiled with Sun/Forte.
I'm not a Sun/Forte expert, can it come from an older version not supporting
this flag, what version do you use ?

Comment 3

[grant beattie]

it is Forte version 8 on Solaris 9 (the box is dead right now unfortunately). 

without having my logs available, I'm guessing that LD must be defaulting to
${CC} if not set in the environment, so when ${LD} is called, "-Qoption ld" is
accepted  . but in the case where LD=/usr/ccs/bin/ld, that is wrong.

Comment 4

[grant beattie]

-Qoption is specific to the C++ compiler:

http://docs.sun.com/source/817-0926/Comp_Options_App.html#pgfId-999197

Comment 5

[grant beattie]

(In reply to comment #3)
> without having my logs available, I'm guessing that LD must be defaulting to
> ${CC} if not set in the environment

of course I meant ${CXX}.

Comment 6

[Olivier Cahagne]

CC'ing the Sun expert :)

Comment 7

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 8

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.