Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upUnable to run 'make' on Fedora Distro #370
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
rade
Jan 27, 2015
Member
The other issue was the absence of the static libs for libpthread and libc. This was fixed by installing glibc-static.
|
The other issue was the absence of the static libs for libpthread and libc. This was fixed by installing glibc-static. |
rade
added
the
chore
label
Jan 28, 2015
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
We should update our docs |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
rade
Jan 29, 2015
Member
@dpw iirc you mentioned that you ran into a bunch of problems building weave on Fedora. Anything other than the above?
|
@dpw iirc you mentioned that you ran into a bunch of problems building weave on Fedora. Anything other than the above? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
dpw
Jan 29, 2015
Contributor
I'm not sure.
But we shouldn't be recommending that people install non-distro libs into system-wide locations, because then we risk breaking stuff for them. Which means you need to set the appropriate environment variables to 'go build' to make it use the alternate libpcap and associated header file.
If we are going to document how to build under other distros, it might be better simply to recommend building in a debian/ubuntu container.
|
I'm not sure. But we shouldn't be recommending that people install non-distro libs into system-wide locations, because then we risk breaking stuff for them. Which means you need to set the appropriate environment variables to 'go build' to make it use the alternate libpcap and associated header file. If we are going to document how to build under other distros, it might be better simply to recommend building in a debian/ubuntu container. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
rade
Jan 29, 2015
Member
If we are going to document how to build under other distros, it might be better simply to recommend building in a debian/ubuntu container.
Well, we already have the vagrant instructions.
Perhaps we just need to tweak the docs in some other way, e.g. put the vagrant section first.
Well, we already have the vagrant instructions. Perhaps we just need to tweak the docs in some other way, e.g. put the vagrant section first. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
aanm
Jan 29, 2015
@dpw
If I may, and in my humble opinion, one of the points of weave's favor should be to have docker networking running on multiple hosts. That multi architecture structure should allow weave to run on different distros and not only on debian/ubuntu. I think it's better to fix those issues now than in the future when it could probably be irreversible.
@rade
Yes, I think it would probably be better to have the "easy" mode first and then distros related.
aanm
commented
Jan 29, 2015
|
@dpw @rade |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
@aanm you don't need to build weave in order to run it. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
aanm
commented
Jan 29, 2015
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
dpw
Jan 29, 2015
Contributor
Well, we already have the vagrant instructions.
Perhaps we just need to tweak the docs in some other way, e.g. put the vagrant section first.
Haven't you heard my opinion of vagrant? Or are you just teasing?
What's wrong with recommending building in a container?
Haven't you heard my opinion of vagrant? Or are you just teasing? What's wrong with recommending building in a container? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
rade
Jan 29, 2015
Member
What's wrong with recommending building in a container?
Nothing. But somebody would actually have to make that work and document it.
Nothing. But somebody would actually have to make that work and document it. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
aanm
Jan 29, 2015
I thought you were talking about using weave (as release) inside vagrant and not building it
aanm
commented
Jan 29, 2015
|
I thought you were talking about using weave (as release) inside vagrant and not building it |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
dpw
Feb 2, 2015
Contributor
@dpw iirc you mentioned that you ran into a bunch of problems building weave on Fedora. Anything other than the above?
I suspect that the WEAVETOOLS_EXES build step doesn't work under fedora with selinux enabled (due to the use of the docker run -v option).
I suspect that the WEAVETOOLS_EXES build step doesn't work under fedora with selinux enabled (due to the use of the |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
This has been superseded by #387. |
aanm commentedJan 27, 2015
Hi,
I was unable to run 'make' on Fedora.
It returned:
/bin/ld: cannot find -lpcap
Although there's a libpcap-devel package, it doesn't provide the "libpcap.a".
To fix it, you just have to build it from libpcap.a from sources (http://www.tcpdump.org/release/).
And copy it to /usr/lib/libpcap.a