Skip to content
This repository has been archived by the owner on Feb 7, 2023. It is now read-only.

hash_set deprecated #162

Closed
thatguymike opened this issue Feb 18, 2017 · 9 comments
Closed

hash_set deprecated #162

thatguymike opened this issue Feb 18, 2017 · 9 comments

Comments

@thatguymike
Copy link

From GCC deprecation page https://gcc.gnu.org/onlinedocs/libstdc++/manual/ext_sgi.html

<hash_map>
<hash_set>


<rb_tree>

Annoyingly, this is buried in glog but throws a lot of deprecation warnings during build. Not sure if we should just report to glog and silence the warning.

@Yangqing
Copy link
Contributor

T_T glog :(

I guess we can put an -W message to suppress it? What specific deprecation warning are we getting?

@Yangqing
Copy link
Contributor

Actually, it seems that glog already supports unordered_set instead of hash_set:

https://github.com/google/glog/blob/0472b91c5defdf90cff7292e3bf7bd86770a9a0a/src/glog/stl_logging.h.in#L41

Maybe this is due to the ubuntu apt-get package not properly compiled.

@slayton58
Copy link
Contributor

We could also move glog to a submodule and compile it ourselves to solve this - slightly heavy-handed though...

@Yangqing
Copy link
Contributor

Would you guys be fine with tolerating the warning message? :)

@pooyadavoodi
Copy link
Contributor

I would prefer to properly get rid of the warning messages only because they are so many (hundreds) and I always ignore them all. This way we can notice new warning messages which could save us from bugs :)
http://www.cprogramming.com/tutorial/compiler_warnings.html

@thatguymike
Copy link
Author

We can silence the warning for now.

@Yangqing
Copy link
Contributor

@thatguymike Mike - what is the build environment you use? I cannot repro on my 16.04 so I probably need a VM.

@thatguymike
Copy link
Author

14.04 fully updated

facebook-github-bot pushed a commit that referenced this issue Feb 27, 2017
Summary:
This addresses #162 for thatguymike
Closes #172

Differential Revision: D4620982

Pulled By: Yangqing

fbshipit-source-id: df3ef45f2c95418c538baa65d5dde3755cb25d1c
@Yangqing
Copy link
Contributor

Should have been fixed in #172 - feel free to reopen this @thatguymike :)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants