pamac broke, yay broke, uninstalled both, can't reinstall either.

rek · 2024-09-16 10:27:28

seems like i have something fundamentally broken in the build system, pacman, or something else.

All this started when nothing would install anymore using Pamac. (I use Pamac to find apps)
I had to use yay to uninstall Pamac, and tried to reinstall. Yay failed. So I uninstalled Yay.
Trying to reinstall Yay gave me the following error:

(base) [username@thing ~]$ git clone https://aur.archlinux.org/yay.git
(base) [username@thing ~]$ cd yay
(base) [username@thing yay]$ makepkg -si
==> Making package: yay 12.3.5-2 (Mon 16 Sep 2024 12:10:48 PM CEST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found yay-12.3.5.tar.gz
==> Validating source files with sha256sums...
    yay-12.3.5.tar.gz ... Passed
==> Extracting sources...
  -> Extracting yay-12.3.5.tar.gz with bsdtar
==> Removing existing $pkgdir/ directory...
==> Starting build()...
go build -trimpath -mod=readonly -modcacherw -ldflags '-X "main.yayVersion=12.3.5" -X "main.localePath=/usr/share/locale/" -linkmode=external -compressdwarf=false' -buildmode=pie -o yay
# runtime/cgo
<command-line>: error: "_FORTIFY_SOURCE" redefined [-Werror]
<command-line>: note: this is the location of the previous definition
cc1: all warnings being treated as errors
make: *** [Makefile:114: yay] Error 1
==> ERROR: A failure occurred in build().
    Aborting...

I've never had any problems with the "_FORTIFY_SOURCE" before.

trying to build pamac from source using git, etc results in the following:

(base) [username@thing yay]$ git clone https://aur.archlinux.org/archlinux-appstream-data-pamac.git
Cloning into 'archlinux-appstream-data-pamac'...
hint: Using 'master' as the name for the initial branch. This default branch name
hint: is subject to change. To configure the initial branch name to use in all
hint: of your new repositories, which will suppress this warning, call:
hint:
hint: 	git config --global init.defaultBranch <name>
hint:
hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
hint: 'development'. The just-created branch can be renamed via this command:
hint:
hint: 	git branch -m <name>
remote: Enumerating objects: 123, done.
remote: Counting objects: 100% (123/123), done.
remote: Compressing objects: 100% (74/74), done.
remote: Total 123 (delta 48), reused 123 (delta 48), pack-reused 0 (from 0)
Receiving objects: 100% (123/123), 54.75 KiB | 2.03 MiB/s, done.
Resolving deltas: 100% (48/48), done.
(base) [username@thing yay]$ cd archlinux-appstream-data-pamac
(base) [username@thing archlinux-appstream-data-pamac]$ makepkg -si
==> Making package: archlinux-appstream-data-pamac 1:20230421-1 (Mon 16 Sep 2024 12:15:09 PM CEST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Downloading core-20230421.xml.gz...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
curl: (22) The requested URL returned error: 404
==> ERROR: Failure while downloading https://sources.archlinux.org/other/packages/archlinux-appstream-data/20230421/core/Components-x86_64.xml.gz
    Aborting...

I guess that is an old url, I don't know. Anyway, nothing seems to want to install or Make on my system right at the moment
regardless of whether it's pacman, pamac or yay.

gromit · 2024-09-16 10:57:20

Could you post your "/etc/makepkg.conf"?

WorMzy · 2024-09-16 10:59:03

Mod note: Moving to AUR Issues.

Awebb · 2024-09-16 11:11:49

In addition: There is an /etc/makepkg.conf and a ~/.makepkg.conf. The one in your home folder has precedence, if it exists.

Also check whether there is a .pacnew makepkg.conf that needs merging.

rek · 2024-09-16 11:14:27

gromit wrote:

Could you post your "/etc/makepkg.conf"?

(base) [username@thing ~]$ cat /etc/makepkg.conf
#!/hint/bash
# shellcheck disable=2034

#
# /etc/makepkg.conf
#

#########################################################################
# SOURCE ACQUISITION
#########################################################################
#
#-- The download utilities that makepkg should use to acquire sources
#  Format: 'protocol::agent'
DLAGENTS=('file::/usr/bin/curl -qgC - -o %o %u'
          'ftp::/usr/bin/curl -qgfC - --ftp-pasv --retry 3 --retry-delay 3 -o %o %u'
          'http::/usr/bin/curl -qgb "" -fLC - --retry 3 --retry-delay 3 -o %o %u'
          'https::/usr/bin/curl -qgb "" -fLC - --retry 3 --retry-delay 3 -o %o %u'
          'rsync::/usr/bin/rsync --no-motd -z %u %o'
          'scp::/usr/bin/scp -C %u %o')

# Other common tools:
# /usr/bin/snarf
# /usr/bin/lftpget -c
# /usr/bin/wget

#-- The package required by makepkg to download VCS sources
#  Format: 'protocol::package'
VCSCLIENTS=('bzr::breezy'
            'fossil::fossil'
            'git::git'
            'hg::mercurial'
            'svn::subversion')

#########################################################################
# ARCHITECTURE, COMPILE FLAGS
#########################################################################
#
CARCH="x86_64"
CHOST="x86_64-pc-linux-gnu"

#-- Compiler and Linker Flags
#CPPFLAGS=""
CFLAGS="-march=x86-64 -mtune=generic -O2 -pipe -fno-plt -fexceptions \
        -Wp,-D_FORTIFY_SOURCE=3 -Wformat -Werror=format-security \
        -fstack-clash-protection -fcf-protection \
        -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer"
CXXFLAGS="$CFLAGS -Wp,-D_GLIBCXX_ASSERTIONS"
LDFLAGS="-Wl,-O1 -Wl,--sort-common -Wl,--as-needed -Wl,-z,relro -Wl,-z,now \
         -Wl,-z,pack-relative-relocs"
LTOFLAGS="-flto=auto"
#-- Make Flags: change this for DistCC/SMP systems
#MAKEFLAGS="-j2"
#-- Debugging flags
DEBUG_CFLAGS="-g"
DEBUG_CXXFLAGS="$DEBUG_CFLAGS"

#########################################################################
# BUILD ENVIRONMENT
#########################################################################
#
# Makepkg defaults: BUILDENV=(!distcc !color !ccache check !sign)
#  A negated environment option will do the opposite of the comments below.
#
#-- distcc:   Use the Distributed C/C++/ObjC compiler
#-- color:    Colorize output messages
#-- ccache:   Use ccache to cache compilation
#-- check:    Run the check() function if present in the PKGBUILD
#-- sign:     Generate PGP signature file
#
BUILDENV=(!distcc color !ccache check !sign)
#
#-- If using DistCC, your MAKEFLAGS will also need modification. In addition,
#-- specify a space-delimited list of hosts running in the DistCC cluster.
#DISTCC_HOSTS=""
#
#-- Specify a directory for package building.
#BUILDDIR=/tmp/makepkg

#########################################################################
# GLOBAL PACKAGE OPTIONS
#   These are default values for the options=() settings
#########################################################################
#
# Makepkg defaults: OPTIONS=(!strip docs libtool staticlibs emptydirs !zipman !purge !debug !lto !autodeps)
#  A negated option will do the opposite of the comments below.
#
#-- strip:      Strip symbols from binaries/libraries
#-- docs:       Save doc directories specified by DOC_DIRS
#-- libtool:    Leave libtool (.la) files in packages
#-- staticlibs: Leave static library (.a) files in packages
#-- emptydirs:  Leave empty directories in packages
#-- zipman:     Compress manual (man and info) pages in MAN_DIRS with gzip
#-- purge:      Remove files specified by PURGE_TARGETS
#-- debug:      Add debugging flags as specified in DEBUG_* variables
#-- lto:        Add compile flags for building with link time optimization
#-- autodeps:   Automatically add depends/provides
#
OPTIONS=(strip docs !libtool !staticlibs emptydirs zipman purge debug lto)

#-- File integrity checks to use. Valid: md5, sha1, sha224, sha256, sha384, sha512, b2
INTEGRITY_CHECK=(sha256)
#-- Options to be used when stripping binaries. See `man strip' for details.
STRIP_BINARIES="--strip-all"
#-- Options to be used when stripping shared libraries. See `man strip' for details.
STRIP_SHARED="--strip-unneeded"
#-- Options to be used when stripping static libraries. See `man strip' for details.
STRIP_STATIC="--strip-debug"
#-- Manual (man and info) directories to compress (if zipman is specified)
MAN_DIRS=({usr{,/local}{,/share},opt/*}/{man,info})
#-- Doc directories to remove (if !docs is specified)
DOC_DIRS=(usr/{,local/}{,share/}{doc,gtk-doc} opt/*/{doc,gtk-doc})
#-- Files to be removed from all packages (if purge is specified)
PURGE_TARGETS=(usr/{,share}/info/dir .packlist *.pod)
#-- Directory to store source code in for debug packages
DBGSRCDIR="/usr/src/debug"
#-- Prefix and directories for library autodeps
LIB_DIRS=('lib:usr/lib' 'lib32:usr/lib32')

#########################################################################
# PACKAGE OUTPUT
#########################################################################
#
# Default: put built package and cached source in build directory
#
#-- Destination: specify a fixed directory where all packages will be placed
#PKGDEST=/home/packages
#-- Source cache: specify a fixed directory where source files will be cached
#SRCDEST=/home/sources
#-- Source packages: specify a fixed directory where all src packages will be placed
#SRCPKGDEST=/home/srcpackages
#-- Log files: specify a fixed directory where all log files will be placed
#LOGDEST=/home/makepkglogs
#-- Packager: name/email of the person or organization building packages
#PACKAGER="John Doe <john@doe.com>"
#-- Specify a key to use for package signing
#GPGKEY=""

#########################################################################
# COMPRESSION DEFAULTS
#########################################################################
#
COMPRESSGZ=(gzip -c -f -n)
COMPRESSBZ2=(bzip2 -c -f)
COMPRESSXZ=(xz -c -z -)
COMPRESSZST=(zstd -c -T0 -)
COMPRESSLRZ=(lrzip -q)
COMPRESSLZO=(lzop -q)
COMPRESSZ=(compress -c -f)
COMPRESSLZ4=(lz4 -q)
COMPRESSLZ=(lzip -c -f)

#########################################################################
# EXTENSION DEFAULTS
#########################################################################
#
PKGEXT='.pkg.tar.zst'
SRCEXT='.src.tar.gz'

#########################################################################
# OTHER
#########################################################################
#
#-- Command used to run pacman as root, instead of trying sudo and su
#PACMAN_AUTH=()
# vim: set ft=sh ts=2 sw=2 et:

Awebb wrote:

In addition: There is an /etc/makepkg.conf and a ~/.makepkg.conf. The one in your home folder has precedence, if it exists.
Also check whether there is a .pacnew makepkg.conf that needs merging.

I seem to have a /etc/pacman.conf.pacnew and a /etc/pamac.conf.pacsave
(i've uninstalled pamac)

edit: I just used pacman to install e3 and that worked, so it doesn't seem to be a pacman issue.

Last edited by rek (2024-09-16 15:47:02)

seth · 2024-09-16 16:24:08

Try to

export VERBOSE=1

or set the makeflags to "-v" to hopefully get more ouptut.
You're defining the variable twice, possibly the cflags are doubled by the make instructions.

rek · 2024-09-16 17:13:22

seth wrote:

Try to
export VERBOSE=1
or set the makeflags to "-v" to hopefully get more ouptut.
You're defining the variable twice, possibly the cflags are doubled by the make instructions.

thanks for the reply

where should i use that flag? i tried

(base) [username@thing yay]$ makepkg -v -si
makepkg: invalid option -- 'v'

and

(base) [username@thing yay]$ makepkg -si -v
makepkg: invalid option -- 'v'

before all this, i used nano to edit /etc/pacman.conf to comment out an ignorepkg that was set for wine.

not sure if there's any connection, but could that have something to do with it?

Last edited by rek (2024-09-16 17:14:14)

seth · 2024-09-16 17:20:57

/etc/makepkg.conf, MAKEFLAGS - or just globally export VERBOSE=1 and hope that makepkg picks it up.

rek · 2024-09-16 19:33:13

seth wrote:

/etc/makepkg.conf, MAKEFLAGS - or just globally export VERBOSE=1 and hope that makepkg picks it up.

I uncommented the MAKEFLAGS and gave it -v, and it finished the install.
that seemed to work, but I think all it did was build it, because when i do the makepkg -si (which should install it)

this happens:

(base) [username@thing ~]$ yay --version
bash: yay: command not found

I tried running makepkg -si again, all it did was 'reinstall'

(base) [username@thing yay]$ makepkg -si
==> WARNING: A package has already been built, installing existing package...
==> Installing package yay with pacman -U...
[sudo] password for username: 
loading packages...
warning: yay-12.3.5-2 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Package (1)  Old Version  New Version  Net Change

yay          12.3.5-2     12.3.5-2       0.00 MiB


:: Proceed with installation? [Y/n] y
(1/1) checking keys in keyring                     [######################] 100%
(1/1) checking package integrity                   [######################] 100%
(1/1) loading package files                        [######################] 100%
(1/1) checking for file conflicts                  [######################] 100%
(1/1) checking available disk space                [######################] 100%
:: Processing package changes...
(1/1) reinstalling yay                             [######################] 100%

afaik, shell should know what yay is. shouldn't need to reboot. i closed terminal and opened a new one. still yay agnostic.

i've never had to edit MAKEFLAGS before. feels like something fundamental must have gone wrong in my system.

Last edited by rek (2024-09-16 19:41:17)

V1del · 2024-09-16 20:27:53

Use

makepkg -Csi

to force an actual rebuild, the VERBOSE in the makeflags should make the follow up output you get while doing a build more verbose and you might want to post it.

johnspack · 2024-09-16 20:29:24

I just went through this myself yesterday. In the end I needed to delete the yay build folder, then empty trash. It was actually using the contents in trash. Then git clone yay and rebuild it. Also make sure to pacman -Syu first and make sure you're updated to pacman 7.
Then you should be able to reinstall pamac. Not sure if this helps you or not....

rek · 2024-09-16 21:07:24

V1del wrote:

Use
makepkg -Csi
to force an actual rebuild, the VERBOSE in the makeflags should make the follow up output you get while doing a build more verbose and you might want to post it.

do i just write a line in makepkg.conf that says:

VERBOSE=1

?

I tried using makepkg -Csi and nothing changed, yay is still not recognized in terminal.

johnspack wrote:

I just went through this myself yesterday. In the end I needed to delete the yay build folder, then empty trash. It was actually using the contents in trash. Then git clone yay and rebuild it. Also make sure to pacman -Syu first and make sure you're updated to pacman 7.
Then you should be able to reinstall pamac. Not sure if this helps you or not....

I need to learn what Trash is, I use shift delete for everything. I just tried

makepkg -code

that some other thread recommended, then re-installed yay, still yay isn't showing up in terminal.
(just checked ~/.local/share/Trash and there's nothing in it.)

(base) [username@thing yay]$ pacman --version

 .--.                  Pacman v7.0.0 - libalpm v15.0.0
/ _.-' .-.  .-.  .-.   Copyright (C) 2006-2024 Pacman Development Team
\  '-. '-'  '-'  '-'   Copyright (C) 2002-2006 Judd Vinet
 '--'
                       This program may be freely redistributed under
                       the terms of the GNU General Public License.

using pacman, targets aren't found for yay, pamac, or pamac-aur, and I didn't expect them to be since yay is the way I did it the first time I think. but all this started when pamac wouldn't install anything anymore. I'm missing something really key.

Last edited by rek (2024-09-16 21:14:13)

V1del · 2024-09-16 21:11:02

pacman -Qkk yay pamac
type -a yay
echo $PATH

as for the verbose, the simplest way would be just to do

VERBOSE=1 makepkg -Csi

for example

Last edited by V1del (2024-09-16 21:12:36)

seth · 2024-09-16 21:11:47

do i just write a line in makepkg.conf that says:

No.
https://wiki.archlinux.org/title/Environment_Variables
"man export"

I just tried

Would you please not type random stuff you don't understand into the terminal?

rek · 2024-09-16 21:35:00

V1del wrote:

pacman -Qkk yay pamac
type -a yay
echo $PATH

(base) [username@thing yay]$ pacman -Qkk yay pamac
yay: 0 total files, 0 altered files
error: package 'pamac' was not found

(base) [username@thing yay]$ type -a yay
bash: type: yay: not found

(base) [username@thing yay]$ echo $PATH
/home/username/miniconda3/bin:/home/username/miniconda3/condabin:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/opt/cuda/bin:/opt/cuda/nsight_compute:/opt/cuda/nsight_systems/bin:/var/lib/flatpak/exports/bin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl:/home/username/.local/share/yabridge

V1del wrote:

as for the verbose, the simplest way would be just to do
VERBOSE=1 makepkg -Csi
for example

(base) [username@thing yay]$ VERBOSE=1 makepkg -Csi
==> WARNING: A package has already been built, installing existing package...
==> Installing package yay with pacman -U...
[sudo] password for username: 
loading packages...
warning: yay-12.3.5-2 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Package (1)  Old Version  New Version  Net Change

yay          12.3.5-2     12.3.5-2       0.00 MiB


:: Proceed with installation? [Y/n] y
(1/1) checking keys in keyring                                                                      [###########################################################] 100%
(1/1) checking package integrity                                                                    [###########################################################] 100%
(1/1) loading package files                                                                         [###########################################################] 100%
(1/1) checking for file conflicts                                                                   [###########################################################] 100%
(1/1) checking available disk space                                                                 [###########################################################] 100%
:: Processing package changes...
(1/1) reinstalling yay                                                                              [###########################################################] 100%

seth · 2024-09-16 21:43:41

VERBOSE=1 makepkg -Csi

That doesn't work.
You've a prebuild package that somehow contains no files and you'll likely have to export the variable.

cd ..
rm -rf yay # first off, we clean up. completely
git clone https://aur.archlinux.org/yay.git
cd yay
less PKGBUILD # you're supposed to read than and make sure it doesn't do stupid stuff - aside installing yay of course
export VERBOSE=1
makepkg

The shorthand version would have been "makepkg -Csif", but with the empty package, I don't trust your PKGBUILD.

Edit: my bad, remove the "-v" from the makeflags. It's "--debug=verbose" but we won't need that.
Explains btw. why the package was "built" and is empty - "make -v" just prints the version.

Last edited by seth (2024-09-16 21:47:44)

rek · 2024-09-16 21:55:06

seth wrote:

VERBOSE=1 makepkg -Csi
That doesn't work.
You've a prebuild package that somehow contains no files and you'll likely have to export the variable.
cd ..
rm -rf yay # first off, we clean up. completely
git clone https://aur.archlinux.org/yay.git
cd yay
less PKGBUILD # you're supposed to read than and make sure it doesn't do stupid stuff - aside installing yay of course
export VERBOSE=1
makepkg
The shorthand version would have been "makepkg -Csif", but with the empty package, I don't trust your PKGBUILD.
Edit: my bad, remove the "-v" from the makeflags. It's "--debug=verbose" but we won't need that.
Explains btw. why the package was "built" and is empty - "make -v" just prints the version.

re: "my bad" i re-commented out the MAKEFLAGS in /etc/makepkg.conf

followed the instructions above and this is the dialog:

(base) [username@thing yay]$ cd ..
(base) [username@thing ~]$ rm -rf yay
(base) [username@thing ~]$ git clone https://aur.archlinux.org/yay.git
Cloning into 'yay'...
hint: Using 'master' as the name for the initial branch. This default branch name
hint: is subject to change. To configure the initial branch name to use in all
hint: of your new repositories, which will suppress this warning, call:
hint:
hint: 	git config --global init.defaultBranch <name>
hint:
hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
hint: 'development'. The just-created branch can be renamed via this command:
hint:
hint: 	git branch -m <name>
remote: Enumerating objects: 520, done.
remote: Counting objects: 100% (520/520), done.
remote: Compressing objects: 100% (353/353), done.
remote: Total 520 (delta 165), reused 504 (delta 164), pack-reused 0 (from 0)
Receiving objects: 100% (520/520), 101.95 KiB | 2.55 MiB/s, done.
Resolving deltas: 100% (165/165), done.
(base) [username@thing ~]$ cd yay
(base) [username@thing yay]$ export VERBOSE=1
(base) [username@thing yay]$ makepkg
==> Making package: yay 12.3.5-2 (Mon 16 Sep 2024 11:52:09 PM CEST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Downloading yay-12.3.5.tar.gz...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  444k  100  444k    0     0   693k      0 --:--:-- --:--:-- --:--:--  693k
==> Validating source files with sha256sums...
    yay-12.3.5.tar.gz ... Passed
==> Extracting sources...
  -> Extracting yay-12.3.5.tar.gz with bsdtar
==> Starting build()...
go build -trimpath -mod=readonly -modcacherw -ldflags '-X "main.yayVersion=12.3.5" -X "main.localePath=/usr/share/locale/" -linkmode=external -compressdwarf=false' -buildmode=pie -o yay
go: downloading github.com/Jguer/aur v1.2.3
go: downloading github.com/Jguer/go-alpm/v2 v2.2.2
go: downloading github.com/Jguer/votar v1.0.0
go: downloading github.com/Morganamilo/go-srcinfo v1.0.0
go: downloading github.com/deckarep/golang-set/v2 v2.6.0
go: downloading github.com/leonelquinteros/gotext v1.5.2
go: downloading golang.org/x/sys v0.18.0
go: downloading github.com/Morganamilo/go-pacmanconf v0.0.0-20210502114700-cff030e927a5
go: downloading github.com/adrg/strutil v0.3.1
go: downloading github.com/hashicorp/go-multierror v1.1.1
go: downloading golang.org/x/term v0.18.0
go: downloading golang.org/x/text v0.14.0
go: downloading github.com/itchyny/gojq v0.12.14
go: downloading github.com/mitchellh/mapstructure v1.5.0
go: downloading github.com/ohler55/ojg v1.21.4
go: downloading github.com/hashicorp/errwrap v1.1.0
go: downloading github.com/itchyny/timefmt-go v0.1.5
# runtime/cgo
<command-line>: error: "_FORTIFY_SOURCE" redefined [-Werror]
<command-line>: note: this is the location of the previous definition
cc1: all warnings being treated as errors
make: *** [Makefile:114: yay] Error 1
==> ERROR: A failure occurred in build().
    Aborting...

Last edited by rek (2024-09-16 21:55:32)

seth · 2024-09-16 22:09:05

grrrr…

Edit the "Makefile" add "-x -v" to the FLAGS

FLAGS ?= -x -v -trimpath -mod=readonly -modcacherw
…

And run "makepkg -e"

rek · 2024-09-16 22:15:02

(base) [username@thing yay]$ makepkg -e
==> Making package: yay 12.3.5-2 (Tue 17 Sep 2024 12:11:10 AM CEST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Removing existing $pkgdir/ directory...
==> Starting build()...
go build -x -v -trimpath -mod=readonly -modcacherw -ldflags '-X "main.yayVersion=12.3.5" -X "main.localePath=/usr/share/locale/" -linkmode=external -compressdwarf=false' -buildmode=pie -o yay
WORK=/tmp/go-build16465261
cd /home/username/yay
git status --porcelain
cd /home/username/yay
git -c log.showsignature=false log -1 --format=%H:%ct
runtime/cgo
mkdir -p $WORK/b127/
echo -n > $WORK/b127/preferlinkext # internal
cd /usr/lib/go/src/runtime/cgo
TERM='dumb' CGO_LDFLAGS='' /usr/lib/go/pkg/tool/linux_amd64/cgo -objdir $WORK/b127/ -importpath runtime/cgo -import_runtime_cgo=false -import_syscall=false "-ldflags=\"-Wl,-O1\" \"-Wl,--sort-common\" \"-Wl,--as-needed\" \"-Wl,-z,relro\" \"-Wl,-z,now\" \"-Wl,-z,pack-relative-relocs\" \"-lpthread\"" -- -DNDEBUG -D_FORTIFY_SOURCE=2 -O2 -isystem /home/username/miniconda3/include -I/home/username/miniconda3/targets/x86_64-linux/include -L/home/username/miniconda3/targets/x86_64-linux/lib -L/home/username/miniconda3/targets/x86_64-linux/lib/stubs -I $WORK/b127/ -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=3 -Wformat -Werror=format-security -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -g -ffile-prefix-map=/home/username/yay/src=/usr/src/debug/yay -Wall -Werror -fno-stack-protector ./cgo.go
cd $WORK/b127
TERM='dumb' /home/username/miniconda3/bin/x86_64-conda-linux-gnu-cc -I /usr/lib/go/src/runtime/cgo -fPIC -m64 -pthread -Wl,--no-gc-sections -fmessage-length=0 -ffile-prefix-map=$WORK/b127=/tmp/go-build -gno-record-gcc-switches -DNDEBUG -D_FORTIFY_SOURCE=2 -O2 -isystem /home/username/miniconda3/include -I/home/username/miniconda3/targets/x86_64-linux/include -L/home/username/miniconda3/targets/x86_64-linux/lib -L/home/username/miniconda3/targets/x86_64-linux/lib/stubs -I $WORK/b127/ -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=3 -Wformat -Werror=format-security -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -g -ffile-prefix-map=/home/username/yay/src=/usr/src/debug/yay -Wall -Werror -fno-stack-protector -ffile-prefix-map=/usr/lib/go=/_/GOROOT -frandom-seed=-JfSvGa7C15HsXhK5q0n -o $WORK/b127/_x001.o -c _cgo_export.c
# runtime/cgo
<command-line>: error: "_FORTIFY_SOURCE" redefined [-Werror]
<command-line>: note: this is the location of the previous definition
cc1: all warnings being treated as errors
make: *** [Makefile:114: yay] Error 1
==> ERROR: A failure occurred in build().
    Aborting...

I don't like seeing miniconda3 all the time on everything. Think that has something to do with it?

loqs · 2024-09-16 22:33:42

TERM='dumb' CGO_LDFLAGS='' /usr/lib/go/pkg/tool/linux_amd64/cgo -objdir $WORK/b127/ -importpath runtime/cgo -import_runtime_cgo=false -import_syscall=false "-ldflags=\"-Wl,-O1\" \"-Wl,--sort-common\" \"-Wl,--as-needed\" \"-Wl,-z,relro\" \"-Wl,-z,now\" \"-Wl,-z,pack-relative-relocs\" \"-lpthread\"" -- -DNDEBUG -D_FORTIFY_SOURCE=2 -O2 -isystem /home/username/miniconda3/include -I/home/username/miniconda3/targets/x86_64-linux/include -L/home/username/miniconda3/targets/x86_64-linux/lib -L/home/username/miniconda3/targets/x86_64-linux/lib/stubs -I $WORK/b127/ -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=3 -Wformat -Werror=format-security -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -g -ffile-prefix-map=/home/username/yay/src=/usr/src/debug/yay -Wall -Werror -fno-stack-protector ./cgo.go

If you turn off miniconda does that prevent "-D_FORTIFY_SOURCE=2" from being set in your environment in one of CFLAGS,CXXFLAGS,CPPFLAGS or LDFLAGS?
if in doubt post the output of `printenv`.

seth · 2024-09-16 22:38:14

If not:

-D_FORTIFY_SOURCE=2 … -D_FORTIFY_SOURCE=3

https://bugs.launchpad.net/ubuntu/+sour … ug/2052483

export CGO_CPPFLAGS=" -DFOOBAR -DNDEBUG -O2 -DSNAFU"
makepkg -e

rek · 2024-09-16 23:13:06

loqs wrote:

TERM='dumb' CGO_LDFLAGS='' /usr/lib/go/pkg/tool/linux_amd64/cgo -objdir $WORK/b127/ -importpath runtime/cgo -import_runtime_cgo=false -import_syscall=false "-ldflags=\"-Wl,-O1\" \"-Wl,--sort-common\" \"-Wl,--as-needed\" \"-Wl,-z,relro\" \"-Wl,-z,now\" \"-Wl,-z,pack-relative-relocs\" \"-lpthread\"" -- -DNDEBUG -D_FORTIFY_SOURCE=2 -O2 -isystem /home/username/miniconda3/include -I/home/username/miniconda3/targets/x86_64-linux/include -L/home/username/miniconda3/targets/x86_64-linux/lib -L/home/username/miniconda3/targets/x86_64-linux/lib/stubs -I $WORK/b127/ -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=3 -Wformat -Werror=format-security -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -g -ffile-prefix-map=/home/username/yay/src=/usr/src/debug/yay -Wall -Werror -fno-stack-protector ./cgo.go

If you turn off miniconda does that prevent "-D_FORTIFY_SOURCE=2" from being set in your environment in one of CFLAGS,CXXFLAGS,CPPFLAGS or LDFLAGS?
if in doubt post the output of `printenv`.

i realized that (base) in front of my prompt meant that conda was doing something so i did a 'conda deactivate' and got rid of the (base) and yay seemed to build a lot of stuff using makepkg -e.

sheesh. it was the darn (base) crap that Anaconda gets you to install. apparently having the cool (base) thing in front of my terminal prompt is a trojan horse for all sorts of nope.

So by disabling dang conda I was able finally to do a makepkg -si after that and it does appear yay is seen by the shell. remains to be seen if it's seen in (base). I thought (base) just meant (base) and only dealing with python, but it seems to be about more than just python. maybe there's python stuff involved in making packages. the heck.

next to find out if i can use yay to install pamac again...

and, it does appear that i did install pamac again, and installed Shotwell as a test, and it worked.

thanks very much although I have no idea why pamac stopped working in the first place. i need to figure out how to use conda without it being tied up with .bashrc and still be able to use it. someone has tried to explain that to me before but it's woosh.

I really appreciate the help.

Last edited by rek (2024-09-16 23:15:04)

seth · 2024-09-17 05:58:16

\o/
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

V1del · 2024-09-17 09:56:36

conda is an entire environment primarily designed to allow easy access to python to Windows installs. Using it on linux and letting it take over the environment is no end of issues.

As for why pamac broke. pacman released a new version and it's supporting libraries that mandate that third party tools making use of these libraries need to minimally get rebuilt (like yay) or if they were using deprecated functionality to be ported to the new libalpm version.

Arch Linux

#1 2024-09-16 10:27:28

pamac broke, yay broke, uninstalled both, can't reinstall either.

#2 2024-09-16 10:57:20

Re: pamac broke, yay broke, uninstalled both, can't reinstall either.

#3 2024-09-16 10:59:03

Re: pamac broke, yay broke, uninstalled both, can't reinstall either.

#4 2024-09-16 11:11:49

Re: pamac broke, yay broke, uninstalled both, can't reinstall either.

#5 2024-09-16 11:14:27

Re: pamac broke, yay broke, uninstalled both, can't reinstall either.

#6 2024-09-16 16:24:08

Re: pamac broke, yay broke, uninstalled both, can't reinstall either.

#7 2024-09-16 17:13:22

Re: pamac broke, yay broke, uninstalled both, can't reinstall either.

#8 2024-09-16 17:20:57

Re: pamac broke, yay broke, uninstalled both, can't reinstall either.

#9 2024-09-16 19:33:13

Re: pamac broke, yay broke, uninstalled both, can't reinstall either.

#10 2024-09-16 20:27:53

Re: pamac broke, yay broke, uninstalled both, can't reinstall either.

#11 2024-09-16 20:29:24

Re: pamac broke, yay broke, uninstalled both, can't reinstall either.

#12 2024-09-16 21:07:24

Re: pamac broke, yay broke, uninstalled both, can't reinstall either.

#13 2024-09-16 21:11:02

Re: pamac broke, yay broke, uninstalled both, can't reinstall either.

#14 2024-09-16 21:11:47

Re: pamac broke, yay broke, uninstalled both, can't reinstall either.

#15 2024-09-16 21:35:00

Re: pamac broke, yay broke, uninstalled both, can't reinstall either.

#16 2024-09-16 21:43:41

Re: pamac broke, yay broke, uninstalled both, can't reinstall either.

#17 2024-09-16 21:55:06

Re: pamac broke, yay broke, uninstalled both, can't reinstall either.

#18 2024-09-16 22:09:05

Re: pamac broke, yay broke, uninstalled both, can't reinstall either.

#19 2024-09-16 22:15:02

Re: pamac broke, yay broke, uninstalled both, can't reinstall either.

#20 2024-09-16 22:33:42

Re: pamac broke, yay broke, uninstalled both, can't reinstall either.

#21 2024-09-16 22:38:14

Re: pamac broke, yay broke, uninstalled both, can't reinstall either.

#22 2024-09-16 23:13:06

Re: pamac broke, yay broke, uninstalled both, can't reinstall either.

#23 2024-09-17 05:58:16

Re: pamac broke, yay broke, uninstalled both, can't reinstall either.

#24 2024-09-17 09:56:36

Re: pamac broke, yay broke, uninstalled both, can't reinstall either.

Board footer