public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: sio / <siosios1@hotmail.com>
To: development@lists.ipfire.org
Subject: Re: The unshared changes give a problem with build after doing git pull on next
Date: Thu, 29 Aug 2024 00:07:55 +0000	[thread overview]
Message-ID: <172489007517.4187739.9056175785935150746@mail02.haj.ipfire.org> (raw)
In-Reply-To: <bf9c2036-82e5-4bc6-8c81-9d8024b6b216@ipfire.org>

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

I ran two separate builds on two different machines from scratch and they ran through the build process no problems that i could tell. I also added the netdata package to the mix on a second run on one of the machines and failed the build with the below error. mind you i have a 3rd machine with CU187 on it and it built the netdata package flawlessly, same files as I used on the CU188 machine so I am not sure if this is from the change or not. I have also gone into the shell with make.sh on the machine that had the error and could build netdata just fine with the same commands as in the lfs file. 

netdata build from shell:
--- We are done! --- 

  ^
  |.-.   .-.   .-.   .-.   .-.   .  netdata  .-.   .-.   .-.   .-.   .-.   .-
  |   '-'   '-'   '-'   '-'   '-'               '-'   '-'   '-'   '-'   '-'   
  +----+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----+--->

 --- is installed now! --- 
  enjoy real-time performance and health monitoring...

ipfire build chroot (x86_64) root:~/netdata-v1.47.0$
Ping from shell:
[root(a)cloud ipfire-2.x]# ./make.sh shell
Entering to a shell inside the build environment, go out with exit
ipfire build chroot (x86_64) root:~$ ping github.com
PING github.com (140.82.116.3) 56(84) bytes of data.
64 bytes from lb-140-82-116-3-sea.github.com (140.82.116.3): icmp_seq=1 ttl=52 time=110 ms
64 bytes from lb-140-82-116-3-sea.github.com (140.82.116.3): icmp_seq=2 ttl=52 time=89.0 ms
64 bytes from lb-140-82-116-3-sea.github.com (140.82.116.3): icmp_seq=3 ttl=52 time=112 ms
64 bytes from lb-140-82-116-3-sea.github.com (140.82.116.3): icmp_seq=4 ttl=52 time=109 ms
64 bytes from lb-140-82-116-3-sea.github.com (140.82.116.3): icmp_seq=5 ttl=52 time=102 ms
64 bytes from lb-140-82-116-3-sea.github.com (140.82.116.3): icmp_seq=6 ttl=52 time=101 ms
64 bytes from lb-140-82-116-3-sea.github.com (140.82.116.3): icmp_seq=7 ttl=52 time=110 ms
64 bytes from lb-140-82-116-3-sea.github.com (140.82.116.3): icmp_seq=8 ttl=52 time=106 ms

Error:

netdata (1.47.0)                                                                                                                                                                    [     1:36 ][ FAIL ]

    Could not resolve host: github.com
    
    shutting down connection #0
  
    --- LOG END ---
    error: downloading 'https://github.com/netdata/kernel-collector/releases/download/v1.4.5.1/netdata-kernel-collector-glibc-v1.4.5.1.tar.xz' failed
    status_code: 6
    status_string: "Could not resolve hostname"
    log:
    --- LOG BEGIN ---
    Could not resolve host: github.com
    
    shutting down connection #0

    --- LOG END ---

    ninja: build stopped: subcommand failed.
    FAILED  ''
    
    ABORTED  Failed to build Netdata.
    
    make: *** [netdata:86: /usr/src/log/netdata-v1.47.0] Error 1
    make: Leaving directory '/usr/src/lfs'

ERROR: Building netdata

  parent reply	other threads:[~2024-08-29  0:07 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cea14eb2-46f3-424b-8e54-aa9df10c78e3@ipfire.org>
2024-08-08 13:56 ` Fwd: " Matthias Fischer
2024-08-16 15:35 ` Michael Tremer
2024-08-16 16:43   ` Matthias Fischer
2024-08-21 14:28     ` Michael Tremer
2024-08-24  8:33       ` Matthias Fischer
2024-08-27 10:01         ` Michael Tremer
2024-08-27 12:55           ` Matthias Fischer
2024-08-27 18:03             ` / /
2024-08-28 15:46               ` Michael Tremer
2024-08-28 16:02                 ` / /
2024-08-28 16:30                 ` Matthias Fischer
2024-08-28 17:52                   ` Adolf Belka
2024-08-28 18:28                     ` Matthias Fischer
2024-08-28 19:10                       ` Adolf Belka
2024-08-28 19:13                         ` Adolf Belka
2024-08-29  7:46                         ` Michael Tremer
2024-08-29  0:07                       ` sio / [this message]
2024-08-29  7:58                         ` Michael Tremer
2024-08-29 12:00                           ` sio /
2024-08-29 12:17                             ` Michael Tremer
2024-08-29  7:41                       ` Michael Tremer
2024-08-29  7:41                     ` Michael Tremer
2024-08-29  7:39                   ` Michael Tremer
2024-08-30  8:56                     ` Matthias Fischer
     [not found] <184670fa-843f-4d5d-b4c9-1885a995fad8@ipfire.org>
2024-08-06 15:40 ` Michael Tremer
2024-08-08 12:09   ` Adolf Belka
2024-08-08 18:25     ` Adolf Belka
2024-08-08 18:31       ` Michael Tremer
     [not found] <9259926f-7276-450e-9a82-44b3c455f67e@ipfire.org>
2024-08-03  8:54 ` Michael Tremer
2024-08-03  9:39   ` Michael Tremer
     [not found] <2e6a45cb-7c55-4725-81f2-d69f0c7b373f@ipfire.org>
2024-08-02 18:13 ` Michael Tremer
2024-07-26  7:57 Adolf Belka
2024-07-26  8:17 ` Michael Tremer
2024-07-26  8:35   ` Adolf Belka
2024-07-26 12:39     ` Adolf Belka
2024-07-26 13:05       ` Michael Tremer
2024-07-26 14:08         ` Matthias Fischer
2024-07-26 14:18           ` Michael Tremer
2024-07-26 15:06             ` Matthias Fischer
2024-07-26 15:08               ` Michael Tremer
2024-08-02 17:50               ` Michael Tremer

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=172489007517.4187739.9056175785935150746@mail02.haj.ipfire.org \
    --to=siosios1@hotmail.com \
    --cc=development@lists.ipfire.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