Created attachment 153742 [details] script(1) session log of sysutils/cdrtools All attempts to build this on a recent 11: FreeBSD dev.box 11.0-CURRENT FreeBSD 11.0-CURRENT #1 r279289: Wed Feb 25 15:17:13 PST 2015 root@dev.box:/usr/obj/usr/src/sys/DEVBOX amd64 result in several messages to syslog: Mar 3 13:34:38 dev kernel: pid 74677 (cc), exited on signal 6 (core dumped) Mar 3 13:34:39 dev kernel: pid 74685 (cc), exited on signal 6 (core dumped) Mar 3 13:34:39 dev kernel: pid 74715 (cc), exited on signal 6 (core dumped) Mar 3 13:34:40 dev kernel: pid 74745 (cc), exited on signal 6 (core dumped) Options selected for the port: OPTIONS_FILE_SET+=CDDA2MP3 OPTIONS_FILE_SET+=CDDA2OGG OPTIONS_FILE_SET+=DOCS OPTIONS_FILE_SET+=NLS OPTIONS_FILE_UNSET+=RSCSI NOTE: also attempted the build with only the default options selected. But same results. Not sure how to resolve this. But am attaching a script(1) session, in hopes someone can fix this. Thanks! --Chris
Closer examination reveals that the majority of the issues are caused by virtue of the fact that the source seems to have *mixed* encoding. I'm going to make an attempt to convert the source to utf-8, and provide a *mega* diff against the entire [source] tree. --Chris
Whew! Well, I went through the contents of the entire archive, by hand, and converted all files that were not already UTF-8 encoded, to UTF-8. I'll inform upstream of the conversion, and provide a link, if their interested in using it. In the meantime, if your interested. Feel free to use the following link, for the source: http://BSDforge.com/projects/source/sysutils/cdrtools-3.00-utf-8.tar.xz I may also put a copy in my GH repo. But this link will be valid for the foreseeable future. HTH --Chris
Created attachment 153753 [details] script session LOG for sysutils/cdrtools - after UTF-8 conversion OK I've attempted another make of cdrtools, after converting the archive's source to UTF-8. While it didn't eliminate the dump core issues reported. It *did* eliminate a large amount of errors. Please find the script(1) session LOG attached for greater details. Thanks! OH I moved the archive. Please find it at: http://BSDforge.com/projects/source/sysutils/cdrtools-3.00-utf-8/cdrtools-3.00.tar.xz Thanks again! --Chris
(In reply to Chris Hutchinson from comment #3) > Created attachment 153753 [details] > script session LOG for sysutils/cdrtools - after UTF-8 conversion > > OK I've attempted another make of cdrtools, after > converting the archive's source to UTF-8. > While it didn't eliminate the dump core issues reported. > It *did* eliminate a large amount of errors. > > Please find the script(1) session LOG attached for > greater details. > > Thanks! > > OH I moved the archive. Please find it at: > http://BSDforge.com/projects/source/sysutils/cdrtools-3.00-utf-8/cdrtools-3. > 00.tar.xz > > Thanks again! > > --Chris OK Spoke to Jörg Schilling, and his response was that this version was too old, and not compatible with any recent(ish) versions of clang. So, noticing that sysutils/cdrtools-devel was more recent, I gave it a try. Which resulted in only one instance of dev kernel: pid 7231 (cc), : exited on signal 6 (core dumped) but also emitted a number of complaints regarding the foreign characters: find_main.c:177:57: warning: illegal character encoding in string literal [-Winvalid-source-encoding] "sfind release %s (%s-%s-%s) Copyright (C) 2004-2010 J<F6>rg Schilling\n", ^~~~ Converting the offending source files from ISO-8859-1 to UTF-8, removes these errors. But I still have no idea what causes the "core dumped" problem. Hope this helps. --Chris
*** Bug 198287 has been marked as a duplicate of this bug. ***
Recent version 3.01 compiles fine, and I think this PR is surely overcome by events.
Agreed. --Chris