This is the mail archive of the egcs@egcs.cygnus.com mailing list for the EGCS project. See the EGCS home page for more information.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
On Fri, Mar 26, 1999 at 11:20:46PM -0700, Jeffrey A Law scribbled:
>
> In message <19990326181438.A28074@cheops.net.csuchico.edu>you write:
> > I'm getting an unresolved symbol when I try to dynamicly link a Perl
> > module. Now before you say anything, the symbol is __udivdi3. This symbol
> > is why I'm asking here, as it exists because of egcs.
> Hmmm. The question then becomes how was the library built. __udivdi3 is
> a function found in libgcc.a.
>
Yup, that's why I asked here.
> When you build a shared library routines like __udivdi3 from libgcc.a should
> have been copied into the library.
>
> > /usr/lib/dld.sl: Unresolved symbol: __udivdi3 (code) from /usr/local/mysql
> > /lib/mysql/libmysqlclient.sl.6
> So. Find out how libmysqlclient.sl.6 was built. I'd bet it was built by
> calling ld directly instead of using gcc -shared -fPIC <blah blah blah>
>
The library was linked using ld. I went and rebuilt it using gcc and it
was happy. Thanks to all for your suggestions.
Chris...
--
What's the point?
An NT server can be run by an idiot, and usually is.
PGP fingerprint: 063FCE320681C336 78C164FC9B2F91EA