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

Unable to run 'make' on Fedora Distro #370

Closed
aanm opened this Issue Jan 27, 2015 · 13 comments

Comments

Projects
None yet
3 participants
@aanm

aanm commented Jan 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

@rade

This comment has been minimized.

Show comment
Hide comment
@rade

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.

Member

rade commented Jan 27, 2015

The other issue was the absence of the static libs for libpthread and libc. This was fixed by installing glibc-static.

@rade rade added the chore label Jan 28, 2015

@rade

This comment has been minimized.

Show comment
Hide comment
@rade

rade Jan 28, 2015

Member

We should update our docs

Member

rade commented Jan 28, 2015

We should update our docs

@rade

This comment has been minimized.

Show comment
Hide comment
@rade

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?

Member

rade commented Jan 29, 2015

@dpw iirc you mentioned that you ran into a bunch of problems building weave on Fedora. Anything other than the above?

@dpw

This comment has been minimized.

Show comment
Hide comment
@dpw

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.

Contributor

dpw commented Jan 29, 2015

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.

@rade

This comment has been minimized.

Show comment
Hide comment
@rade

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.

Member

rade commented Jan 29, 2015

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.

@aanm

This comment has been minimized.

Show comment
Hide comment
@aanm

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
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.

@rade

This comment has been minimized.

Show comment
Hide comment
@rade

rade Jan 29, 2015

Member

@aanm you don't need to build weave in order to run it.

Member

rade commented Jan 29, 2015

@aanm you don't need to build weave in order to run it.

@aanm

This comment has been minimized.

Show comment
Hide comment
@aanm

aanm Jan 29, 2015

@rade Oh yeah, I completely forgot about that.
@dpw Forget what I said :-)

aanm commented Jan 29, 2015

@rade Oh yeah, I completely forgot about that.
@dpw Forget what I said :-)

@dpw

This comment has been minimized.

Show comment
Hide comment
@dpw

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?

Contributor

dpw commented Jan 29, 2015

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?

@rade

This comment has been minimized.

Show comment
Hide comment
@rade

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.

Member

rade commented Jan 29, 2015

What's wrong with recommending building in a container?

Nothing. But somebody would actually have to make that work and document it.

@aanm

This comment has been minimized.

Show comment
Hide comment
@aanm

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

@dpw

This comment has been minimized.

Show comment
Hide comment
@dpw

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).

Contributor

dpw commented Feb 2, 2015

@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).

@rade

This comment has been minimized.

Show comment
Hide comment
@rade

rade Feb 28, 2015

Member

This has been superseded by #387.

Member

rade commented Feb 28, 2015

This has been superseded by #387.

@rade rade closed this Feb 28, 2015

@rade rade added this to the 0.10.0 milestone Apr 18, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment