On Wednesday, March 31, 2021 at 2:53:22 PM UTC-7 [email protected] wrote:

> with rc0 and rc1, I have a real problem on all three macOS systems of mine 
> (10.13.6, 10.14.6 and 10.15.7): the build proceeds a while, and then blows 
> up on pynac. The log for this build, and the config.log, are attached (and 
> I do not use any package managers). 
>
> One possibly odd thing is this line near the end of the pynac log: 
> ld: can't map file, errno=22 file '/Users/Sage/sage-9.3.rc1/local/lib' for 
> architecture x86_64


>From pynac.log:

/bin/bash ../libtool  --tag=CXX   --mode=link g++ -std=gnu++11 -std=c++11  
-O2 -g -O2 -g -march=native -version-info 21:5:3 
-L/Users/Sage/sage-9.3.rc0/local/lib 
-Wl,-rpath,/Users/Sage/sage-9.3.rc0/local/lib  -o libpynac.la -rpath 
/Users/Sage/sage-9.3.rc0/local/lib libpynac_la-add.lo [...] 
libpynac_la-useries.lo -bundle -undefined dynamic_lookup 
-L/Users/Sage/sage-9.3.rc0/local/lib 
-Wl,-rpath,/Users/Sage/sage-9.3.rc0/local/lib -L. 
-L/Users/Sage/sage-9.3.rc0/local/lib 
-Wl,-rpath,/Users/Sage/sage-9.3.rc0/local/lib 
-L/Users/Sage/sage-9.3.rc0/local/lib 
-Wl,-rpath,/Users/Sage/sage-9.3.rc0/local/lib -O2 -g -march=native -lflint 
-lgmp  -lfactory -Wl,/Users/Sage/sage-9.3.rc0/local/lib -lflint -lmpfr 
-lntl -L/usr/local/lib *-Wl,-rpath -Wl,/usr/local/lib* -lgmp -lomalloc 
-L/Users/Sage/sage-9.3.rc0/local/lib -lsingular_resources    -lflint -lgmp 

Note the "*-Wl,-rpath -Wl,/usr/local/lib" *- which gets reordered by 
libtool in the next line to something that causes the error.
Correct would be "*-Wl,-rpath,/usr/local/lib".* It would be worth checking 
whether this is coming in from some environment variables that you may have 
set.

>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/3e4472e7-e829-449f-8608-6d87e2c9e0dfn%40googlegroups.com.

Reply via email to