public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Alexei Sholomitskiy <asholomitskiy84@gmail.com>
To: binutils@sourceware.org
Subject: a question from novice
Date: Wed, 21 Dec 2022 18:47:53 +0800	[thread overview]
Message-ID: <b6eb71fd-d7e7-d18b-491a-7b86262e7665@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1093 bytes --]

Hello!

I am a novice in Linux, so I'd like to understand, how it works

and I started compile projects, follow by linuxfromscratch recommendations

But I do it not in clear system, - on my Linux Mint

//---------------------------------------------------------------

to build binutils - is very simple ! (according to www.linuxfromscratch.org)

but there were so many errors and warnings ...

I don't understand, what is a reason I cannot build this project - 
according different sites, it is easy!


so I decided to compile binutils step-by-step - and not statically, but 
make shared libraries

I have wrote a bash script about 150 lines (initially it was up to 600!) 
to automatically download, extract, and *prepare for compiling* binutils 
tar.gz archive.


For next step I am to build gdb server and gcc compiler

and now I see directories libiberty, gold, libdecimal with the same 
names I saw in bunutils


Could you explain me, these projects have the same components?

why not to build binutils components as shared libraries and install 
them to /lib directory to use in future?

             reply	other threads:[~2022-12-21 10:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-21 10:47 Alexei Sholomitskiy [this message]
2022-12-21 11:18 ` Dmitry Mikushin

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=b6eb71fd-d7e7-d18b-491a-7b86262e7665@gmail.com \
    --to=asholomitskiy84@gmail.com \
    --cc=binutils@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).