On Jul 16, 2008, at 11:28 PM, Jean-François Mertens wrote: > > On 16 Jul 2008, at 21:25, Jean-François Mertens wrote: > >> I remember from previous versions of swig that one did not have to >> have all (or even : any...) of those languages installed to build a >> fully-enabled swig; >> configure was just testing them, and at worst it might affect e.g. >> the build of >> some example files.. >> Might be worth to investigate whether this is no longer true, before >> changing >> a number of other pkgs. >> >> Jean-Francois > > > Just re-built it; there is still the note, in the middle of configure > output : > "Note : None of the following packages are required to compile SWIG" > ...
I believe you are correct. I tried building swig 1.3.35 when it first came out in hopes of stomping on the octave issue early, but I couldn't convince myself the core package didn't change at all when the various supported languages were present or absent. The really strange thing was that it seemed to me that the packages installed (at least by name and size) were nearly identical whether swig was configured --without-alllang or with all of the languages in place. There may be an issue with non-standard directory structures (guile, for example). I seem to recall a problem getting swig to build correctly without configuring it to find the right guile subdirectories. But my memory of that is fuzzy enough it could have just been my misunderstanding at that point. Dave -- David Reiser [EMAIL PROTECTED] ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Fink-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fink-users
