-
Notifications
You must be signed in to change notification settings - Fork 130
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
tibble
3.2.1.9017: some errors in running vignette code
#1575
Comments
Thanks. Does The errors in the vignette code are meant to be caught. Can we run the check without |
Unfortunately, it uses Pandoc for vignettes, so if I drop that argument, it just fails completely:
|
What is the problem with using Pandoc? |
Can we make that a build requirement? |
Please don’t, it will break it for all systems where Pandoc is broken. That is completely unnecessary. |
It depends on GHC, and that too a very recent GHC. So wherever GHC does not work, Pandoc won’t build. |
Thanks, Sergey. It's tricky -- pandoc is universal on all platforms that matter in practice (that is, for the vast majority of users). I hear it for the first time that installing pandoc may be difficult on some platforms. Unfortunately, I can't prioritize fixing this particular use case, but I'm open to reviewing a pull request. |
IIUC, fixing the Haskell compiler where it's broken allows us to pull in pandoc? |
@krlmlr As long as it is optional, there is no problem, I was just explaining why we have to disable building vignettes: on newer systems it is an unwanted heavy dependency, on older systems it does not build at all. (Well, it might be possible to build some old version of Pandoc on ppc, but it may not be trivial, requires time and in result it may or may not work for a given aim, nobody knows.) |
So, the problem is that newer GHC doesn't work for older platforms? Is this fixable upstream? To properly support TeX doesn't create HTML. |
If you mean whether GHC upstream is going to fix anything on their end, then no, AFAIK. If you rather mean whether they accept a fix if I do it, then possibly yes. Generally speaking, it is non-trivial to fix languages which can only be built by themselves. So we got Rust, GHC and Go broken indefinitely. The last GHC for ppc was 7.0.4. I have fixed 7.6.3, but anything later either failed to build or refused to (it requires a relatively recent version, so using an archaic one to build the current like with SBCL does not work here). Upstream suggested to fix the code in the current GHC and cross-compile it from Intel. Well, that is perhaps doable, but I have no experience with cross-compiling things and Macports does not have functionality for it, so it will need a lot of time to sort it out. Plus restoring code for ppc is not straightforward, since GHC sources changed quite a bit. Very likely, just restoring and fixing SDK issues will not suffice, and something will be needed to reimplement in assembler.
A lot of work for this will be impractical, of course. (And just in case, there is no need to bother with finding a way to build html documentation for systems without Pandoc, users can certainly live without html docs offline.)
Ok, fair point. But is html documentation a strictly required thing for tests? Let it be generated by default (so no one suffers because of a few users with ppc, mips and older x86), but if there will be an option to turn it off, that will be nice, perhaps. |
All valid points. All I'm saying is that I can't spend time on the implementation. If anyone wants to chime in, happy to review. I see failures consistent with your report when I check with |
@krlmlr Thank you very much for verifying that! It is very helpful.
Yes, I may return to this. |
Just wanna tag this issue here Which is the same: failing the building of vignettes that have |
Unfortunately, rebuilding
|
Thanks for the heads-up. Should we add |
@krlmlr At least that's what I did. |
Tests pass fine, but I get some errors in running vignette code:
Could this be addressed?
tibble
is a foundational package, it would be great to have it working without issues, however minor.The text was updated successfully, but these errors were encountered: