This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 6772 - strange behaviour of --enable-system-libwww
Summary: strange behaviour of --enable-system-libwww
Status: RESOLVED FIXED
Alias: None
Product: Amaya
Classification: Unclassified
Component: Building (show other bugs)
Version: 11.1
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: Vatton
QA Contact: Vatton
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-04 21:31 UTC by Guglielmo Saggiorato
Modified: 2009-06-23 15:02 UTC (History)
4 users (show)

See Also:

Attachments

Description Guglielmo Saggiorato 2009-04-04 21:31:29 UTC 
Hi, 

I noted that the --enable-system-libwww parameter of the configure doesn't work as told in the description. Precisely it doesn't _try_ to use the system lib, but simply checks if its available system wide, in case it's not, it neither stops the configure, neither falls back to the amaya's own copy of the library.

So the compilation fails when compiling code depending upon this library.

In may case, debian squeeze amd64, I've not yet that library but I activated that flag because I wasn't sure of that. So compilation failed until I understood this thing and removed that flag.

(I hope my english is not too bad)
Comment 1 Vatton 2009-06-23 15:02:48 UTC 
(In reply to comment #0)
> Hi, 
> 
> I noted that the --enable-system-libwww parameter of the configure doesn't work
> as told in the description. Precisely it doesn't _try_ to use the system lib,
> but simply checks if its available system wide, in case it's not, it neither
> stops the configure, neither falls back to the amaya's own copy of the library.
> 
> So the compilation fails when compiling code depending upon this library.
> 
> In may case, debian squeeze amd64, I've not yet that library but I activated
> that flag because I wasn't sure of that. So compilation failed until I
> understood this thing and removed that flag.
> 
> (I hope my english is not too bad)
> 

I guess the problem is fixed now.