View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003958 | unreal | installing | public | 2010-09-08 16:29 | 2010-09-08 17:39 |
| Reporter | chotaire | Assigned To | syzop | ||
| Priority | normal | Severity | major | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Platform | x86 | OS | QNX | OS Version | 6.5.0 |
| Product Version | 3.2.9-RC1 | ||||
| Fixed in Version | 3.2.9-RC1 | ||||
| Summary | 0003958: ./Config does not forward --enable-inet6 parameter to configure process | ||||
| Description | There is a HOT new issue with CVS regarding IPv6, I realize it cannot bind stream sockets to IPv6 addresses anymore, while this worked fine with 3.2.8.1. IPv6 was select during ./Config. I am adding log entries: [Wed Sep 8 16:02:49 2010] - setsockopt(IP_OPTIONS) irc.example.com[]:Invalid argument [Wed Sep 8 16:02:49 2010] - Error binding stream socket to IP 2001.0.0.0 port 7100 - irc.example.com[]:Can't assign requested address [Wed Sep 8 16:03:51 2010] - setsockopt(IP_OPTIONS) irc.example.com[]:Invalid argument [Wed Sep 8 16:03:51 2010] - Error binding stream socket to IP 2001.0.0.0 port 7100 - irc.example.com[]:Can't assign requested address While double-checking the ./configure progress I realize that eventhough IPv6 was enabled by default, --enable-inet6 was not added to the configure parameters (!). Adding it to the extra parameters in ./Config fixes the issue and IPv6 is compiled in properly. ziplinks are not affected by this bug. I haven't tested remote includes. | ||||
| Tags | No tags attached. | ||||
| 3rd party modules | |||||
|
|
I think I misread configure.ac, try reverting this patch (for ./Config), and see if it solves things: http://cvsweb.unrealircd.com/cgi-bin/cvsweb/unreal/Config.diff?r1=1.1.1.1.4.1.2.58.2.24;r2=1.1.1.1.4.1.2.58.2.25 |
|
|
Hm, yeah, that must be the issue, fixed in .878: - Reverted an IPv6/Config fix I did on July 17. Reported by chotaire (0003958). |
|
|
syzop: Not directly pertaining to this bug, but this issue and similar ones could be avoided if the code looked like: if [ "$INET6" = "1" ]; then ARG="$ARG--enable-inet6 " else ARG="$ARG--disable-inet6 " fi May I change ./Config to do this for all ./configure options? |
|
|
Why would we want to add X options when they have no effect? :P Actually it was all working ok, until you decided to set different defaults... Perhaps another time, but not now. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2010-09-08 16:29 | chotaire | New Issue | |
| 2010-09-08 17:14 | syzop | Note Added: 0016345 | |
| 2010-09-08 17:15 | syzop | Note Edited: 0016345 | |
| 2010-09-08 17:18 | syzop | QA | => Not touched yet by developer |
| 2010-09-08 17:18 | syzop | U4: Need for upstream patch | => No need for upstream InspIRCd patch |
| 2010-09-08 17:18 | syzop | Note Added: 0016346 | |
| 2010-09-08 17:18 | syzop | Status | new => resolved |
| 2010-09-08 17:18 | syzop | Fixed in Version | => 3.2.9-RC1 |
| 2010-09-08 17:18 | syzop | Resolution | open => fixed |
| 2010-09-08 17:18 | syzop | Assigned To | => syzop |
| 2010-09-08 17:25 | ohnobinki | Note Added: 0016348 | |
| 2010-09-08 17:39 | syzop | Note Added: 0016349 |
