[Solved] yay update from 11.3.2-1 to 12.0.3-1 fails

ddeimeke · 2023-04-08 10:13:06

Hi!

I get an error "No rule to make target '24" from make when trying an update of yay.

The log is as follows.

Any ideas that might solve the issue?

Thanks in advance

Dirk

$ yay -Syu
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community is up to date
:: Starting full system upgrade...
 there is nothing to do
:: Searching databases for updates...
:: Searching AUR for updates...
 -> Missing AUR Packages:  gfbgraph
:: 1 Packages to upgrade.
1  aur/yay  11.3.2-1 -> 12.0.3-1
==> Packages to exclude: (eg: "1 2 3", "1-3", "^4" or repo name)
==> 
:: Checking for conflicts...
:: Checking for inner conflicts...
[Aur:1]  yay-12.0.3-1

  1 yay                                      (Installed) (Build Files Exist)
==> Packages to cleanBuild?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==> 
:: PKGBUILD up to date, Skipping (1/0): yay
  1 yay                                      (Installed) (Build Files Exist)
==> Diffs to show?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==> 
:: (1/1) Parsing SRCINFO: yay
==> Making package: yay 12.0.3-1 (Sa 08 Apr 2023 08:19:02)
==> Retrieving sources...
  -> Found yay-12.0.3.tar.gz
==> Validating source files with sha256sums...
    yay-12.0.3.tar.gz ... Passed
==> Making package: yay 12.0.3-1 (Sa 08 Apr 2023 08:19:04)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found yay-12.0.3.tar.gz
==> Validating source files with sha256sums...
    yay-12.0.3.tar.gz ... Passed
==> Removing existing $srcdir/ directory...
==> Extracting sources...
  -> Extracting yay-12.0.3.tar.gz with bsdtar
==> Sources are ready.
==> Making package: yay 12.0.3-1 (Sa 08 Apr 2023 08:19:08)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Removing existing $pkgdir/ directory...
==> Starting build()...
make: *** No rule to make target '24
scaling'.  Stop.
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: yay

Last edited by ddeimeke (2023-04-08 12:51:19)

Lone_Wolf · 2023-04-08 11:09:09

Building latest yay version with makepkg works.

Please read https://wiki.archlinux.org/title/AUR_helpers and https://wiki.archlinux.org/title/Arch_User_Repository .
If you still want to use yay after reading the 1st link, the 2nd link should provide enough info to build it with makepkg yourself.

Last edited by Lone_Wolf (2023-04-08 11:09:38)

Scimmia · 2023-04-08 11:21:12

What's in your MAKEFLAGS in makepkg.conf?

ddeimeke · 2023-04-08 12:52:38

Because of the manual build failing with the same error message, I replaced yay with yay-bin.

Trilby · 2023-04-08 13:10:58

And we'll look forward to your next thread when you get a similar issue next time you try to build anything from the AUR as you've not solved the problem, but rather just brushed it under the rug for later.

