From: Thomas Schwinge <thomas@codesourcery.com>
To: Yao Qi <yao@codesourcery.com>
Cc: <gdb-patches@sourceware.org>, <bug-hurd@gnu.org>
Subject: Re: [PATCH 3/3] Find and link with -lmachuser -lhurduser
Date: Sun, 16 Feb 2014 07:49:00 -0000 [thread overview]
Message-ID: <87a9drv6o6.fsf@kepler.schwinge.homeip.net> (raw)
In-Reply-To: <1391759958-972-4-git-send-email-yao@codesourcery.com>
[-- Attachment #1: Type: text/plain, Size: 1476 bytes --]
Hi!
On Fri, 7 Feb 2014 15:59:18 +0800, Yao Qi <yao@codesourcery.com> wrote:
> I see this link error when build native gdb for hurd.
>
> /home/yao/Software/hurd-toolchain/bin/../lib/gcc/i686-pc-gnu/4.8.0/../../../../i686-pc-gnu/bin/ld: gnu-nat.o: undefined reference to symbol 'mach_port_destroy'
> /home/yao/Software/hurd-toolchain/bin/../lib/gcc/i686-pc-gnu/4.8.0/../../../../i686-pc-gnu/bin/ld: note: 'mach_port_destroy' is defined in DSO
> /home/yao/Software/hurd-toolchain/bin/../i686-pc-gnu/libc/lib/libmachuser.so.1 so try adding it to the linker command line
> /home/yao/Software/hurd-toolchain/bin/../i686-pc-gnu/libc/lib/libmachuser.so.1:
> could not read symbols: Invalid operation
>
> This patch is to find and link GDB with -lmachuser and -lhurduser.
> * configure.ac: Invoke AC_SEARCH_LIBS to search libmachuser and
> libhurduser.
This should (currently) not be needed, for these two libraries are
(currently) considered to be part of libc.
(<http://www.gnu.org/software/hurd/open_issues/libmachuser_libhurduser_rpc_stubs.html>
and the thread starting at
<http://news.gmane.org/find-root.php?message_id=%3C20110329220143.GB5425%40const.famille.thibault.fr%3E>
have some discussion about this.)
Can you please post your toolchain's libc.so file (that is, the text file
of a few lines, not the binary libc.so.0.3). Am I assuming correctly
that this is a i686-pc-gnu toolchain that I once provided you with?
Grüße,
Thomas
[-- Attachment #2: Type: application/pgp-signature, Size: 489 bytes --]
next prev parent reply other threads:[~2014-02-16 7:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-07 8:01 [PATCH 0/3] Unbreak build on hurd Yao Qi
2014-02-07 8:01 ` [PATCH 3/3] Find and link with -lmachuser -lhurduser Yao Qi
2014-02-16 7:49 ` Thomas Schwinge [this message]
2014-02-17 2:17 ` Yao Qi
2014-02-25 5:10 ` Samuel Thibault
2014-02-07 8:01 ` [PATCH 2/3] Fix -Werror=pointer-sign warnings Yao Qi
2014-02-07 11:42 ` Joel Brobecker
2014-02-16 7:39 ` Thomas Schwinge
2014-02-17 3:32 ` Yao Qi
2014-02-07 8:01 ` [PATCH 1/3 OBV] Fix -Wformat warnings in gnu-nat.c Yao Qi
2014-02-16 7:38 ` Thomas Schwinge
2014-02-17 3:32 ` Yao Qi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a9drv6o6.fsf@kepler.schwinge.homeip.net \
--to=thomas@codesourcery.com \
--cc=bug-hurd@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=yao@codesourcery.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox