public inbox for libc-help@sourceware.org
 help / color / mirror / Atom feed
From: Vincent Fortier <th0ma7@gmail.com>
To: libc-help@sourceware.org
Subject: tools only installation?
Date: Sun, 30 Jul 2023 07:58:26 -0400	[thread overview]
Message-ID: <CALAySuL4qcDLG8uQMnzO+F9AofLWXo97gNkgMpFRBL2+Kh4cgw@mail.gmail.com> (raw)

Hi,

Currently maintaining a SynoCommunity development package with a set
of various tools including compilers.  One thing I'd really much like
to add is ldd, as everything being cross-compiled, having a native ldd
would be helpful to check shared libraries relationships directly from
its installed destination.

So I've been playing with glibc to cross-compile it, which now works.
Although I now have two remaining issues:
1. I can't find a way to install only the set of glibc tools, without
the entire library or any include files?  Focus being in particular to
ldd.
2. Presumably in lack of a solution for item 1, when invoking glibc
build after my other set of tools already built in planning to
generate a resulting package, glibc ends-up colliding with the already
installed gmp.h include file, coming from binutils who required gmp as
dependency.  I'm presuming I should not build glibc first as
everything else will be bound to that newer version of glibc instead
of the one provided by the Synology toolchain.

github PR: https://github.com/SynoCommunity/spksrc/pull/5824

Help or pointers would be really much appreciated.

Thnx in advance.

Vincent Fortier

             reply	other threads:[~2023-07-30 11:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-30 11:58 Vincent Fortier [this message]
2023-08-01 20:52 ` Adhemerval Zanella Netto

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=CALAySuL4qcDLG8uQMnzO+F9AofLWXo97gNkgMpFRBL2+Kh4cgw@mail.gmail.com \
    --to=th0ma7@gmail.com \
    --cc=libc-help@sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).