Summary: | sci-libs/hdf-4.2.8 fails to build with error local_nc.h:53:23: fatal error: rpc/types.h: File or directory not found | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Marco Clocchiatti <ziapannocchia> |
Component: | Current packages | Assignee: | Gentoo Science Related Packages <sci> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | jstein |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://bugs.gentoo.org/show_bug.cgi?id=630868 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
emerge --info
build.log libtirc.patch |
Description
Marco Clocchiatti
2018-04-08 23:08:53 UTC
Created attachment 526878 [details]
build.log
Created attachment 526880 [details, diff]
libtirc.patch
Hi Marco, thanks for the report. What is the difference between this bug and bug #630868? (In reply to Benda Xu from comment #3) > Hi Marco, thanks for the report. What is the difference between this bug > and bug #630868? they are independent at all. The problem is that the user having problems with the 4.2.8 hdf version can't simply upgrade to the ~ version, because of the second bug. p.s.: my libtirc.patch is a simplified version of the similar patch from the second bug. I' don't know if it is a well formed patch, because I'm not a developer, but it works for me. Hi Macro, (In reply to Marco Clocchiatti from comment #4) > (In reply to Benda Xu from comment #3) > > Hi Marco, thanks for the report. What is the difference between this bug > > and bug #630868? > > they are independent at all. > The problem is that the user having problems with the 4.2.8 hdf version > can't simply upgrade to the ~ version, because of the second bug. > > p.s.: my libtirc.patch is a simplified version of the similar patch from the > second bug. I' don't know if it is a well formed patch, because I'm not a > developer, but it works for me. Now I understand. Thank you! Let's wait for hdf-4.2.13-r1 to be stablized. *** This bug has been marked as a duplicate of bug 630868 *** |