Skip to content
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

‘scm_timestamping’ does not name a type #2102

Open
Swthaochen opened this issue Nov 23, 2023 · 0 comments
Open

‘scm_timestamping’ does not name a type #2102

Swthaochen opened this issue Nov 23, 2023 · 0 comments

Comments

@Swthaochen
Copy link

I have some problems when build velox, it may be related with folly:

../folly/io/async/AsyncSocket.cpp:216:7: error: ‘scm_timestamping’ does not name a type; did you mean ‘SN_ad_timeStamping’?
  216 | const scm_timestamping* FOLLY_NULLABLE
      |       ^~~~~~~~~~~~~~~~
      |       SN_ad_timeStamping
../folly/io/async/AsyncSocket.cpp: In member function ‘folly::Optional<folly::AsyncTransport::ByteEvent> folly::AsyncSocket::ByteEventHelper::processCmsg(const cmsghdr&, size_t)’:
../folly/io/async/AsyncSocket.cpp:506:27: error: ‘cmsgToScmTimestamping’ was not declared in this scope
  506 |   } else if (auto scmTs = cmsgToScmTimestamping(cmsg)) {
      |                           ^~~~~~~~~~~~~~~~~~~~~
ninja: build stopped: subcommand failed.

so what's wrong with this ? I find someone have this error early too but until now does not have a solution.

@facebook facebook deleted a comment from rostech1793 Jun 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant