From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chip Olson To: Source-Navigator Subject: [Fwd: Re: Building on FreeBSD 3.2] Date: Fri, 10 Nov 2000 14:19:00 -0000 Message-id: <3A0C7464.7A306A15@shore.net> X-SW-Source: 2000-q4/msg00210.html Ben Elliston wrote: > Why are you trying to use the Linux compatibility? Why not try and compile > the whole package to run natively on FreeBSD? If that's the case, where do > you normally link dl_open() from? Why, that's an excellent idea. (The answer to your question is "because I don't know what part of this is Linux-specific and what isn't"). As it turns out, dlopen() in FreeBSD is in libc rather than in its own library, so I took the -ldl off of the line in the config script. Now it doesn't complain about that when I run configure, but I'm still getting the same error when I try to build, and a check of config.log reveals a number of similar issues (i.e. trying to link in libraries that don't exist in FreeBSD). I'd think that, if this is a standard Tcl distribution, it'd be set up to deal with FreeBSD as well as Linux, so I'm not quite sure what's going on here. At this point, I'm not sure if the issue lies with SN, the 3rd-party modules it includes, FreeBSD, or my setup. But I *MASSIVELY* appreciate everyone's help. -- -Chip Olson. | ceo at shore dot net "You ask me why we celebrate, when nothing has been won; We take dark hours, we make them great, that's all we've ever done..." -Oysterband, "This Is The Voice".