This is the mail archive of the mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: PR 26792

On 08/06/2006, at 7:48 AM, Jack Howarth wrote:

I noticed PR 26792 last night. After reading that it became clear what
was causing the massive c++ regressions when I built gcc trunk under fink.
Fink sets MACOSX_DEPLOYMENT_TARGET to 10.4 when a package is built in
fink 10.4 branch. They also were applying the rejected patch from...

to their gcc4 builds as well. That explains why the c++ regressions
suddenly appeared when I stopped applying their gcc4.patch (which
contains that and other changes for building on MacIntel).
    The good news is that when I build gcc trunk under fink with
MACOSX_DEPLOYMENT_TARGET unset, the massive c++ regressions now
disappear. The bad news is that the resulting gcc, when used to
build xplor-nih, still results in the c++ regression in the xplor-nih
testsuite which I reported several weeks ago. Did the information
I reported give you any hints as to where the problem might be?

Let me know if there is anything I can do to try to pin down
this remaining libgcc issue (which appears to be unrelated to
PR 26792).

I don't believe it's a libgcc issue. I think it's something that's happening at link (probably) or load time that just happens to involve libgcc. You may be encountering

<rdar://problem/4428696> a strong symbol in a dylib should not override a weak private extern symbol

or perhaps some not yet known problem.

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]