Open GoogleCodeExporter opened 9 years ago
Is the PATH_MAX declaration really the appropriate fix on HURD? I'm not keen
to try and present it to the gtest upstream owners as is.
Also, I'm trying to understand why it is necessary that the HURD get treated as
PLATFORM=linux vs. PLATFORM=unknown. Is it primariliy for the Java and Python
build pointers?
Original comment by fwarmerdam@gmail.com
on 30 Jan 2013 at 11:08
> Is the PATH_MAX declaration really the appropriate fix on HURD?
It's similar to what the gtest developers did, so this patch should stay local
for libkml until the next update of the gtest copy.
> Also, I'm trying to understand why it is necessary that the HURD get treated
as PLATFORM=linux vs. PLATFORM=unknown. Is it primariliy for the Java and
Python build pointers?
Yes, basically. I don't know how to eventually replace the two PLATFORM usages
with cross-platform ways (to get the Python library and the Java includes),
sorry. (But I can eventually test patches.)
Original comment by toscano....@tiscali.it
on 30 Jan 2013 at 11:33
I'm ok with this. I'm pursuing applying the patch...
Original comment by warmerdam@google.com
on 2 Apr 2013 at 11:35
Original comment by fwarmerdam@gmail.com
on 2 Apr 2013 at 11:38
Backed out internal patch pending a contribution assignment from the
contributor.
Original comment by fwarmerdam@gmail.com
on 16 Apr 2013 at 8:30
Original issue reported on code.google.com by
toscano....@tiscali.it
on 5 Oct 2012 at 1:41Attachments: