As you can imagine, there is no way to tell what exactly is going on
from your "it breaking something or the other".

We also need logs/install.log to see the actual errors.

On Tue, Mar 31, 2026 at 9:45 AM Aatman Supkar <[email protected]> wrote:
>
> The build form source guides are helpful to some extent (I have tried both at 
> some point), but I also find it breaking something or the other everytime. 
> Just to be sure, I tried it again, after following the readme to the best of 
> my ability (I don't know how to set the config variables, although I did make 
> a rather clean PATH this time).
>
> I'll attach a config.log if you can help me find the exact problem.
>
> I'm using a MacOS 15.7.5, and am currently using Homebrew. But I have also 
> been trying to abandon Homebrew and shift to Nix, so builds using that would 
> be much appreciated.
>
> On Tuesday, March 31, 2026 at 5:30:27 PM UTC+5:30 [email protected] wrote:
>>
>> This documentation has more detailed instructions about building without 
>> conda.
>> https://doc.sagemath.org/html/en/installation/source-distro.html
>>
>> What OS are you building Sage on?
>>
>> On Monday, March 30, 2026 at 9:19:14 PM UTC+9 [email protected] wrote:
>>>
>>> I want to set up Sage for development, but I don't want to use Conda due to 
>>> its system-wide installs. What all methods for building Sage currently 
>>> exist?
>>>
> --
> 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 [email protected].
> To view this discussion visit 
> https://groups.google.com/d/msgid/sage-devel/7e872d99-fbc3-47ab-971e-4fbc2158bd9cn%40googlegroups.com.

-- 
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 [email protected].
To view this discussion visit 
https://groups.google.com/d/msgid/sage-devel/CAAWYfq2NryPhj0m6W9NKhoeqOw34aALvjVjuLp0su_6cz6ATYQ%40mail.gmail.com.

Reply via email to