Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 934123 - dev-ruby/racc-1.7.3 assumes /usr/bin/mkdir path
Summary: dev-ruby/racc-1.7.3 assumes /usr/bin/mkdir path
Status: RESOLVED DUPLICATE of bug 932386
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-06-12 07:13 UTC by fjmccloud
Modified: 2024-06-12 16:19 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description fjmccloud 2024-06-12 07:13:54 UTC
dev-ruby/racc-1.7.3 has a hard-coded expectation of /usr/bin/mkdir on systems where /bin/mkdir exists.

I use this profile:
default/linux/amd64/23.0/split-usr/desktop

and this results in

>>> Install dev-ruby/racc-1.7.3 into /var/tmp/portage/dev-ruby/racc-1.7.3/image
 * Running install phase for ruby31
 * installing extensions
make -j9 V=1 sitearchdir=/var/tmp/portage/dev-ruby/racc-1.7.3/image/usr/lib64/ruby/gems/3.1.0/extensions/x86_64-linux/3.1.0/racc-1.7.3 sitelibdir=/var/tmp/portage/dev-ruby/racc-1.7.3/image/usr/lib64/ruby/site_ruby/3.1.0 -C ext/racc/cparse install
make: Entering directory '/var/tmp/portage/dev-ruby/racc-1.7.3/work/ruby31/racc-1.7.3/ext/racc/cparse'
/usr/bin/mkdir -p . /var/tmp/portage/dev-ruby/racc-1.7.3/image/usr/lib64/ruby/gems/3.1.0/extensions/x86_64-linux/3.1.0/racc-1.7.3/racc
make: /usr/bin/mkdir: No such file or directory
make: *** [Makefile:204: .sitearchdir.-.racc.time] Error 127
make: Leaving directory '/var/tmp/portage/dev-ruby/racc-1.7.3/work/ruby31/racc-1.7.3/ext/racc/cparse' 



This bug is filed as per request from the forum here:
https://forums.gentoo.org/viewtopic-p-8829964.html#8829964
and it might have relations with existing bug
https://bugs.gentoo.org/932386
Comment 1 Mike Gilbert gentoo-dev 2024-06-12 16:19:10 UTC

*** This bug has been marked as a duplicate of bug 932386 ***