Skip to content

Commit

Permalink
Fix FreeBSD build by adding new libuv file to Makefile.in
Browse files Browse the repository at this point in the history
FreeBSD build broke after bumping libuv. Add the new file to Makefile.in
  • Loading branch information
samcv committed Sep 18, 2017
1 parent 2824dcf commit dfbf9df
Showing 1 changed file with 2 additions and 1 deletion.
3 changes: 2 additions & 1 deletion build/Makefile.in
Expand Up @@ -402,7 +402,8 @@ UV_UNIX = 3rdparty/libuv/src/fs-poll@obj@ \
3rdparty/libuv/src/threadpool@obj@ \
3rdparty/libuv/src/unix/timer@obj@ \
3rdparty/libuv/src/unix/tty@obj@ \
3rdparty/libuv/src/unix/udp@obj@
3rdparty/libuv/src/unix/udp@obj@ \
3rdparty/libuv/src/unix/posix-hrtime.c

UV_LINUX = 3rdparty/libuv/src/unix/linux-core@obj@ \
3rdparty/libuv/src/unix/linux-inotify@obj@ \
Expand Down

3 comments on commit dfbf9df

@usev6
Copy link
Contributor

@usev6 usev6 commented on dfbf9df Sep 19, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh, I just stumbled about this problem when building Rakudo and wanted to suggest a similiar fix.

Ooc, is there a deeper reason why you added 'posix-hrtime.c' instead of 'posix-hrtime@obj@'?

@samcv
Copy link
Member Author

@samcv samcv commented on dfbf9df Sep 19, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It was an accident actually. Did @obj@ on my FreeBSD test machine and accidentally did .c on my work machine which I pushed from.

@usev6
Copy link
Contributor

@usev6 usev6 commented on dfbf9df Sep 19, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see. I figured something like that and opened a PR to fix it (merged now, commit 5bdb778).

Please sign in to comment.