public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mir Immad <mirimnan017@gmail.com>
To: Mohamed Atef <mohamedatef1698@gmail.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Compiling GCC source
Date: Mon, 7 Feb 2022 00:48:41 +0530	[thread overview]
Message-ID: <CAE1-7ozzW5+x-NO=m8mn3GJL7EN90Ck40QYgAC_sM-zTYYqN3w@mail.gmail.com> (raw)
In-Reply-To: <CAPFh8NLcWct4Q-SMon_h1atX-pxhSWJC1tnZzKo7CE+n_Y0Agw@mail.gmail.com>

The build system probably first tries to make sure if everything is in
place and if there were any changes and re-compiles the new/changed files.

How much time does it take when you try to rebuild?

On Mon, Feb 7, 2022, 12:43 AM Mohamed Atef <mohamedatef1698@gmail.com>
wrote:

> After i built it
> I tried make - j 8 and it's recompiling now i thought i will have messege
> like
> Every thing is up to date or there are no change done
> But it actually started to compile again
>
>
> في الأحد، ٦ فبراير، ٢٠٢٢ ٩:٠٨ م Mir Immad <mirimnan017@gmail.com> كتب:
>
>> Yes, that is right.
>>
>> On Mon, Feb 7, 2022, 12:38 AM Mohamed Atef <mohamedatef1698@gmail.com>
>> wrote:
>>
>>> Hello,
>>>       Only modified files will be recompiled, won't it?
>>>
>>>
>>> في الأحد، ٦ فبراير، ٢٠٢٢ ٩:٠٥ م Mir Immad <mirimnan017@gmail.com> كتب:
>>>
>>>> Make sure to use all the cores available.
>>>>
>>>> make -j N
>>>>
>>>> e.g; make -j 8
>>>>
>>>>
>>>> On Mon, Feb 7, 2022, 12:26 AM Mohamed Atef via Gcc <gcc@gcc.gnu.org>
>>>> wrote:
>>>>
>>>>> Hello everyone,
>>>>>         I built gcc from the repo and it took around 2 hours but I am
>>>>> wondering should I wait two hours after every modification?
>>>>> Is there any way to recompile faster.
>>>>> That's very important as we will add some files and tests  for OMPD.
>>>>> Thanks
>>>>>
>>>>

  reply	other threads:[~2022-02-06 19:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-06 18:55 Mohamed Atef
2022-02-06 19:05 ` Mir Immad
2022-02-06 19:07   ` Mohamed Atef
2022-02-06 19:08     ` Mir Immad
2022-02-06 19:13       ` Mohamed Atef
2022-02-06 19:18         ` Mir Immad [this message]
2022-02-06 19:28           ` Mohamed Atef
2022-02-07  9:20         ` Richard Biener
2022-02-06 21:22 ` Martin Jambor

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='CAE1-7ozzW5+x-NO=m8mn3GJL7EN90Ck40QYgAC_sM-zTYYqN3w@mail.gmail.com' \
    --to=mirimnan017@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=mohamedatef1698@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).