From: Yao Qi <yao@codesourcery.com>
To: Thomas Schwinge <thomas@codesourcery.com>
Cc: <gdb-patches@sourceware.org>, <bug-hurd@gnu.org>
Subject: Re: [PATCH 3/3] Find and link with -lmachuser -lhurduser
Date: Mon, 17 Feb 2014 02:17:00 -0000 [thread overview]
Message-ID: <530170C7.9020803@codesourcery.com> (raw)
In-Reply-To: <87a9drv6o6.fsf@kepler.schwinge.homeip.net>
On 02/16/2014 03:49 PM, Thomas Schwinge wrote:
> 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.)
That is to say, this problem doesn't exist with toolchain using recent
libc. However, this link error still exists when an old toolchain is
used and it sounds unfeasible to upgrade libc to fix the link error.
Link -lmachuser and -lhurduser explicitly, as a fallback, is no harm.
I don't have a strong opinion on this patch.
>
> 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
/* GNU ld script
Use the shared library, but some functions are only in
the static library, so try that secondarily. */
OUTPUT_FORMAT(elf32-i386)
GROUP ( /lib/libc.so.0.3 /usr/lib/libcrt_nonshared.a AS_NEEDED (
/lib/ld.so.1 ) )
> that this is a i686-pc-gnu toolchain that I once provided you with?
Yes.
--
Yao (é½å°§)
next prev parent reply other threads:[~2014-02-17 2:17 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
2014-02-17 2:17 ` Yao Qi [this message]
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=530170C7.9020803@codesourcery.com \
--to=yao@codesourcery.com \
--cc=bug-hurd@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=thomas@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