www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From aa...@apache.org
Subject Re: build/10038: apache can't start
Date Tue, 05 Mar 2002 15:45:32 GMT
[In order for any reply to be added to the PR database, you need]
[to include <apbugs@Apache.Org> in the Cc line and make sure the]
[subject line starts with the report component and number, with ]
[or without any 'Re:' prefixes (such as "general/1098:" or      ]
["Re: general/1098:").  If the subject doesn't match this       ]
[pattern, your message will be misfiled and ignored.  The       ]
["apbugs" address is not added to the Cc line of messages from  ]
[the database automatically because of the potential for mail   ]
[loops.  If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request from a  ]
[developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]


Synopsis: apache can't start

State-Changed-From-To: open-closed
State-Changed-By: aaron
State-Changed-When: Tue Mar  5 07:45:31 PST 2002
State-Changed-Why:
This is a common error caused by the interaction of
an improperly compiled gcc 2.95.x and its implicit use of
the Solaris linker (ld).

There are a few possible solutions to this:
1) Rebuild gcc to use the gnu assembler from the gnu utils package.
2) Rebuild gcc to pass the proper implicit paths to the Solaris linker, specifically the path
to libgcc.a
3) (Quick Workaround) Simply add the following output to your LDFLAGS variable before running
configure:
`gcc -print-libgcc-file-name`

Details:
The gcc compiler is introducing symbols into compiled object files that are only available
in libgcc.a, but
does not explicitly identify this library to the underlying linker. Unless gcc was explicitly
built with
this implicit pathname, this error will occur.


Mime
View raw message