Netfab,
On Friday, 2023-04-21 19:41:54 +0200, you wrote:
> ...
> You should open a bug to explain that ARCH variable is already defined
> in your shell environment. As a consequence the results on the following
> commands are different :
Hm, I'm not at all sure this would qualify as a bug. A
Le 21/04/23 à 18:26, Dr Rainer Woitok a tapoté :
> Skimming farther upward reveals the string "x86_64" being derived
> in line "33:" from environment variable "ARCH" which is defined
> in my shell initialization scripts:
>
>export ARCH=$({ arch || uname -m || echo unknown ; } 2>
Netfab,
On Friday, 2023-04-21 14:43:32 +0200, you wrote:
> ...
> I do not see anything particular in your emerge --info.
> What is your eselect version ?
> > $ eselect --version
$ eselect --version
eselect 1.4.20
Copyright (c) 2005-2020 Gentoo Authors.
Distributed under the terms
Le 20/04/23 à 17:41, Dr Rainer Woitok a tapoté :
> Netfab,
>
> On Tuesday, 2023-04-18 19:23:08 +0200, you wrote:
>
> > ...
> > Please post your emerge --info.
>
> $ emerge --info
I do not see anything particular in your emerge --info.
What is your eselect version ?
> $ eselect --version
You
Netfab,
On Tuesday, 2023-04-18 19:23:08 +0200, you wrote:
> ...
> Please post your emerge --info.
$ emerge --info
Portage 3.0.44 (python 3.10.10-final-0, default/linux/amd64/17.1/desktop,
gcc-12, glibc-2.36-r7, 6.1.19-gentoo x86_64)
Le 18/04/23 à 17:25, Dr Rainer Woitok a tapoté :
> On Monday, 2023-04-17 13:49:57 +0200, you wrote:
>
> > ...
> > Is the following file readable ?
> >
> > > $ ls -l $(portageq get_repo_path / gentoo)/profiles/profiles.desc
>
> Yes:
>
> [...]
Please post your emerge --info.
Netfab,
On Monday, 2023-04-17 13:49:57 +0200, you wrote:
> ...
> Is the following file readable ?
>
> > $ ls -l $(portageq get_repo_path / gentoo)/profiles/profiles.desc
Yes:
$ ls -l $(portageq get_repo_path / gentoo)/profiles/profiles.desc
-rw-r--r-- 1 root root 20443 2023-03-24 15:05
On Sun, Apr 16, 2023 at 06:56:35PM -0400, Walter Dnes wrote
>
> ***I CAN'T EVEN BUILD THE CURRENT GLIBC ON MY MACHINE***. It looks
> more and more like somewhere somehow my profile selection got changed
> after my previous glibc update.
>
> I regularly back up incrementally to two large
Le 17/04/23 à 12:06, Dr Rainer Woitok a tapoté :
> Walter's problems triggered me to check what profile was selected on
> my own rig:
>
># eselect profile show
>Current /etc/portage/make.profile symlink:
> default/linux/amd64/17.1/desktop
># eselect profile list
>!!! Error:
Greetings,
On Sunday, 2023-04-16 18:56:35 -0400, Walter Dnes wrote:
> On Sun, Apr 16, 2023 at 01:29:46AM -0400, Walter Dnes wrote
> > When I installed Gentoo on my desktop PC, I could've sworn that I
> > selected...
> >
> > [15] default/linux/amd64/17.1/no-multilib (stable)
> >
> > ...as
On Sun, Apr 16, 2023 at 01:29:46AM -0400, Walter Dnes wrote
> When I installed Gentoo on my desktop PC, I could've sworn that I
> selected...
>
> [15] default/linux/amd64/17.1/no-multilib (stable)
>
> ...as the profile. ***THINGS HAVE BEEN WORKING FINE FOR A COUPLE OF
> YEARS.***
Things
When I installed Gentoo on my desktop PC, I could've sworn that I
selected...
[15] default/linux/amd64/17.1/no-multilib (stable)
...as the profile. ***THINGS HAVE BEEN WORKING FINE FOR A COUPLE OF
YEARS.***
While updating tonight, glibc dies with a build error...
.[31;01m*.[0m ERROR:
12 matches
Mail list logo
