ManjaroThis forum is for the discussion of Manjaro Linux. Note: This forum does not have any official participation.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
==> entrance-git dependencies:
- efl (already installed)
- xorg-xauth (already installed)
- sudo (already installed)
- git (already installed) [makedepend]
- meson (already installed) [makedepend]
==> Continue building entrance-git ? [Y/n]
==> --------------------------------------
==>
==> Building and installing package
==> Making package: entrance-git 3.0.0_alpha5.r10.gb8894ea-1 (Sun 21 Oct 2018 02:58:47 PM CDT)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Updating entrance git repo...
Fetching origin
==> Validating source files with sha256sums...
entrance ... Skipped
==> Extracting sources...
-> Creating working copy of entrance git repo...
Switched to a new branch 'makepkg'
==> Starting prepare()...
==> Starting pkgver()...
==> Removing existing $pkgdir/ directory...
==> Starting build()...
+ exec meson setup --prefix /usr --libdir /usr/lib --libexecdir /usr/lib --bindir /usr/bin --sbindir /usr/bin --includedir /usr/include --datadir /usr/share --mandir /usr/share/man --infodir /usr/share/info --localedir /usr/share/locale --sysconfdir /etc --localstatedir /var --sharedstatedir /var/lib --buildtype release --auto-features enabled --wrap-mode nofallback -D b_lto=true build -Dconsolekit=false -Dlogind=true
The Meson build system
Version: 0.48.1
Source dir: /tmp/yaourt-tmp-userx/aur-entrance-git/src/entrance
Build dir: /tmp/yaourt-tmp-userx/aur-entrance-git/src/entrance/build
Build type: native build
meson_options.txt:9:0: ERROR: Option name debug is reserved.
A full log can be found at /tmp/yaourt-tmp-userx/aur-entrance-git/src/entrance/build/meson-logs/meson-log.txt
==> ERROR: A failure occurred in build().
Aborting...
==> ERROR: Makepkg was unable to build entrance-git.
==> Restart building entrance-git ? [y/N]
what is this meson_options.txt:9:0: ERROR: Option name debug is reserved. error all about and how can I fix that? it is not located within the build script whatsoever.
you still didn't learn:
1. what are you doing at all? (what package/file, where is it from, what commands, whatever else might be important...)
2. especially did you check the mentioned log file?
you still didn't learn:
1. what are you doing at all? (what package/file, where is it from, what commands, whatever else might be important...)
2. especially did you check the mentioned log file?
did you see this bold part in my post?
'meson_options.txt:9:0: ERROR: Option name debug is reserved.'
I have no idea where that file is located, it is not made mention of in the build script. after I posted I remembered, then looked on the web page for messages about this package. nope, missed that line below the ERROR message.
though I did get it to compile, forgot what I did to get it to, I think I just took it to the source, compiled, installed, crashed, looked it up on git, seen the image they use, I remember it looking a lot cooler back when, so I just put that little project aside.
Ok, again: This LQ forum is really good, you can ask anything - if you cannot figure out. That's what I do too. But this is only one aspect. The other one: see here. If you [would] give more information about your problem you will/would get better responses/answers. Dropping in a meaningless error message will lead to a meaningless one-liner answer. It is not about you, it is about the nature of communication, nature of people.
I know you think there is someone who is actually familiar with that message and will give you a how-to-solve-it-in-5-minutes immediately, but I'm afraid, posting without context makes it impossible.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.