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

autogen.sh not found? #364

Closed
rohmanhm opened this issue Sep 18, 2016 · 4 comments
Closed

autogen.sh not found? #364

rohmanhm opened this issue Sep 18, 2016 · 4 comments

Comments

@rohmanhm
Copy link

rohmanhm commented Sep 18, 2016

I using Bash on Ubuntu on Windows in Windows 10

When I run ./autogen.sh then show this error

RohmanHM@MHR-PC:/mnt/d/Hybrid/watchman$ ./autogen.sh
./autogen.sh: 9: ./autogen.sh: aclocal: not found
./autogen.sh: 10: ./autogen.sh: autoheader: not found
./autogen.sh: 11: ./autogen.sh: automake: not found
./autogen.sh: 12: ./autogen.sh: autoconf: not found
@wez
Copy link
Contributor

wez commented Sep 18, 2016

Please check the first paragraph of https://facebook.github.io/watchman/docs/install.html#installing-from-source
You need to install some development packages.

Since you are probably the first person to try this configuration, and because inotify running on windows is unproven, I'd recommend that you run make integration to run the integration tests to verify that inotify works.

Please let us know the outcome of this!

@rohmanhm
Copy link
Author

Wow, I have installed Watchman on my Windows PC with Bash on Ubuntu on Windows

root@MHR-PC:/mnt/d/Hybrid/watchman# watchman --help
Usage: watchman [opts] command

 -h, --help                 Show this help

     --inetd                Spawning from an inetd style supervisor

 -v, --version              Show version number

 -U, --sockname=PATH        Specify alternate sockname

 -o, --logfile=PATH         Specify path to logfile

     --log-level            set the log level (0 = off, default is 1, verbose = 2)

     --pidfile=PATH         Specify path to pidfile

 -p, --persistent           Persist and wait for further responses

 -n, --no-save-state        Don't save state between invocations

     --statefile=PATH       Specify path to file to hold watch and trigger state

 -j, --json-command         Instead of parsing CLI arguments, take a single json object from stdin

     --output-encoding=ARG  CLI output encoding. json (default) or bser

     --server-encoding=ARG  CLI<->server encoding. bser (default) or json

 -f, --foreground           Run the service in the foreground

     --no-pretty            Don't pretty print JSON

     --no-spawn             Don't try to start the service if it is not available

     --no-local             When no-spawn is enabled, don't try to handle request in client mode if service is unavailable


Available commands:

      clock
      debug-ageout
      debug-drop-privs
      debug-poison
      debug-recrawl
      debug-show-cursors
      find
      get-config
      get-pid
      get-sockname
      list-capabilities
      log
      log-level
      query
      shutdown-server
      since
      state-enter
      state-leave
      subscribe
      trigger
      trigger-del
      trigger-list
      unsubscribe
      version
      watch
      watch-del
      watch-del-all
      watch-list
      watch-project

See https://github.com/facebook/watchman#watchman for more help

Watchman, by Wez Furlong.
Copyright 2012-2015 Facebook, Inc.

@sunshowers
Copy link
Contributor

inotify doesn't currently work in that environment, so watchman isn't going to work either.

  • Siddharth

On Sun, Sep 18, 2016 at 3:52 PM -0700, "Muhammad Habib Rohman" <notifications@github.commailto:notifications@github.com> wrote:

Wow, I have installed Watchman on my Windows PC with Bash on Ubuntu on Windows

root@MHR-PC:/mnt/d/Hybrid/watchman# watchman --help
Usage: watchman [opts] command

-h, --help Show this help

 --inetd                Spawning from an inetd style supervisor

-v, --version Show version number

-U, --sockname=PATH Specify alternate sockname

-o, --logfile=PATH Specify path to logfile

 --log-level            set the log level (0 = off, default is 1, verbose = 2)

 --pidfile=PATH         Specify path to pidfile

-p, --persistent Persist and wait for further responses

-n, --no-save-state Don't save state between invocations

 --statefile=PATH       Specify path to file to hold watch and trigger state

-j, --json-command Instead of parsing CLI arguments, take a single json object from stdin

 --output-encoding=ARG  CLI output encoding. json (default) or bser

 --server-encoding=ARG  CLI<->server encoding. bser (default) or json

-f, --foreground Run the service in the foreground

 --no-pretty            Don't pretty print JSON

 --no-spawn             Don't try to start the service if it is not available

 --no-local             When no-spawn is enabled, don't try to handle request in client mode if service is unavailable

Available commands:

  clock
  debug-ageout
  debug-drop-privs
  debug-poison
  debug-recrawl
  debug-show-cursors
  find
  get-config
  get-pid
  get-sockname
  list-capabilities
  log
  log-level
  query
  shutdown-server
  since
  state-enter
  state-leave
  subscribe
  trigger
  trigger-del
  trigger-list
  unsubscribe
  version
  watch
  watch-del
  watch-del-all
  watch-list
  watch-project

See https://github.com/facebook/watchman#watchman for more help

Watchman, by Wez Furlong.
Copyright 2012-2015 Facebook, Inc.

You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com//issues/364#issuecomment-247886175, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AALBisBU6qbBGZUj7gHYWKSey2W1tpYdks5qrcCjgaJpZM4J_zCo.

@wez
Copy link
Contributor

wez commented Sep 20, 2016

I'm closing this out because it was a local environment issue. Per @Sid0's comment above, we don't expect watchman to function correctly in that environment, so you may want to switch to the real (alpha) watchman build for windows. More details on that can be found in #19

@wez wez closed this as completed Sep 20, 2016
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

3 participants