You are not logged in.
Pages: 1
I'm trying to install wine3.0 on my laptop using yaourt wine-stable but it came up with a makepkg error. I tried executing it by it self just in case it was yaourt causing the problem.
[root@Arch /]# makepkg
==> ERROR: Running makepkg as root is not allowed as it can cause permanent,
catastrophic damage to your system.
==> ERROR: An unknown error has occurred. Exiting...
I tried executing it as a normal user but it came up with a permission denied message. Do i make a user in a certain group(s) or do i edit makepkg.conf?
Offline
Which instructions did you follow to install Arch Linux?
Mod note: Moving to NC.
Last edited by V1del (2018-03-20 10:08:24)
Offline
[root@Arch /]# makepkg
==> ERROR: Running makepkg as root is not allowed as it can cause permanent,
catastrophic damage to your system.
I'm confused. Did you run yaourt or makepkg? It seems like you ran makepkg as root. Have you tried running it as a normal user?
Offline
spegesilden, read the first post. Both of your questions were already addressed quite clearly and succinctly.
Onixiya, the errors while attempting to run makepkg as root are expected - don't do that. You say there are other errors when it is run as a regular user; those are what we need to see. Though I'd first say start fresh, remove the PKGBUILD and any associated files and start in a new directory that your user has access to (definitely not /).
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
V1del
I followed the instructions on the wiki
Trilby
I tried again but this time it went through though it didn't build because of a bunch of lib32 deps missing and it couldn't download them.
Offline
Paste your pacman.conf and full pacman.log
Offline
Please read https://bbs.archlinux.org/viewtopic.php?id=57855
No one can help you with those sparse bits of information.
Offline
Onixiya, you've been asked several times now for actual error message, not vauge summaries of them. All that output might seem nonsensical to you, but it makes perfect sense to those of us more familiar with it - but only if we see it.
I do think the vague bits you have referenced to point to a likely cause of the problem, but it'd be much better to know based on fact rather than to speculate based on vague description. But I'd gather you have not enabled multilib which is required for wine - that's where the lib32 dependencies come from.
You'll also find that a comparable version of wine is already available in the multilib repo. Do you even need to build this yourself?
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
Pages: 1