search

epitzer / sparsehash

Automatically exported from code.google.com/p/sparsehash
BSD 3-Clause "New" or "Revised" License
0 stars 0 forks source link

Fix build for VOS: # not allowed in filenames #41

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
Hello Project Owner
Actually I Am Trying To Submit A Post. Couldnt Find Any Other Way To 
Contact. How Do I Submit It?

Original issue reported on code.google.com by bornlibr...@gmail.com on 8 Jun 2009 at 4:12

GoogleCodeExporter commented 8 years ago 
Can you clarify: are you trying to submit a port, or a post?  If it's a port, 
just
put it here: you can attach the diff as a file.  If it's a post, you can send 
it to
google-sparsehash@googlegroups.com.

Original comment by csilv...@gmail.com on 8 Jun 2009 at 7:33

GoogleCodeExporter commented 8 years ago 
It is a port to Stratus VOS operating system. Sorry for the typo. I dont know 
how to 
diff files so I will just tell the files & how to identify the change.
hashtable_unittest.cc : Search for __VOS__
sparsetable_unittest.cc: Search for __VOS__
Both these locations assume that # is a allowed character in the file name but 
on 
VOS it isnt. Can configure check for such characters?
Thanks
Ashutosh Warikoo

Original comment by bornlibr...@gmail.com on 11 Jun 2009 at 6:46

Attachments:

GoogleCodeExporter commented 8 years ago 
No problem -- I'll just replace the # for everyone.  It's not really needed.

Original comment by csilv...@gmail.com on 12 Jun 2009 at 3:28

GoogleCodeExporter commented 8 years ago

Original comment by csilv...@gmail.com on 12 Jun 2009 at 3:28

GoogleCodeExporter commented 8 years ago 
This should be resolved in sparsehash 1.6, just released.

Original comment by csilv...@gmail.com on 11 Jan 2010 at 10:53