Ticket #45 (closed defect: invalid)

Opened 4 years ago

Last modified 4 years ago

compile error 0.5.74.alpha2 on fedora 7

Reported by: joukio@… Owned by: victor
Priority: major Milestone: undecided
Component: suite Version: 0.5.74 alpha 2
Keywords: Cc:

Description

compiling libvuurmuur goes well. On the other hand, compiling vuurmuur or vuurmuur_conf doesn't work. Both packages to compile. I have added the output of rpmbuild to this ticket. I don't know if something on my system is not in place, but 0.5.73 did build without problems. Don't know if it are 2 separate problems or just 1.

cheers Jouk

Attachments

vuurmuur.2.rpmbuild (27.5 KB) - added by joukio@… 4 years ago.
vuurmuur_conf.rpmbuild (34.3 KB) - added by joukio@… 4 years ago.
vuurmuur.rpmbuild (30.1 KB) - added by joukio@… 4 years ago.
including stderr
vuurmuur_conf.2.rpmbuild (39.9 KB) - added by joukio@… 4 years ago.
including stderr

Change History

Changed 4 years ago by joukio@…

Changed 4 years ago by joukio@…

Changed 4 years ago by joukio@…

including stderr

Changed 4 years ago by joukio@…

including stderr

comment:1 Changed 4 years ago by anonymous

attachments vuurmuur_conf.rpmbuild and vuurmuur.2.rpmbuild can be ignored. They don't have the stderr in them. Didn't know how to remove them.

comment:2 Changed 4 years ago by victor

It looks like the packages are build using libvuurmuur 0.5.73 and not the new 0.5.74.alpha2. Did you install the 0.5.74.alpha 2 package of libvuurmuur before building the other two? If not, please try that...

comment:3 Changed 4 years ago by anonymous

thanks, it worked. I installed libvuurmuur 0.5.74.alpha2 and compiled the vuurmuur and vuurmuur_conf packages without problem. Now I have traffic shaping as well, only outgoing traffic though. Is that going to be solved in the final release?

cheers Jouk

comment:4 Changed 4 years ago by victor

  • Status changed from new to closed
  • Resolution set to invalid

The outgoing only limitation is only for setups where Vuurmuur is not used on a gateway, but lets take that conversation out of the bugtracking system...

Note: See TracTickets for help on using tickets.