OMNeT++/OMNEST Bug Tracker - OMNeT++ | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0000106 | OMNeT++ | command line tools | public | 2009-09-09 16:33 | 2009-09-10 13:54 |
| Reporter | andras | ||||
| Assigned To | andras | ||||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Platform | x86 | OS | Windows | OS Version | XP |
| Product Version | 4.0 | ||||
| Target Version | Fixed in Version | 4.1 | |||
| Summary | 0000106: configure script sets HAVE_PCAP even if wpcap.dll is missing | ||||
| Description | On Windows, OMNeT++ ships with a pcap.lib (in msys/lib). However, pcap.lib depends on wpcap.dll which is NOT contained in OMNeT++, but needs to be installed separately as part of WinPCAP. The problem is that the configure script detects pcap.lib, and thus adds -DHAVE_PCAP to CFLAGS (and -lpcap to LDFLAGS). That is, any program that contains #ifdef HAVE_PCAP blocks (e.g. INET Framework!!!) will compile automatically with PCAP support, however it will fail to run because the wpcap.dll is missing. Fix: configure should check if it can actually *run* a program that links with pcap, and only set HAVE_PCAP if it was successful. | ||||
| Steps To Reproduce | |||||
| Additional Information | |||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2009-09-09 16:33 | andras | New Issue | |||
| 2009-09-10 13:54 | andras | Note Added: 0000172 | |||
| 2009-09-10 13:54 | andras | Status | new => resolved | ||
| 2009-09-10 13:54 | andras | Fixed in Version | => 4.1 | ||
| 2009-09-10 13:54 | andras | Resolution | open => fixed | ||
| 2009-09-10 13:54 | andras | Assigned To | => andras | ||
| Notes | |||||
|
|
|||||
|
|
||||