The only way this would not come back to bite you very soon is if you don't actually use any other AUR packages. And if you don't use any other AUR packages, why on earth would you use yay (really that shouldn't even be a conditional question: why on earth would anyone use yay ... but only the conditional form really needs to be addressed here).

ddeimeke · 2023-04-08 13:17:50

Scimmia wrote:

What's in your MAKEFLAGS in makepkg.conf?

Nothing so far

$ grep MAKEFLAGS /etc/makepkg.conf 
#MAKEFLAGS="-j2"
...

Same in /home/dirk/.cache/yay/pacman-git/makepkg.conf.

Last edited by ddeimeke (2023-04-08 13:18:34)

Trilby · 2023-04-08 13:27:37

Add a "set -x" as the first line of the build() function in the PKGBUILD and run makepkg again so we can see exactly what commnd is generating the error. Also check any other flags set in makepkg.conf - or as a quick and easy check `grep 24 /etc/makepkg.conf`.

Last edited by Trilby (2023-04-08 13:28:50)

ddeimeke · 2023-04-08 15:52:27

Trilby wrote:

Add a "set -x" as the first line of the build() function in the PKGBUILD and run makepkg again so we can see exactly what commnd is generating the error. Also check any other flags set in makepkg.conf - or as a quick and easy check `grep 24 /etc/makepkg.conf`.

I expect the target to be in the Makefile.

Will check tomorrow.

Trilby · 2023-04-08 15:58:42

The fact that no one else gets this error suggests that it comes from a configuration on your system - and there is no '24 in the makefile - it most likely comes from an expansion of one of the exported variables.

ddeimeke · 2023-04-08 21:08:59

Trilby wrote:

The fact that no one else gets this error suggests that it comes from a configuration on your system - and there is no '24 in the makefile - it most likely comes from an expansion of one of the exported variables.

I think I found the line in my .bashrc (completely forgot about it):

export MAKEFLAGS="-j $(lscpu | awk '/^CPU\(s\):/ {print $2}')"

With unsetting the variable everything works again.

Thank you all for your support.

Dirk

Trilby · 2023-04-08 21:26:24

That is a perfectly reasonable line to include except for two critiques and one condition. First the condition: (something like) that would often be in makepkg.conf. Having it in your shellrc could also make sense if you regularly build software manually with `make`.

Then the two critiques: 1) there's no reason to calculate that every time the shellrc (or makepkg.conf) is sourced: the number of processors isn't changing. Just set it to the number of processors/cores you actually have. And even if you do want to determine it dynamically, just use `nproc` rather than parsing lscpu. 2) despite these critiques, that line as written here on the forums would be fine - but a typo in that line could very easily cause the problem noted in this thread. There's no need to throw out the whole setting to fix the typo.

Last edited by Trilby (2023-04-08 21:28:05)

ddeimeke · 2023-04-09 16:14:53

Trilby wrote:

That is a perfectly reasonable line to include except for two critiques and one condition. First the condition: (something like) that would often be in makepkg.conf. Having it in your shellrc could also make sense if you regularly build software manually with `make`.

Yes, I used to work a lot with make, but since I left the Taskwarrior-team, it does not make sense anymore.

On other Linux-distributions there is no such thing like makepkg.conf (I use Linux for about 27 years now, but I am pretty new to Arch Linux, which I use for about nine months).

Trilby wrote:

Then the two critiques: 1) there's no reason to calculate that every time the shellrc (or makepkg.conf) is sourced: the number of processors isn't changing. Just set it to the number of processors/cores you actually have. And even if you do want to determine it dynamically, just use `nproc` rather than parsing lscpu. 2) despite these critiques, that line as written here on the forums would be fine - but a typo in that line could very easily cause the problem noted in this thread. There's no need to throw out the whole setting to fix the typo.

Absolutely agreed with that.

I have the feeling that parts of my .bashrc are much older than nproc, thanks for the hint. :-)

Dirk

Arch Linux

#1 2023-04-08 10:13:06

[Solved] yay update from 11.3.2-1 to 12.0.3-1 fails

#2 2023-04-08 11:09:09

Re: [Solved] yay update from 11.3.2-1 to 12.0.3-1 fails

#3 2023-04-08 11:21:12

Re: [Solved] yay update from 11.3.2-1 to 12.0.3-1 fails

#4 2023-04-08 12:52:38

Re: [Solved] yay update from 11.3.2-1 to 12.0.3-1 fails

#5 2023-04-08 13:10:58

Re: [Solved] yay update from 11.3.2-1 to 12.0.3-1 fails

#6 2023-04-08 13:17:50

Re: [Solved] yay update from 11.3.2-1 to 12.0.3-1 fails

#7 2023-04-08 13:27:37

Re: [Solved] yay update from 11.3.2-1 to 12.0.3-1 fails

#8 2023-04-08 15:52:27

Re: [Solved] yay update from 11.3.2-1 to 12.0.3-1 fails

#9 2023-04-08 15:58:42

Re: [Solved] yay update from 11.3.2-1 to 12.0.3-1 fails

#10 2023-04-08 21:08:59

Re: [Solved] yay update from 11.3.2-1 to 12.0.3-1 fails

#11 2023-04-08 21:26:24

Re: [Solved] yay update from 11.3.2-1 to 12.0.3-1 fails

#12 2023-04-09 16:14:53

Re: [Solved] yay update from 11.3.2-1 to 12.0.3-1 fails

Board footer