-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Warnings when installing RQuantLib 0.4.4 from source on OSX #99
Comments
Can you try to format it as code? Right now it is unreadable. See the Styling with Markdown is support link at bottom left of each edit box. Edit: Did it for you by now. |
I think the fix would be for macOS to not be stupid and ignore case. |
On Dec 30, 2017, at 2:28 PM, Dirk Eddelbuettel ***@***.***> wrote:
I think the fix would be for macOS to not be stupid and ignore case. RQuantLib.h is the filename, just as it is Rcpp.h. Surely there must be a flag you could use in your ~/.R/Makevars to turn the warning off?
Huh. I thought Linux was also case sensitive in it filesystem. Live and learn I guess. Sorry for the noise. I'll report back if I find a switch to shut off that warning.
|
On Dec 30, 2017, at 4:29 PM, David Winsemius ***@***.***> wrote:
> On Dec 30, 2017, at 2:28 PM, Dirk Eddelbuettel ***@***.***> wrote:
>
> I think the fix would be for macOS to not be stupid and ignore case. RQuantLib.h is the filename, just as it is Rcpp.h. Surely there must be a flag you could use in your ~/.R/Makevars to turn the warning off?
>
Huh. I thought Linux was also case sensitive in it filesystem. Live and learn I guess. Sorry for the noise. I'll report back if I find a switch to shut off that warning.
One of the reasons I _thought_ that Linux was case-sensitive was this quote of yours regarding OSX: "... (who ever thought case-insensitive filesystems where a good idea?)"
So I thought I had it on excellent authority that the converse .... case-sensitivity was a ... "good idea".
--(From this months http://dirk.eddelbuettel.com/blog/)
|
Sorry, I was out with the family for a bit. At the same, @joshuaulrich and I were exchanging Slack messages regarding RQuantLib while he is trying to build/update the Windows -- and he reminded me that I do in fact have In the meantime, you could try renaming one of the two headers differing only in case and see if it helps. I don't use or own a macOS machine so I am unaffected (as is seemingly @tleitch who happily contributed to RQuantLib using a macOS box...) |
Yes, a quick recursive grep (or, rathre,
|
Also from #ifndef rquantlib_src_h
#define rquantlib_src_h
// Rcpp Attributes requires a file with package name in inst/include,
// in our case inst/include/RQuantLib.h -- but R does not want us to have
// another header file with the same name, differing only by case
//
// So we place the existing 'rquantlib.h' in src/ instead so that the
// issue of equal names (for everything but the case) no longer
// matters. This provides us with a backwards compatible
// 'rquantlib.h' file, and its definitons are now in a file
// inst/include/rquantlib_internal.h which we source here.
#include "rquantlib_internal.h"
#endif so the Can you let me know if that helps? |
I wasn't actually having any difficulty. (The only difficulty I had was in getting rgl to load to run the demo, and I solved that.) They were only a warnings and I get those reasonably often when compiling from source. Because OSX seems to be a distinct minority of RQuantLib users and Apple keeps changing the rules, and C compilers, I thought it might be useful to let you know about warnings before some future revision of the rules turned into errors. Thanks, David. |
Oh, you have no idea -- there were dozens of emails from folks stranded on macOS / OS X. We do have a somewhat current entry in the wiki that describes it. Many folks just seem to get lost picking compilers and the like. That is not for everyone. But I can't rely on Simon to always build binaries, just how Uwe stopped providing them for Windows. I saw the mostly-wrong / mostly-ill-informed thread on r-help today but I didn't have sufficient spare time to get involved. Anyway -- glad to hear you got sorted out. |
So I presume we can close this then if these were just line-noise warnings? |
Oh yes. If there’s anything I can do now that I have a working RQuantLib installation I’d be willing to try. However as you can tell I’m not highly proficient with NIX commands.
—
David
…Sent from my iPhone
On Dec 30, 2017, at 7:09 PM, Dirk Eddelbuettel ***@***.***> wrote:
So I presume we can close this then if these were just line-noise warnings?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
You could probably help just by going over the wiki entry about installing and checking / updating / complementing the macOS portion. Or maybe branch off a new one depending on how big a chance is needed. Otherwise, I'll close this. And I am working on moving |
For what it is worth, #100 now deprecated |
I installed boost using homebrew and installed QuantLib 1.11 from source using instructions from their website. (Admittedly I probably should have used homebrew to this as well but didn't find those instructions until later.) Initially I failed to include the --enable-intraday argument to ./configure but after failing to load RQuantLib, I went back and added that and am waiting for the rebuild to complete. At any rate I got 12 warnings like this one during compilation of RQuantLib from the console. Seems likely that these warnings would also have occurred if compiled from Terminal session:
Seems that a simple fix would be to rename that file "rquantlib.h"?
The text was updated successfully, but these errors were encountered: