Menu

#1039 Firewall Builder

Added_to_Fink
closed-accepted
None
5
2004-02-24
2003-05-22
lord
No

This is fink package for Firewall Builder. This is
official package produced by the project 1.0.10
release. It consists of the GUI package (fwbuilder) and
shared components (API, support files, etc.) -
libfwbuilder.

Discussion

  • lord

    lord - 2003-05-22

    Logged In: YES
    user_id=550

    Project home page: http://www.fwbuilder.org/

     
  • David R. Morrison

    Logged In: YES
    user_id=271216

    Hi. There is a problem with some of your dependencies. In
    general, you need to put foo-shlibs into Depends, and either foo
    or foo-dev into BuildDepends.

    A more serious problem is that, although libfwbuilder compiled
    and installed just fine, fwbuilder failed to compile. Here's the
    error:

    sw/lib/sigc++-1.0/include -I/sw/include/sigc++-1.0 -I/sw/lib/
    gtkmm/include -I/sw/include/gtk-1.2 -I/usr/X11R6/include -I/
    sw/include/gdk-pixbuf-1.0 -c TargetDialog_unknown_glade.cc
    In file included from TargetDialog_unknown_glade.cc:11:
    TargetDialog_unknown.hh:29:33: fwbuilder/FWObject.hh: No
    such file or directory
    In file included from TargetDialog_unknown.hh:31,
    from TargetDialog_unknown_glade.cc:11:
    DialogPlugin.hh:37:33: fwbuilder/FWObject.hh: No such file or
    directory
    In file included from TargetDialog_unknown.hh:31,
    from TargetDialog_unknown_glade.cc:11:
    DialogPlugin.hh:53: syntax error before `::' token
    DialogPlugin.hh:71: `libfwbuilder' was not declared in this scope
    DialogPlugin.hh:71: parse error before `::' token
    DialogPlugin.hh:72: `libfwbuilder' was not declared in this scope
    DialogPlugin.hh:72: parse error before `::' token
    DialogPlugin.hh:75: `libfwbuilder' was not declared in this scope
    DialogPlugin.hh:75: parse error before `::' token
    DialogPlugin.hh:76: `libfwbuilder' was not declared in this scope
    DialogPlugin.hh:76: parse error before `::' token
    DialogPlugin.hh:77: `libfwbuilder' was not declared in this scope
    DialogPlugin.hh:77: parse error before `::' token
    DialogPlugin.hh:78: `libfwbuilder' was not declared in this scope
    DialogPlugin.hh:78: parse error before `::' token
    DialogPlugin.hh:79: `libfwbuilder' was not declared in this scope
    DialogPlugin.hh:79: parse error before `::' token
    DialogPlugin.hh:80: `libfwbuilder' was not declared in this scope

    ETC ETC

    DialogPlugin.hh:112: warning: ISO C++ forbids defining types
    within return type
    DialogPlugin.hh:112: syntax error before `(' token
    DialogPlugin.hh:117: `libfwbuilder' was not declared in this scope
    DialogPlugin.hh:117: parse error before `::' token
    DialogPlugin.hh:117: virtual outside class declaration
    DialogPlugin.hh:125: `libfwbuilder' was not declared in this scope
    DialogPlugin.hh:125: parse error before `::' token
    DialogPlugin.hh:125: virtual outside class declaration
    In file included from TargetDialog_unknown_glade.cc:11:
    TargetDialog_unknown.hh:50: parse error before `*' token
    make[2]: *** [TargetDialog_unknown_glade.o] Error 1
    make[2]: Leaving directory `/Volumes/Mac_OS_9/sw/src/
    fwbuilder-1.0.10-1/fwbuilder-1.0.10/src/gui'
    make[2]: Entering directory `/Volumes/Mac_OS_9/sw/src/
    fwbuilder-1.0.10-1/fwbuilder-1.0.10/src/tools'
    g++ -DLOCALEDIR=\"/sw/share/locale\" -
    DPACKAGE=\"fwbuilder\" -DHAVE_CONFIG_H -I. -I../.. -I../../intl
    -I/sw/include -DHAVE_CONFIG_H -I/sw/lib/sigc++-1.0/include -
    I/sw/include/sigc++-1.0 -I/sw/lib/gtkmm/include -I/sw/include/
    gtk-1.2 -I/usr/X11R6/include -I/sw/include -I/sw/include/glib-1.2
    -I/sw/lib/glib/include -D_REENTRANT -I/sw/include/libxml2 -I/
    sw/include/glib-1.2 -I/sw/lib/glib/include -D_REENTRANT -I../gui/
    -c fwblookup.cc
    fwblookup.cc:43:34: fwbuilder/Resources.hh: No such file or
    directory
    fwblookup.cc:45:41: fwbuilder/FWObjectDatabase.hh: No such
    file or directory
    fwblookup.cc:46:33: fwbuilder/XMLTools.hh: No such file or
    directory
    fwblookup.cc:47:36: fwbuilder/FWException.hh: No such file or
    directory
    fwblookup.cc:48:33: fwbuilder/Firewall.hh: No such file or
    directory
    fwblookup.cc:49:34: fwbuilder/Interface.hh: No such file or
    directory
    fwblookup.cc:75: namespace `libfwbuilder' undeclared

    ETC ETC

    fwblookup.cc:289: parse error before `}' token
    fwblookup.cc:291: warning: ISO C++ forbids declaration of `exit'
    with no type
    fwblookup.cc:291: redefinition of `int exit'
    fwblookup.cc:288: `int exit' previously defined here
    fwblookup.cc:292: parse error before `}' token
    make[2]: *** [fwblookup.o] Error 1
    make[2]: Leaving directory `/Volumes/Mac_OS_9/sw/src/
    fwbuilder-1.0.10-1/fwbuilder-1.0.10/src/tools'
    make[1]: *** [install] Error 2
    make[1]: Leaving directory `/Volumes/Mac_OS_9/sw/src/
    fwbuilder-1.0.10-1/fwbuilder-1.0.10/src'
    make: *** [install] Error 2
    ### execution of make failed, exit code 2
    Failed: installing fwbuilder-1.0.10-1 failed

     
  • David R. Morrison

    Logged In: YES
    user_id=271216

    OK, I have a theory about what happened. It looks like this was
    actually happening during fink's Install Phase, rather than during
    the Compile Phase, and that the Install had already moved the
    header files to the installation directory.

    This sounds like the "relinking bug" which some versions of
    libtool have been subject too. When that bug occurs, libtool
    notices that the lib hasn't been installed into it's final resting
    place, and relinks it.

     
  • lord

    lord - 2003-06-17

    Logged In: YES
    user_id=550

    I am attaching new version of the package. It adds libfwbuilder
    into build dependencies and this should solve the problem.
    Please let me know if it works for you now.

     
  • Peter O'Gorman

    Peter O'Gorman - 2004-02-02
    • milestone: --> 373614
     
  • Peter O'Gorman

    Peter O'Gorman - 2004-02-02

    Logged In: YES
    user_id=27265

    Hi,
    Looks like nobody has had time to look at this for a while, sorry.
    Could you attach .info files for the new version (1.1.2) of
    fwbuilder? Note that the Depends: field is quite incorrect. Things
    like libxml2 should be in BuildDepends: and libxml2-shlibs in the
    Depends: line. the Depends: line should contain only those
    packages required for your package to run, everything else is
    BuildDepends:.

    Thanks.
    Peter

     
  • lord

    lord - 2004-02-02

    Logged In: YES
    user_id=550

    Yes, we are in process of preparing new package. We run into
    some problems after Panther upgrade which are now
    (hopefully) are solved and I plan to update this item with
    new .info files soon.

     
  • lord

    lord - 2004-02-09

    Logged In: YES
    user_id=550

    Attached are latest .INFO files tested to work with 10.3.
    I also reviewed dependencies and did some other minor changes.

    These packages are for latest official release.

     
  • Peter O'Gorman

    Peter O'Gorman - 2004-02-11
    • assigned_to: nobody --> ogorman
     
  • Peter O'Gorman

    Peter O'Gorman - 2004-02-11

    Logged In: YES
    user_id=27265

    Hi,
    Aside from:
    Warning: Field "compilescript" appears to contain a hardcoded /sw.
    (fwbuilder-1.1.2-2.info)
    Warning: Field "compilescript" appears to contain a hardcoded /sw.
    (libfwbuilder-1.0.2-2.info)
    Warning: Length of package description exceeds 45 characters.
    (libfwbuilder-1.0.2-2.info)

    dlcompat and dpcompat-shlibs dependencies should not appear for 10.3
    packages, is this for the 10.3 tree the 10.2-gcc3.3 tree or both?
    Same is true for libpoll and libpoll-shlibs.

    Do you really need to run the autotools for this to build?

    I haven't tried to build it yet, but I think %p/lib/libfwcompiler.5:1:0.dylib
    should have "." not ":".

    I'll look at fixing these up if I have time, but I'm hoping you'll get around
    to it :-)

     
  • lord

    lord - 2004-02-15

    fwbuilder-1.1.2-2.info

     
  • lord

    lord - 2004-02-15

    libfwbuilder-1.0.2-2.info

     
  • lord

    lord - 2004-02-15

    Logged In: YES
    user_id=550

    Hi!

    I've updated the package taking into the account your remarks.

    To answer your questions:

    1. We do need to run autools during the build. I removed
    hardcoded path from the call.

    1. This is package for 10.3, I do not think we going to
    support 10.2 simply because we do not have access to 10.2
    machine.

    Vadim

     
  • Peter O'Gorman

    Peter O'Gorman - 2004-02-16

    ogormans-libfwbuilder.info

     
  • Peter O'Gorman

    Peter O'Gorman - 2004-02-16

    Logged In: YES
    user_id=27265

    Hi,
    There were still one or two problems with this.
    1) the -shlibs splitoff should have most of the Depends: your main
    libfwbuilder package contains nothing but headers lib symlinks and a
    -config script (correctly). It need only depend on the libfwbuilder-shlibs
    package.
    2) These packages link against libcrypto, they should depend on
    openssl097-shlibs and probably ought to have the name changed to be
    -ssl, but that is not a requirement.
    3) You call libtoolize --force --copy, but also have UpdateLibtool: True in
    the package. This is a little strange. I removed the UpdateLibtool, it is
    only required to update a packages libtool if it is libtool-1.3.x in the
    package.

    Probably some other things. I have attached the .info files that I'm
    willing to commit to unstable/crypto. If you are okay with that, just say
    so, if not then submit another revision :)

    Thanks for putting up with this process so far.

     
  • Peter O'Gorman

    Peter O'Gorman - 2004-02-16

    ogormans-fwbuilder.info

     
  • lord

    lord - 2004-02-23

    Logged In: YES
    user_id=550

    Peter,

    Thanks for your changes to info files. I looked at them and
    they look OK to me. Also I tested them and they build fine
    on my machine as well. So I guess it is OK to commit them.

    One more remark about SSL dependency: it is optional for
    fwbuilder. If OpenSSL is not installed configure will notice
    that and will build it without SSL support. Since currently
    it does not pose any problem to build with openSSL I think
    we should keep this dependency. If in future we will face
    some restrictions like going to separate tree or something,
    it is OK just to drop it.

     
  • Peter O'Gorman

    Peter O'Gorman - 2004-02-24

    Logged In: YES
    user_id=27265

    In unstable/crypto

     
  • Peter O'Gorman

    Peter O'Gorman - 2004-02-24
    • status: open --> closed-accepted
     
  • Christian Schaffner

    • milestone: 373614 --> Added_to_Fink
     

Log in to post a comment.

MongoDB Logo MongoDB