[#83773] [Ruby trunk Bug#14108] Seg Fault with MinGW on svn 60769 — usa@...
Issue #14108 has been updated by usa (Usaku NAKAMURA).
9 messages
2017/11/15
[#83774] Re: [Ruby trunk Bug#14108] Seg Fault with MinGW on svn 60769
— Eric Wong <normalperson@...>
2017/11/15
usa@garbagecollect.jp wrote:
[#83775] Re: [Ruby trunk Bug#14108] Seg Fault with MinGW on svn 60769
— "U.NAKAMURA" <usa@...>
2017/11/15
Hi, Eric
[#83779] Re: [Ruby trunk Bug#14108] Seg Fault with MinGW on svn 60769
— Eric Wong <normalperson@...>
2017/11/15
"U.NAKAMURA" <usa@garbagecollect.jp> wrote:
[#83781] Re: [Ruby trunk Bug#14108] Seg Fault with MinGW on svn 60769
— "U.NAKAMURA" <usa@...>
2017/11/15
Hi, Eric,
[#83782] Re: [Ruby trunk Bug#14108] Seg Fault with MinGW on svn 60769
— Eric Wong <normalperson@...>
2017/11/15
"U.NAKAMURA" <usa@garbagecollect.jp> wrote:
[ruby-core:83714] [Ruby trunk Bug#14089][Feedback] Configure/build issue on OSX 10.12 w/ utimensat
From:
hsbt@...
Date:
2017-11-10 03:32:34 UTC
List:
ruby-core #83714
Issue #14089 has been updated by hsbt (Hiroshi SHIBATA).
Status changed from Open to Feedback
Hi, Can you try patch of https://github.com/rbenv/ruby-build/issues/1133#issuecomment-331332963 with your environment?
----------------------------------------
Bug #14089: Configure/build issue on OSX 10.12 w/ utimensat
https://bugs.ruby-lang.org/issues/14089#change-67737
* Author: zenspider (Ryan Davis)
* Status: Feedback
* Priority: Normal
* Assignee:
* Target version:
* ruby -v:
* Backport: 2.3: UNKNOWN, 2.4: UNKNOWN
----------------------------------------
For other reasons I recently installed xcode (instead of JUST using the command line developer tools). This caused builds on ruby to break.
The symptom happens when rdoc tries to build the doco:
~~~
dyld: lazy symbol binding failed: Symbol not found: _utimensat
~~~
You can see this in the build output:
~~~
file.c:2580:13: warning: 'utimensat' is only available on macOS 10.13 or newer
[-Wunguarded-availability-new]
if (utimensat(AT_FDCWD, path, tsp, 0) < 0) {
^~~~~~~~~
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.13.sdk/usr/include/sys/stat.h:374:5: note:
'utimensat' has been explicitly marked partial here
int utimensat(int __fd, const char *__path, const struct timespec __...
^
file.c:2580:13: note: enclose 'utimensat' in a __builtin_available check to
silence this warning
if (utimensat(AT_FDCWD, path, tsp, 0) < 0) {
^~~~~~~~~
~~~
and the clue is that path to `MacOSX10.13.sdk`. The Xcode.app doesn't ship with 10.12, but the developer tools do. It is fixed with:
~~~
$ sudo xcode-select --switch /Library/Developer/CommandLineTools
~~~
This is here mostly for documentation / search purposes... but maybe we could do something to improve the situation by figuring out that it is being linked against the wrong SDK version?
--
https://bugs.ruby-lang.org/
Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>