topic Re: unresolved symbol in Operating System - HP-UX

unresolved symbol

Fred K. Abell Jr._1 — Mon, 15 Sep 2008 18:15:56 GMT

I am trying to compile eventlog-0.2.5 using a gcc compiler from the porting center in the UK. I had to make a few links to point to libs in gtk, but now I get the error:
"/usr/lib/dld.sl: Unresolved symbol: libintl_bindtextdomain (code) from gcc"

I rarely program, and am at a stand still with this error.

Thanks in advance.

Fred

Re: unresolved symbol

Tim Nelson — Mon, 15 Sep 2008 19:12:50 GMT

did you download and install "ALL" the co-requisites ??

Re: unresolved symbol

Dennis Handly — Mon, 15 Sep 2008 21:35:48 GMT

You use the following to search for the shlib:
nm -pxAN /path-to_shlibs/lib* | grep libintl_bindtextdomain

Re: unresolved symbol

Sandeep_Chaudhary — Tue, 16 Sep 2008 05:34:30 GMT

u have bto install "gettext" package.
Please see the thread:

http://forums12.itrc.hp.com/service/forums/questionanswer.do?admit=109447627+1221546579009+28353475&threadId=732097

Re: unresolved symbol

Fred K. Abell Jr._1 — Tue, 23 Sep 2008 17:14:05 GMT

Tim,

I did download and install all the co-requisites.

Dennis,

The response to nm -pxAN /path-to_shlibs/lib* | grep libintl_bindtextdomain
is "nm: /path-to_shlibs/lib*: cannot open"

Sandeep,

Gettext is installed with the gnome and gtk installs.

Re: unresolved symbol

Tim Nelson — Tue, 23 Sep 2008 17:39:11 GMT

I think Dennis wanted you to substitute "path-to_shlibs" with your path to your shared libs.

e.g.

nm -pxAN /usr/lib* | grep libintl_bindtextdomain/usr/lib
or
nm -pxAN /usr/local/lib/lib* | grep libintl_bindtextdomain

etc...

Re: unresolved symbol

Fred K. Abell Jr._1 — Tue, 23 Sep 2008 18:03:35 GMT

Sorry, this is my first third party software installation. And, the system crashed the other day and I had to rebuild.

Okay, I get the following:
# nm -pxAN /usr/lib* | grep libintl_bindtextdomain/usr/lib
nm: /usr/lib: bad magic
# nm -pxAN /usr/local/lib/lib* | grep libintl_bindtextdomain
nm: /usr/local/lib/libbfd.la: bad magic
nm: /usr/local/lib/libffi.la: bad magic
nm: /usr/local/lib/libgcj-tools.la: bad magic
nm: /usr/local/lib/libgcj.la: bad magic
nm: /usr/local/lib/libgcj.spec: bad magic
nm: /usr/local/lib/libgij.la: bad magic
nm: /usr/local/lib/libgomp.la: bad magic
nm: /usr/local/lib/libgomp.spec: bad magic
nm: /usr/local/lib/libopcodes.la: bad magic
nm: /usr/local/lib/libssp.la: bad magic
nm: /usr/local/lib/libssp_nonshared.la: bad magic
nm: /usr/local/lib/libstdc++.la: bad magic
nm: /usr/local/lib/libsupc++.la: bad magic

Lots of bad magic, whatever that is?

Re: unresolved symbol

Dennis Handly — Thu, 25 Sep 2008 05:09:21 GMT

>Tim: I think Dennis wanted you to substitute "path-to_shlibs"

Yes.

># nm -pxAN /usr/lib* | grep libintl_bindtextdomain/usr/lib
nm: /usr/lib: bad magic

Tim's typo. This should be:
nm -pxAN /usr/lib/lib* usr/local/lib/lib* | grep libintl_bindtextdomain

>Lots of bad magic, whatever that is?

Basically these are non-library files that just happen to be in these directories.

But most importantly nm didn't find libintl_bindtextdomain.

If you want to be pedantic you could also use:
odump -slexport /usr/lib/lib* | grep libintl_bindtextdomain

Re: unresolved symbol

Fred K. Abell Jr._1 — Fri, 26 Sep 2008 13:23:01 GMT

OK, I have never used nm nor odump. But I do like being pedantic! I appreciate your efforts to help me. The results are:

# nm -pxAN /usr/lib/lib* usr/local/lib/lib* | grep libintl_bindtextdomain
nm: /usr/lib/lib.b: bad magic
nm: /usr/lib/libAt.sl: cannot open
nm: /usr/lib/libdd98704.a: cannot open
nm: /usr/lib/libdd98704.sl: cannot open
nm: /usr/lib/libdd98705.a: cannot open
nm: /usr/lib/libdd98705.sl: cannot open
nm: /usr/lib/libdd98735.a: cannot open
nm: /usr/lib/libdd98735.sl: cannot open
nm: /usr/lib/libdd98736.a: cannot open
nm: /usr/lib/libdd98736.sl: cannot open
nm: /usr/lib/libdd98765.a: cannot open
nm: /usr/lib/libdd98765.sl: cannot open
nm: /usr/lib/libdd98766.a: cannot open
nm: /usr/lib/libdd98766.sl: cannot open
nm: /usr/lib/libddcrx48z.a: cannot open
nm: /usr/lib/libddcrx48z.sl: cannot open
nm: /usr/lib/libddgcrx.a: cannot open
nm: /usr/lib/libddgcrx.sl: cannot open
nm: /usr/lib/libddhpterm.a: cannot open
nm: /usr/lib/libddhpterm.sl: cannot open
nm: /usr/lib/libddkbd.a: cannot open
nm: /usr/lib/libddkbd.sl: cannot open
nm: /usr/lib/libddlkbd.a: cannot open
nm: /usr/lib/libddlkbd.sl: cannot open
nm: /usr/lib/libddsbv.a: cannot open
nm: /usr/lib/libddsbv.sl: cannot open
nm: /usr/lib/libil.sl: cannot open
nm: /usr/lib/libilefs.sl: cannot open
nm: /usr/lib/libp: cannot open
nm: usr/local/lib/lib*: cannot open

# odump -slexport /usr/lib/lib* | grep libintl_bindtextdomain
odump: Error: Cannot open '/usr/lib/libAt.sl'

Re: unresolved symbol

Dennis Handly — Sat, 27 Sep 2008 02:49:58 GMT

>The results are:

Basically it didn't find that symbol in any lib in those directories.

Re: unresolved symbol

Fred K. Abell Jr._1 — Fri, 17 Oct 2008 14:23:36 GMT

I just did what I needed on Centos, thanks for all the help anyways.

Re: unresolved symbol

Fred K. Abell Jr._1 — Wed, 12 Nov 2008 20:42:30 GMT

All,

I thought gettext was installed. I did the gettext command and it asked for inputs. I did a man on gettext and I got a man page. I then installed the gettext depot and it did not give me an error already installed, so now I ran the configure script again and YIKES, it worked! Thanks again to all.

Re: unresolved symbol

Fred K. Abell Jr._1 — Wed, 12 Nov 2008 20:44:06 GMT

see last post