Summary: | dev-libs/sway-0.6 - .../work/sway-0.6/sway/main.c:191:7: error: too few arguments to function ‘wlc_init’ | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Marek Paśnikowski <mail> |
Component: | [OLD] Library | Assignee: | Jasen Borisov <tajjada> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | mail, proxy-maint |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | build.log |
Description
Marek Paśnikowski
2016-05-20 06:51:46 UTC
I just tried building sway-0.6 with GCC 5.3.0 on my system, and I cannot reproduce this error. I tried both versions of wlc available in portage (0.0.2 and the live one), and both of them work. I saw you use systemd (you have the systemd USE flag enabled). That is the only difference in USE flag (on the sway package, at least) that I noticed between you and me (I don't use systemd), so I suspected that might be the problem. However, I just tried temporarily installing systemd and enabling the systemd USE flag for testing, and it still built just fine (no errors), so I confirmed it is indeed not the problem. Hmm, strange. I also tried building with your CFLAGS. Still built fine. I have no idea what the issue you are experiencing might be. This is strange. I will try to investigate more, but I just cannot reproduce your build failure. What about the "vtv" and "sanitize" flags in GCC? I have no idea what those two do exactly, but sounds to me like the "vtv" might have something to do here. I had enabled it thinking of security. I have just the slightest idea of programming, so the message "too few arguments" goes in line with requirement of certain quality level. The weird thing is that throughout my use of the current portage settings I never had this kind of error. I had seen missing headers sometimes only. Everything else in my system compiles fine, whatever I request. I also have zero runtime crashes for over a year now, so I am confident my flags are sane. As my computer is a slow laptop, recompilation of GCC (more than ten hours) just for one file is something I would rather avoid. I am a programmer, and yes, I agree that this error situation seems strange. You and I are compiling the exact same source code. The compiler error you are getting seems to indicate a mistake in the code (something that shouldn't be affected by CFLAGS, for instance, but I still gave it a try just in case), but yet it compiles for me. I have a fast CPU; it takes just a few minutes to rebuild GCC. I will play around with compiling gcc with vtv and other options, and see how that goes. I am a little busy over the next few hours, though, so I'll do that later today when I have time. The next lines in the build log are more interesting: In file included from /var/tmp/portage/dev-libs/sway-0.6/work/sway-0.6/sway/main.c:4:0: /usr/local/include/wlc/wlc.h:234:21: note: declared here Notice the "/usr/local". (In reply to Felix Janda from comment #4) > The next lines in the build log are more interesting: > > In file included from > /var/tmp/portage/dev-libs/sway-0.6/work/sway-0.6/sway/main.c:4:0: > /usr/local/include/wlc/wlc.h:234:21: note: declared here > > Notice the "/usr/local". I must be blind; that explains a lot ;-). Thank you for pointing it out. To the original poster: Please use the wlc package provided in gentoo. It provides the correct headers and version of wlc to build. It is the only supported way. There is no support anyone can give you if you have your own custom headers in /usr/local. Oi. I definitely understand how a header file from a test a few months back could break the compilation. Sorry about the false alert. However - is Portage standardized to use the '/usr/local' headers before the package's? Maybe it is a good idea to open a bug for Portage in order to set the headers' path to safeguard against external sources? (In reply to Marek Paśnikowski from comment #6) > Oi. I definitely understand how a header file from a test a few months back > could break the compilation. Sorry about the false alert. > However - is Portage standardized to use the '/usr/local' headers before the > package's? Maybe it is a good idea to open a bug for Portage in order to set > the headers' path to safeguard against external sources? Gentoo is about customisation and user choice, so locking the package manager down to prevent that would only be done with major problems. Regardless, generally the include paths are determined by the build system and preconceptions of upstreams - they expect you'll manually build and install software to /usr/local rather than using a package manager. |