I just uninstalled Homebrew completely (I don't think I need it), deleted 
my old attempt at making Sage, restarted my laptop and started making Sage 
again. That did not help any, I still get exactly the same error.


On Wednesday, April 25, 2018 at 12:22:08 PM UTC-4, Samuel Lelievre wrote:
>
> Typically Homebrew installs stuff in /usr/local or /opt/local.
>
> Personally I have Homebrew installed, and I just get it out
> of the way when I build Sage, by doing
>
>     sudo mv /usr/local /usr/localbackup
>     sudo mv /opt/local /opt/localbackup
>
> and then when I'm done building Sage I revert that with
>
>     sudo mv /usr/localbackup /usr/local
>     sudo mv /opt/localbackup /opt/local
>
> To make my life easier I have aliases in my .bash_profile to
> - check which state things are in (local or localbackup),
> - rename "local" to "localbackup" in /opt and /usr
> - rename "localbackup" to "local" in /opt and /usr
>
> The aliases look like this:
> alias backuplocal='sudo mv /opt/local /opt/localbackup && sudo mv 
> /usr/local /usr/localbackup'
> alias restorelocal='sudo mv /opt/localbackup /opt/local && sudo mv 
> /usr/localbackup /usr/local'
> alias islocalthere='ls /opt | grep oca && ls /usr | grep oca'
>
>
> Le mercredi 25 avril 2018 14:05:13 UTC+2, Christelle Vincent a écrit :
>>
>> I do have Homebrew installed! Is there any way to stop it from seeing the 
>> wrong library? Can I uninstall Homebrew? I originally installed it at the 
>> suggestion of someone who was trying to help me fix a problem I had 
>> installing Sage 8.0 (which never worked by the way, I've been having these 
>> problems for a while...)
>>
>> On Wednesday, April 25, 2018 at 8:03:37 AM UTC-4, Dima Pasechnik wrote:
>>>
>>> I guess you have Homebrew/MacPorts/Anaconda installed, and a wrong 
>>> library is picked up from one of these.
>>>
>>>
>>> On Wednesday, April 25, 2018 at 1:49:19 PM UTC+3, Christelle Vincent 
>>> wrote:
>>>>
>>>> I upgraded through the Apple Developer website. I also did open Xcode 
>>>> again after the installation, but I can't remember if any additional 
>>>> components were installed.
>>>>
>>>> On Tuesday, April 24, 2018 at 1:23:01 PM UTC-4, John H Palmieri wrote:
>>>>>
>>>>> In my experience, it can help to run Xcode once after upgrading so 
>>>>> that it can install some "additional components". Did you re-install 
>>>>> command line tools by upgrading through the app store, or some other way?
>>>>>
>>>>>
>>>>> On Tuesday, April 24, 2018 at 8:57:30 AM UTC-7, Christelle Vincent 
>>>>> wrote:
>>>>>>
>>>>>> Hi,
>>>>>> I am trying to build Sage 8.1 from source on Mac (High Sierra 
>>>>>> 10.13.4, just updated Xcode and re-installed Command Line Tools).
>>>>>> I get the error "Error building package python3-3.6.1.p1"
>>>>>> I am attaching the whole log but it ends with
>>>>>> Undefined symbols for architecture x86_64:
>>>>>>   "_libintl_bindtextdomain", referenced from:
>>>>>>       _PyIntl_bindtextdomain in _localemodule.o
>>>>>>   "_libintl_dcgettext", referenced from:
>>>>>>       _PyIntl_dcgettext in _localemodule.o
>>>>>>   "_libintl_dgettext", referenced from:
>>>>>>       _PyIntl_dgettext in _localemodule.o
>>>>>>   "_libintl_gettext", referenced from:
>>>>>>       _PyIntl_gettext in _localemodule.o
>>>>>>   "_libintl_textdomain", referenced from:
>>>>>>       _PyIntl_textdomain in _localemodule.o
>>>>>> ld: symbol(s) not found for architecture x86_64
>>>>>> clang: error: linker command failed with exit code 1 (use -v to see 
>>>>>> invocation)
>>>>>> make[3]: *** [Programs/_freeze_importlib] Error 1
>>>>>> Error building Python.
>>>>>>
>>>>>> Anyone can help me fix this? Thanks!
>>>>>> Christelle
>>>>>>
>>>>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Reply via email to