Gentoo Archives: gentoo-user

From: Jude DaShiell <jdashiel@×××××.com>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] what test gets done in pcre makefile to find gcc won't work?
Date: Mon, 05 Oct 2020 17:51:51
Message-Id: alpine.NEB.2.23.451.2010051347530.4842@panix1.panix.com
In Reply to: Re: [gentoo-user] what test gets done in pcre makefile to find gcc won't work? by Ashley Dixon
1 Oops, correction the emerge offers where pcre broke happened after:
2 emerge --ask --verbose --update --deep --newuse @world
3 Would it have been best to refuse to do the emerges at that point in the
4 installation? The handbook was silent on that point except to say
5 updates could be done after installation.
6 The gcc compiler works this time though the pcre package continues to
7 break. I'll get the output for it and share with the list as soon as I
8 have it together.
9 On Sun, 4 Oct 2020, Ashley Dixon wrote:
10
11 > Date: Sun, 4 Oct 2020 02:59:18
12 > From: Ashley Dixon <ash@××××××××××.uk>
13 > Reply-To: gentoo-user@l.g.o
14 > To: gentoo-user@l.g.o
15 > Subject: Re: [gentoo-user] what test gets done in pcre makefile to find gcc
16 > won't work?
17 >
18 > On Sun, Oct 04, 2020 at 12:47:39AM -0400, Jude DaShiell wrote:
19 > > I ran emerge-webrsync and agreed to merge some software titles from
20 > > gentoo. The first one was pcre and so far as I can tell, all went fine
21 > > until the makefile tested gcc and found gcc doesn't work. At that point
22 > > the emerge errored out.
23 >
24 > I think you mean the configure script, not the Makefile? It is executed in the
25 > ebuild with the `econf` wrapper function [1, 2]; its output looks like this:
26 >
27 > checking for a BSD-compatible install... /usr/bin/install -c
28 > checking whether build environment is sane... yes
29 > checking for a thread-safe mkdir -p... /bin/mkdir -p
30 > [...]
31 >
32 > Can you post the full output of emerge? "The gcc test" is equivocal; the GNU
33 > configure script does lots of compiler tests, and it will be useful to know
34 > which one fails.
35 >
36 > > Now, it's possible everyone is using the systemd profile but I went with
37 > > the default profile already used for amd64 installs so it could be that
38 > > profile ran me into this particular error.
39 >
40 > I could be very mistaken, but I think that the majority of the Gentoo community
41 > uses an OpenRC profile, probably because it's the default. Gentoo supports quite
42 > a few init systems, if you'd like to have a play and see which one you like the
43 > most [3].
44 >
45 > > Something else that was strange, I had the gentoo-minimal cd in use and
46 > > had downloaded a stage3 file and a snapshot. The package
47 > > sys-libs/timezone-data did not download in those packages and the handbook
48 > > provided no instructions on downloading and installing that package before
49 > > trying to set the local time. Could it be failure to use systemd profile
50 > > also brought me this error as well?
51 >
52 > Which profile have you chosen? The Stage 3 tarball consists of a system set for
53 > a particular profile [4], all of which inherit the base @system [5]. The
54 > `timezone-data` package is not included in any of the default profile system
55 > sets, so it should not be expected to appear in a Stage 3:
56 >
57 > $ shopt -s globstar
58 > $ grep timezone-data gentoo/profiles/**/packages
59 > # or
60 > $ find gentoo/profiles/ -type f -name "packages" -exec grep \
61 > > timezone-data {} \;
62 >
63 > It should be pulled in a dependency of glibc, providing the `vanilla` flag isn't
64 > set, but you can just emerge it manually.
65 >
66 > $ equery d timezone-data # add `-a` after `d` for a full list
67 > * These packages depend on timezone-data:
68 > dev-libs/libical-3.0.8 (sys-libs/timezone-data)
69 > sys-libs/glibc-2.31-r6 (!vanilla ? sys-libs/timezone-data)
70 >
71 > Anyway, this is independent of the init system you choose. Have you had a look
72 > at [6]? Find the relevant file in `/usr/share/zoneinfo` which corresponds to
73 > your timezone, write its relative path to the `/etc/timezone` file, and
74 > reconfigure the `timezone-data` package. To steal the example in the handbook:
75 >
76 > $ ls -l /usr/share/zoneinfo
77 > $ echo "Europe/Brussels" > /etc/timezone # Suppose you're in Brussels
78 > $ emerge --config sys-libs/timezone-data # Regenerate `/etc/localtime`
79 >
80 > [1] https://gitweb.gentoo.org/repo/gentoo.git/tree/dev-libs/libpcre2/libpcre2-10.35.ebuild#n74
81 > [2] https://devmanual.gentoo.org/function-reference/build-functions/
82 > [3] https://wiki.gentoo.org/wiki/Comparison_of_init_systems
83 > [4] https://wiki.gentoo.org/wiki/Stage_tarball#Stage_3
84 > [5] https://gitweb.gentoo.org/repo/gentoo.git/tree/profiles/base/packages
85 > [6] https://wiki.gentoo.org/wiki/Handbook:AMD64/Full/Installation#Timezone
86 >
87 > P.S. You can examine the contents of `/etc/localtime`, and thus the supported
88 > timezones, with the `zdump` utility from the `timezone-data` package:
89 >
90 > $ zdump /etc/locatime
91 > /etc/localtime Sun Oct 4 07:41:45 2020 BST
92 >
93 >
94
95 --

Replies

Subject Author
Re: [gentoo-user] what test gets done in pcre makefile to find gcc won't work? Ashley Dixon <ash@××××××××××.uk>