Linux From Scratch This Forum is for the discussion of LFS.
LFS is a project that provides you with the steps necessary to build your own custom Linux system. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
03-09-2003, 09:52 PM
|
#1
|
LQ Newbie
Registered: Nov 2002
Location: Houston, Texas
Distribution: LFS-4.0 and Mandrake 9.0
Posts: 7
Rep:
|
wvstreams & openssl
I followed the blfs docs instructions and have the same versions;
wvstreams-3.70
openssl-0.9.6g
and ran ldconfig -v but get this when I try to install wvstreams
Quote:
make PREFIX=/usr &&
> make PREFIX=/usr install
.
.
--> Making all in /LFS/blfs/wvstreams-3.70/src/streams...
Using my own device locking functions in wvlockfile.
g++ $_R_CXXFLAGS -c wvstream.cc
In file included from wvstream.h:10,
from wvstream.cc:11:
../utils/wvcallback.h:104: warning: `typename WvCallback0<RET>::Fake' is
implicitly a typename
../utils/wvcallback.h:104: warning: implicit typename is deprecated, please see
the documentation for details
../utils/wvcallback.h:106: warning: `typename WvCallback0_bound<RET, T>::Fake'
is implicitly a typename
../utils/wvcallback.h:106: warning: implicit typename is deprecated, please see
the documentation for details
../utils/wvcallback.h:106: warning: `typename WvCallback0_bound<RET, T>::Func'
is implicitly a typename
../utils/wvcallback.h:106: warning: implicit typename is deprecated, please see
the documentation for details
.
.
.
In file included from cfgentry.cc:10:
wvconf.h:66: warning: `typename WvConfCallback_bound<T>::BoundFunc' is
implicitly a typename
wvconf.h:66: warning: implicit typename is deprecated, please see the
documentation for details
rm -f configfile.libs
echo wvconf.o cfgsection.o cfgentry.o ../streams/streams.libs >configfile.libs
--> Making all in /LFS/blfs/wvstreams-3.70/src/ipstreams...
g++ $_R_CXXFLAGS -c wvaddr.cc
wvaddr.cc:641: prototype for `WvIPPortAddr::WvIPPortAddr(unsigned char*, short
unsigned int)' does not match any in class `WvIPPortAddr'
wvaddr.h:365: candidates are: WvIPPortAddr::WvIPPortAddr(const WvIPPortAddr&)
wvaddr.h:382: WvIPPortAddr::WvIPPortAddr(sockaddr_in*)
wvaddr.h:380: WvIPPortAddr::WvIPPortAddr(const char*, short
unsigned int)
wvaddr.h:379: WvIPPortAddr::WvIPPortAddr(short unsigned int)
wvaddr.h:376: WvIPPortAddr::WvIPPortAddr(const WvString&)
wvaddr.h:374: WvIPPortAddr::WvIPPortAddr(const char*)
wvaddr.h:373: WvIPPortAddr::WvIPPortAddr(const WvIPAddr&, short
unsigned int = 0)
wvaddr.h:372: WvIPPortAddr::WvIPPortAddr(const unsigned char*,
short unsigned int = 0)
wvaddr.cc:634: WvIPPortAddr::WvIPPortAddr()
make[2]: *** [wvaddr.o] Error 1
make[1]: *** [ipstreams] Error 2
make: *** [src] Error 2
|
I've also tried openssl-0.9.7.
Any help appreciated 
|
|
|
03-13-2003, 09:46 AM
|
#2
|
LQ Newbie
Registered: Nov 2002
Location: Houston, Texas
Distribution: LFS-4.0 and Mandrake 9.0
Posts: 7
Original Poster
Rep:
|
According to the wvstreams mail archive @ http://open.nit.ca/ gcc-2.95 must be used to successfully compile wvstreams. Is this what everyone is doing?
http://open.nit.ca/lists/archives/wv...v/threads.html
When having multiple gcc's, is it better to have version libs installed to the same dir, or installed to diff dir's?
Thanks!
|
|
|
03-13-2003, 11:13 AM
|
#3
|
Senior Member
Registered: Oct 2000
Location: UK - Frome
Distribution: Ubuntu
Posts: 1,081
Rep:
|
Can't help you with the Version libs question (try the BLFS Mailing list - sorry!).
As far as the wvstreams output is concerned is does appear to be some library mis-spelled, or not compatible with gcc-3.2 (which I assume you were using?). However, you may find patches for it to compile with 3.2 or as I think you are trying use an earlier version of gcc (best of luck with that!  ).
The BLFS mailing list should help though - try searching the previous posts there as I'm sure someone else would have come across your problem.
|
|
|
03-24-2003, 03:10 AM
|
#4
|
Member
Registered: Dec 2002
Posts: 35
Rep:
|
try this patch, it worked for me.
here is what i had installed
gcc-3.2.2
openssl-0.9.7a.tar.gz
then I patched wvstreams-3.70, it still put out a bunch of garbage while it was building but it worked.
http://linuxfromscratch.org/~billyoc...cc-3.2.1.patch
Last edited by starcrzr; 03-24-2003 at 03:46 AM.
|
|
|
All times are GMT -5. The time now is 12:14 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|