Configure error macport - mkvToolnix
ryandesign at macports.org
Wed Sep 24 14:28:39 PDT 2008
On Sep 24, 2008, at 16:06, Mine wrote:
> On 24 Sep 2008, at 04:31, Ryan Schmidt wrote:
>> Please remember to Reply All so your reply goes to the list too,
>> not just to me.
>> On Sep 23, 2008, at 8:03 PM, Mine wrote:
>>> Hi Ryan,
>>> I have stuff in /usr/local which are apps installed by macPorts
>> MacPorts installs in /opt/local by default, not /usr/local. Things
>> installed in /usr/local can interfere with MacPorts. Using /usr/
>> local as your MacPorts prefix is not supported.
>>> and I also have stuff in /sw apps installed by Fink. Although the
>>> Fink doc state that because it installs its files in /sw it does not
>>> interfere with other apps.
>> I don't care what the Fink docs say. :) Items installed in /sw
>> and /usr/local can interfere with software that MacPorts wants to
>> install. It is not supported to have two different package
>> managers installed. That means it may work for you but I won't
>> help you with it. :)
>>> I am a little nervous about disabling thing as I am new at this
>>> and I don't want to screw up my system or the other apps I
>>> have managed to install which is not yet backed up.
>> Move /sw and /usr/local out of the way by renaming them to /sw-off
>> and /usr/local-off. Then try again. If things now work, you'll
>> know /sw or /usr/local interfered.
>> You can always rename them back to /sw and /usr/local temporarily
>> while you need to use what's in there, but your long term solution
>> is to install all that software with MacPorts, then get rid of /sw
>> and /usr/local.
>>> I have uninstalled and re-installed boost.
>>> As stated in your email I did the following:
>>> My-Computer:~ tw2$ sudo port deactivate boost
>>> ---> Deactivating boost
>>> My-Computer:~ tw2$ sudo port clean --work boost
>>> ---> Cleaning boost
>>> My-Computer:~ tw2$ sudo port configure boost
>>> My-Computer:~ tw2$ open $(port dir boost)
>>> My-Computer:~ tw2$
>>> The first time I did this, I was able to open a work
>>> directory and I have attached it to a separate email.
>>> However, out of curiosity, I opened the file as it
>>> did not have config in its name but the file only
>>> contained two words 'variant: +darwin'.
>>> I assumed that I had made an error so I reactivated
>>> boost and tried again but each time I try, the work
>>> directory is now an alias that I can't open.
>> Sorry; I gave incorrect instructions. It seems that because the
>> boost port was still installed (though deactivated), "port
>> configure" did nothing, hence there was nothing in the work
>> directory. (The work directory is, by the way, always an alias to
>> another location.)
>> Uninstall boost instead of deactivating it. Then "port configure"
>> should actually configure, and then you can find the config.log
>> and attach it.
>>> While I was re-installing boost I saw the following
>>> appear in the Terminal:
>>> Building Boost.Regex with the optional Unicode/ICU support disabled.
>>> Please refer to the Boost.Regex documentation for more information
>>> (don't panic: this is a strictly optional feature).
>>> I don't know if this has anything to do with the error I have
>>> been getting
>>> 'configure: error: Could not link against boost_regex-boost_regex-
>>> mt !'
>>> when trying to install mkvToolnix. I did have a look at the
>>> documentation but the info 'Building with Unicode and ICU
>>> Support' and
>>> other thing mentioned, is way beyond me.
>> I don't know the significance of that message. I'm not really
>> familiar with boost.
>> Tomorrow I'll try configuring it again on my system and see if it
>> says the same thing.
> I have (sudo mv /sw /sw-off, sudo mv /usr/local /usr/local-off)
> both sets of directories,
> configured boost and sent you the configure file. I assume you
> didn't want me to
> send the config file to the list so I just sent it to you. I have
> not installed boost yet
> just in case there are any changes to be made before installing.
You sent me the configure script, but I already have that. :) I need
the output the configure script produces when run on your system.
That's the config.log file.
More information about the macports-users