| View previous topic :: View next topic |
| Author |
Message |
chaosys
n00b
Joined: 02 Nov 2017
Posts: 2
|
 Posted: Thu Nov 02, 2017 7:48 am Post subject: [SOLVED] New install failed to emerge sysklogd |
 |
|
I'm installing a new dual-boot instance of Gentoo, using SystemRescueCD off a USB drive as the initial install environment. I'm trying to keep this as by-the-book as possible, as it's been nearly a decade since I last used Gentoo. (I mostly ran Arch until now, but the proliferation of systemd drove me away.)
I've gotten to the point where I'm installing system tools in the chroot env, and have had no problem until trying to install sysklogd. The emerge attempt fails with this:
| >>> Failed to emerge app-admin/sysklogd-1.5.1: | syslogd.c: In function ‘reapchild’:
syslogd.c:2142:13: error: storage size of ‘status’ isn’t known
union wait status;
|
While I could use a different logger, I'd rather stick to something I'm familiar with until the system's standing on its own. This is just a desktop box anyway; my logging needs are pretty straightforward. Any help is appreciated.
build log
build env
emerge --info
| emerge -pqv: | | [ebuild N ] app-admin/sysklogd-1.5.1 USE="-logrotate" |
Last edited by chaosys on Thu Nov 02, 2017 9:22 pm; edited 2 times in total |
|
| Back to top |
|
 |
eccerr0r
Watchman
Joined: 01 Jul 2004
Posts: 9679
Location: almost Mile High in the USA
|
| Posted: Thu Nov 02, 2017 7:06 pm Post subject: |
|
|
I think this is a bug that just showed up, I was able to reproduce it with glibc-2.25.
I was able to build it on a 2-week old machine with glibc-2.23. Still researching though initial finds are that sysklogd will need to be fixed.
I think the best course of action is to upgrade to sysklogd-1.5.1-r1.
You'll need to keyword unmask it for now.
_________________
Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching?
Last edited by eccerr0r on Thu Nov 02, 2017 7:18 pm; edited 1 time in total |
|
| Back to top |
|
|
Jaglover
Watchman
Joined: 29 May 2005
Posts: 8291
Location: Saint Amant, Acadiana
|
|
| Back to top |
|
|
eccerr0r
Watchman
Joined: 01 Jul 2004
Posts: 9679
Location: almost Mile High in the USA
|
| Posted: Thu Nov 02, 2017 7:20 pm Post subject: |
|
|
Yes it was temporary, though I think I found an actual fix instead of a workaround:
Add the unmask
/etc/portage/package.keywords/glibc225.unmasks (or whatever):
| Code: | | =app-admin/sysklogd-1.5.1-r1 ~amd64 ~x86 |
(or whatever arch you are using)
Ref: https://bugs.gentoo.org/636046
"This too, shall pass." (hopefully this unmask will be redundant within the next few days and a simple emerge --sync will let you install the -r1 version.)
_________________
Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching? |
|
| Back to top |
|
|
fedeliallalinea
Administrator
Joined: 08 Mar 2003
Posts: 30915
Location: here
|
| Posted: Thu Nov 02, 2017 7:48 pm Post subject: |
|
|
And welcome 
_________________
Questions are guaranteed in life; Answers aren't. |
|
| Back to top |
|
|
chaosys
n00b
Joined: 02 Nov 2017
Posts: 2
|
| Posted: Thu Nov 02, 2017 8:31 pm Post subject: |
|
|
@eccerr0r:
That worked, thank you! Here's hoping the rest of the install goes fine. I'd like my system to at least be bootable before something else goes wrong.  |
|
| Back to top |
|
|
|
Installing Gentoo
