Bug 102528 - unable to rebuild wvdial from srpm
Summary: unable to rebuild wvdial from srpm
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: wvdial
Version: 3.0
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Nalin Dahyabhai
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-08-16 16:59 UTC by alex kramarov
Modified: 2007-11-30 22:06 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2003-09-11 21:03:18 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description alex kramarov 2003-08-16 16:59:29 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 
1.1.4322)

Description of problem:
while rebuilding the srpm on taroon machine :

/usr/include/wvstreams/wvstream.h:21: warning: `typename
   WvStreamCallback_bound<T>::BoundFunc' is implicitly a typename
/usr/include/wvstreams/wvstream.h:21: warning: implicit typename is deprecated,
   please see the documentation for details
wvmodemscan.cc: In member function `void WvModemScan::execute()':
wvmodemscan.cc:140: invalid conversion from `WvModem*' to `long int'
wvmodemscan.cc:204: invalid conversion from `WvModem*' to `long int'
wvmodemscan.cc:310: invalid conversion from `WvModem*' to `long int'
wvmodemscan.cc: In member function `size_t WvModemScan::coagulate(char*,
   unsigned int, int)':
wvmodemscan.cc:414: invalid conversion from `WvModem*' to `long int'
make[1]: *** [wvmodemscan.o] Error 1
make: *** [src] Error 2
error: Bad exit status from /var/tmp/rpm-tmp.63179 (%build)



Version-Release number of selected component (if applicable):
wvdial-1.53-9.src.rpm

How reproducible:
Always

Steps to Reproduce:
1.get a taroon machine
2.rpmbuild --rebuild wvdial-1.53-9.src.rpm
3.
    

Actual Results:  failes

Expected Results:  should succeed

Additional info:

Comment 1 Nalin Dahyabhai 2003-09-11 21:03:18 UTC
Can't reproduce this failure on my B1 test system with either 1.53-9 or 1.53-11.


Note You need to log in before you can comment on or make changes to this bug.