| Summary: | net-irc/inspircd-1.0.6.ebuild bad built_with_use check | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Wolf Giesen (RETIRED) <frilled> |
| Component: | New packages | Assignee: | William Pitcock <nenolod> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | bugs, hansmi |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
inspircd-1.0.6-r1.ebuild
inspircd-1.0.7.ebuild inspircd-1.0.6-1.0.7.diff inspircd-1.0.8.ebuild inspircd-1.0.8-r1.ebuild |
||
Acknowledged, thanks. Created attachment 99177 [details]
inspircd-1.0.6-r1.ebuild
Hi, can you test this and see if it fixes it for you? It worked for me, anyway.
If it works for you, mark this bug as resolved and I will send it to Hansmi for committing.
William, can you please add a diff? That's easier to see the differences. No need to send it to me, I'm watching this bug. --- inspircd-1.0.6.ebuild 2006-10-09 04:01:18.000000000 -0500
+++ inspircd-1.0.6-r1.ebuild 2006-10-09 04:02:00.000000000 -0500
@@ -95,7 +95,8 @@
_EOF_
# for a rainy day: USE="ssl" could be gnutls too?
- inspircd_use_enable openssl ssl HAS_OPENSSL y n
+ inspircd_use_enable openssl openssl HAS_OPENSSL y n
+ inspircd_use_enable gnutls gnutls HAS_GNUTLS y n
# build makefiles based on our configure params
# Please note that it's not the autoconf configure script, thus
>>> Emerging (1 of 2) net-irc/inspircd-1.0.6-r1 to / * InspIRCd-1.0.6.tar.bz2 MD5 ;-) ... [ ok ] * InspIRCd-1.0.6.tar.bz2 RMD160 ;-) ... [ ok ] * InspIRCd-1.0.6.tar.bz2 SHA1 ;-) ... [ ok ] * InspIRCd-1.0.6.tar.bz2 SHA256 ;-) ... [ ok ] * InspIRCd-1.0.6.tar.bz2 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * checking InspIRCd-1.0.6.tar.bz2 ;-) ... [ ok ] >>> Unpacking source... >>> Unpacking InspIRCd-1.0.6.tar.bz2 to /var/tmp/portage/inspircd-1.0.6-r1/work tar: Read 5632 bytes from - >>> Source unpacked. >>> Compiling source in /var/tmp/portage/inspircd-1.0.6-r1/work/inspircd ... * Building configuration parameters file. !!! ERROR: net-irc/inspircd-1.0.6-r1 failed. Call stack: ebuild.sh, line 1546: Called dyn_compile ebuild.sh, line 937: Called src_compile inspircd-1.0.6-r1.ebuild, line 98: Called inspircd_use_enable 'openssl' 'openssl' 'HAS_OPENSSL' 'y' 'n' inspircd-1.0.6-r1.ebuild, line 38: Called built_with_use 'openssl' 'openssl' eutils.eclass, line 1619: Called die !!! dev-libs/openssl-0.9.8d does not actually support the openssl USE flag! !!! If you need support, post the topmost build error, and the call stack if relevant. !!! This ebuild is from an overlay: '/usr/local/portage' BTW: What about 1.0.7 ("fossil")? .-)
rats. ok, i'll update it to 1.0.7 (fossil), and strip out SSL support for now until I can figure out what is going on with this openssl ebuild conflict... but I'm kinda busy right now so it will have to wait until tonight if that's OK. Hey, I'm happy you're working on it! Hm. SSL support in itself works; the obvious problem seems to me that your're testing whether openssl was built with "ssl" use flag, which in turn doesn't work. Sorry for pointing out the profane .-) It shouldn't be testing openssl though. It should just be checking if SSL is in USE. ;) Sorry, I don't get it ... you're calling "inspircd_use_enable openssl openssl HAS_OPENSSL y n" and inspircd_use_enable in turn does a if built_with_use openssl openssl [...] What else is supposed to happen? (In reply to comment #10) > It shouldn't be testing openssl though. It should just be checking if SSL is in > USE. ;) For that, use "use": if use ssl then echo foo fi That hit me right after I hit commit to add the comment. Anyhow, 1.0.7 ebuild later today. :) Created attachment 100192 [details]
inspircd-1.0.7.ebuild
InspIRCd 1.0.7 ebuild.
- fixes improper SSL built_with_use
- updates to 1.0.7 release
- changes USE=ssl to USE=openssl or USE=gnutls to select which SSL engine modules to enable
Created attachment 100193 [details, diff]
inspircd-1.0.6-1.0.7.diff
Differences between the 1.0.6 and 1.0.7 ebuilds.
Resolved by 1.0.7 ebuild, should be committed soon enough. CVSed Heh. I'll report once I have a test environment up (as I'm already using the SVN version now). BRB. Well, that was easy (virtualization is really handy sometimes). Here's what I get without any of the ssl USE flags: make[1]: Leaving directory `/var/tmp/portage/inspircd-1.0.7/work/inspircd/src/modules' ************************************* * BUILD COMPLETE! * * To install InspIRCd, type: * * make install * ************************************* !!! ERROR: net-irc/inspircd-1.0.7 failed. Call stack: ebuild.sh, line 1546: Called dyn_compile ebuild.sh, line 937: Called src_compile inspircd-1.0.7.ebuild, line 128: Called die !!! emake failed !!! If you need support, post the topmost build error, and the call stack if relevant. With USE="openssl", it builds correctly, though. *** Bug 152495 has been marked as a duplicate of this bug. *** Fixing it in ~arch won't exactly help for folks that run stable. Reopen. (In reply to comment #19) > Here's what I get without any of the ssl USE flags: I tried this: USE="-*" ebuild inspircd-1.0.7.ebuild clean install and it worked. How to reproduce your error? Good question, since I can't reproduce it myself now. I'll have to retry with a fresh VM, I guess. Anything new on this? I just checked out the 1.0.7 ebuild, and there are still a couple if issues: Logging goes to the wrong place (it would want to put it to /usr/bin/...); if that isn't a compile-time option (don't remember whether it was), it should be put in the init script with "-logfile /var/log/inspircd.log" or sth. like that. You should be nice and pre-edit the .conf file to reflect the locations you install stuff to; it's all set to "/path/to/..." I built with USE="openssl"; I know gnutls is preferred, but I had openssl on that server but no gnutls. Anyway, the module is not built (or not installed): # equery f inspircd |grep ssl /usr/lib/inspircd/modules/m_ssl_dummy.so /usr/lib/inspircd/modules/m_sslmodes.so Alas, m_ssl_openssl.so is missing. There may be more, I was kinda in a hurry to set that one up and thought I'd try the ebuild for a change ^_^, but those are stumbling blocks; especially the missing logging is annoying since there does not seem to be a config option (or it's not included in the .example) and you just can't see why it doesn't work :D It's because the damn InspIRCd buildsystem doesn't listen unless you do manual configure. The only solution is the pull SSL support entirely, or drop the ebuild. I do not wish to package 1.1 because there are drastic changes being made to it, but it uses a more autoconf-like system (think: mplayer). Created attachment 102933 [details]
inspircd-1.0.8.ebuild
inspircd-1.0.8 ebuild:
- version bump
- remove SSL support due to inspircd 1.0.x buildsystem not supporting it any other way than by manual configure
this ebuild can be used as 1.0.6-r1, 1.0.7-r1 too.
Created attachment 102934 [details]
inspircd-1.0.8-r1.ebuild
inspircd-1.0.8.ebuild with how-to-use-SSL information removed.
1.0.7-r1 in CVS From the diff I'd say 1.0.7-r1 is not supposed to fix the logging, right? Please reopen and bug nenolod if there's someething left. |
Regardless of "ssl" USE flag, the ebuild fails on line 98 (the "rainy day section"): >> inspircd_use_enable openssl ssl HAS_OPENSSL y n resulting in !!! ERROR: net-irc/inspircd-1.0.6 failed. Call stack: ebuild.sh, line 1546: Called dyn_compile ebuild.sh, line 937: Called src_compile inspircd-1.0.6.ebuild, line 98: Called inspircd_use_enable 'openssl' 'ssl' 'HAS_OPENSSL' 'y' 'n' inspircd-1.0.6.ebuild, line 38: Called built_with_use 'openssl' 'ssl' eutils.eclass, line 1619: Called die !!! dev-libs/openssl-0.9.8d does not actually support the ssl USE flag! !!! If you need support, post the topmost build error, and the call stack if relevant. Removed the check, built successfully.