Re: library porting question - optional python bindings
On Thu, Mar 3, 2016 at 2:20 AM, Shane Ambler wrote: > On 03/03/2016 03:03, Chris Inacio wrote: > >> On Tue, Mar 1, 2016 at 3:04 AM, Shane Ambler >> wrote: >> >> On 01/03/2016 13:08, Chris Inacio wrote: >>> >>> All, >>>> >>>> I'm trying to build a port definition for a library/application that can >>>> optionally include Python bindings. The library/application generally >>>> depends on other C libraries to exist (ZMQ v3, Protobufs-C) and if you >>>> enable Python support, then you need a Python interpreter plus >>>> Python-protobufs & python zmq. >>>> >>>> > >>> For a normal python module I would suggest making it as a separate port >>> that just installs the python module. This makes it easier to install >>> multiple versions for each python version. The py-module port can be a >>> slave of the main port so you don't have to maintain the same code >>> twice. >>> >>> > >>> The library is generally a C library with 3 "targets" a library (.so), >> header files (.h), and daemon that can be used as well. >> >> If you enable the optional Python support, then there is an entire python >> build area with the full "python setup.py ..." that gets run *from the C >> Makefile* when the Python dependencies are available. >> >> So yes, I can see that it makes sense to have this has 2 separate ports >> from a port maintenance point of view, but this is distributed as a single >> distribution. >> >> So you're suggesting 2 ports, from one source download, and 1 of those >> ports dependent on the other port? >> > > Yes you only need the one src tarball and distinfo between both ports. > You can also use the same pkg-descr and maybe the same pkg-plist. > > If the contents of the python port Makefile is kept to a minimum you > will only have to change the master port to update both, the changes to > the master port will apply to both ports. You can use conditionals to > get variations between building each port. > > The python module port only needs to depend on the master port if it > uses the libraries installed by it, which I'm expecting it would. > > > > -- > FreeBSD - the place to B...Software Developing > > Shane Ambler > > Thanks for the tips, truly helpful. I'm doing the slave port implementation. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: library porting question - optional python bindings
On Tue, Mar 1, 2016 at 8:57 PM, Kubilay Kocak wrote: > On 1/03/2016 1:38 PM, Chris Inacio wrote: > > All, > > > > I'm trying to build a port definition for a library/application that can > > optionally include Python bindings. The library/application generally > > depends on other C libraries to exist (ZMQ v3, Protobufs-C) and if you > > enable Python support, then you need a Python interpreter plus > > Python-protobufs & python zmq. > > > > Putting an OPTION of Python in the port file is easy. Including the > > optional Python dependencies (and presumably targets - but I'm not that > far > > yet) seems to be a lot more complicated. I haven't found anything that > > would tell me how I'm supposed to do that. I have found that I'm > supposed > > to add pyXX prefixes to the python targets. > > > > Does anyone know of a similar application/library that I can go look at? > > Is there any documentation on how to solve this? > > Package it separately if it: > > * Is listed on PyPI (.python.org) > * Has value separate from the 'parent software' (on its own) > * Users might want it without the parent software > * Is pure python, OR > * Doesn't otherwise explicitly require depend on the parent software > > From the description above, given the dependencies of each of the > software components are different (main software, python package), I'd > go for separate packaging unless there's a good reason not to. > > > thanks, > > Chris Inacio > > I don't believe you can build the Python package without the availability of the C library. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: library porting question - optional python bindings
On Tue, Mar 1, 2016 at 3:04 AM, Shane Ambler wrote:
> On 01/03/2016 13:08, Chris Inacio wrote:
>
>> All,
>>
>> I'm trying to build a port definition for a library/application that can
>> optionally include Python bindings. The library/application generally
>> depends on other C libraries to exist (ZMQ v3, Protobufs-C) and if you
>> enable Python support, then you need a Python interpreter plus
>> Python-protobufs & python zmq.
>>
>> Putting an OPTION of Python in the port file is easy. Including the
>> optional Python dependencies (and presumably targets - but I'm not that
>> far
>> yet) seems to be a lot more complicated. I haven't found anything that
>> would tell me how I'm supposed to do that. I have found that I'm supposed
>> to add pyXX prefixes to the python targets.
>>
>
> Python bindings as in a module that can be imported in python? or
> python bindings that help the lib linking to it to be exposed to python?
>
> The difference is a python module will be installed into
> pythonx.y/site-packages while the other will install lib/libxxx.so
>
> devel/boost-python-libs is an example of the later.
>
> For a normal python module I would suggest making it as a separate port
> that just installs the python module. This makes it easier to install
> multiple versions for each python version. The py-module port can be a
> slave of the main port so you don't have to maintain the same code
> twice.
>
> A port with PORTNAME=nose and PKGNAMEPREFIX=${PYTHON_PKGNAMEPREFIX}
> can then end up with multiple installs to support each python version.
>
> pkg info -ox nose
> py27-nose-1.3.7devel/py-nose
> py34-nose-1.3.7devel/py-nose
> py35-nose-1.3.7devel/py-nose
>
> Does anyone know of a similar application/library that I can go look at?
>> Is there any documentation on how to solve this?
>>
>
> I have graphics/openimageio and py-openimageio as well as
> graphics/opencolorio that has opencolorio-tools and py-opencolorio as
> slaves.
>
> openimageio uses SLAVE_PORT as defined by the ports infrastructure
> while opencolorio defines it's own OCIO_SLAVE to distinguish between
> the two slaves
>
> Using VARIABLE?=xxx in the master Makefile allows the slave port to
> override that variable.
>
> --
> FreeBSD - the place to B...Software Developing
>
> Shane Ambler
>
>
The library is generally a C library with 3 "targets" a library (.so),
header files (.h), and daemon that can be used as well.
If you enable the optional Python support, then there is an entire python
build area with the full "python setup.py ..." that gets run *from the C
Makefile* when the Python dependencies are available.
So yes, I can see that it makes sense to have this has 2 separate ports
from a port maintenance point of view, but this is distributed as a single
distribution.
So you're suggesting 2 ports, from one source download, and 1 of those
ports dependent on the other port?
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: library porting question - optional python bindings
On Mon, Feb 29, 2016 at 10:04 PM, Chris H wrote:
> On Mon, 29 Feb 2016 18:53:37 -0800 "Chris H"
> wrote
>
> > On Mon, 29 Feb 2016 21:38:40 -0500 Chris Inacio
> wrote
> >
> > > All,
> > >
> > > I'm trying to build a port definition for a library/application that
> can
> > > optionally include Python bindings. The library/application generally
> > > depends on other C libraries to exist (ZMQ v3, Protobufs-C) and if you
> > > enable Python support, then you need a Python interpreter plus
> > > Python-protobufs & python zmq.
> > >
> > > Putting an OPTION of Python in the port file is easy. Including the
> > > optional Python dependencies (and presumably targets - but I'm not
> that far
> > > yet) seems to be a lot more complicated. I haven't found anything that
> > > would tell me how I'm supposed to do that. I have found that I'm
> supposed
> > > to add pyXX prefixes to the python targets.
> > >
> > > Does anyone know of a similar application/library that I can go look
> at?
> > > Is there any documentation on how to solve this?
> > Sure. You've read the Porters Handbook;
> > https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/
> > Right? :)
>
I have read through the handbook - although probably not linearly. I have
read the section on Python in ports.
But the combination of what I'm trying to do - Python as an option - can do
that, but also including extra python library dependencies as an option
doesn't seem straight forward.
> > Other than that, there's a myriad of ports in the ports tree.
> > Almost all of which have (OPTIONAL) requirements. Your keyword
> > here is; depends. :)
> If I understand you correctly; maybe something like;
>
> if ${PORT_OPTIONS:MMYOPTION}
> RUN_DEPENDS=${LOCALBASE}/lib/somelib:${PORTSDIR}/lang/python...
> endif
>
> Same is true for BUILD_DEPENDS
>
>
I was hoping there was some newer / less documented
_PYPACKAGE_DEPENDS variable that would save the day here. Or
port that someone had worked on and effectively created some Makefile foo
that does the equivalent of my made up variable/macro name.
>
> --Chris
> > >
> > > thanks,
> > > Chris Inacio
> >
> >
>
>
> ___
> freebsd-ports@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
>
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
library porting question - optional python bindings
All, I'm trying to build a port definition for a library/application that can optionally include Python bindings. The library/application generally depends on other C libraries to exist (ZMQ v3, Protobufs-C) and if you enable Python support, then you need a Python interpreter plus Python-protobufs & python zmq. Putting an OPTION of Python in the port file is easy. Including the optional Python dependencies (and presumably targets - but I'm not that far yet) seems to be a lot more complicated. I haven't found anything that would tell me how I'm supposed to do that. I have found that I'm supposed to add pyXX prefixes to the python targets. Does anyone know of a similar application/library that I can go look at? Is there any documentation on how to solve this? thanks, Chris Inacio ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Completely unscientific poll: cfengine, puppet, other?
Hello all, I was considering adding some more support into some tooling/ports for FreeBSD and I thought it would probably be good to get configuration management support some thought. So I can understand under certain Linux flavors (e.g. RedHat) that puppet is the de facto choice - since the distribution packager has chosen one. Is there a dominant one for FreeBSD? Happy if you would just reply with which one, if any, you use. If you want to add more to the conversation, that's fine. I understand the mailing list I posted this to and the likely audience - as I said I started think about this from adding more support into some ports. Thanks chris inacio ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Can't get _IMPLIES to work
I'm having trouble getting the _IMPLIES to function correctly. I have been trying to improve a port and add more of the options available in the underlying package into the ports/pkg system. Basically, as a smoke test I attempt to enable "NONIP" without selecting "MPLS". NONIP requires MPLS to function. I think I've covered this in the NONIP_IMPLIES, but I get configure errors stating that MPLS must be enabled. Here is the Makefile snippet, I've tried a bit of reordering and including/removing/moving the ".include " Any help would be appreciated. thanks OPTIONS_DEFINE= PAYLOAD APPLABEL PLUGIN FPEXPORT ENTROPY MPLS NONIP P0FPRINT IFE OPTIONS_DEFAULT= PAYLOAD APPLABEL PLUGIN ENTROPY PAYLOAD_DESC= YAF will enable reading past IP headers to do deep packet inspec APPLABEL_DESC= Create protocol application labels via traffic header inspection PLUGIN_DESC=Enable YAF plugins, primary for application labeling. FPEXPORT_DESC= Export of OS fingerprinting information, e.g. p0f. ENTROPY_DESC= Generate Shannon entropy values of the data stream. MPLS_DESC= MPLS capture and export NONIP_DESC= Capture non-IP packets P0FPRINT_DESC= Generate p0f O/S fingerprinting. IFEXP_DESC= Export capture interface for DAG/Napatech/Netronome cards. CMPTIP4_DESC= Create compact IPv4 output (no IPv6 support). LOCALTIME_DESC= Allow localtime to be used for command inputs and record printin DNSAUTH_DESC= Modify DNS export to only export Authoritative DNS responses. DNSNX_DESC= Modify DNS export to only export NXDomain responses. PAYLOAD_CONFIGURE_ENABLE= payload APPLABEL_CONFIGURE_ENABLE= applabel PLUGIN_CONFIGURE_ENABLE=plugins FPEXPORT_CONFIGURE_ENABLE= fpexporter ENTROPY_CONFIGURE_ENABLE= entropy MPLS_CONFIGURE_ENABLE= mpls NONIP_CONFIGURE_ENABLE= nonip P0FPRINT_CONFIGURE_ENABLE= p0fprinter IFEXP_CONFIGURE_ENABLE= interface CMPTIP4_CONFIGURE_ENABLE= compact-ip4 LOCALTIME_CONFIGURE_ENABLE= localtime DNSAUTH_CONFIGURE_ENABLE= exportDNSAuth DNSNX_CONFIGURE_ENABLE= exportDNSNXDomain APPLABEL_IMPLIES= PAYLOAD DNSAUTH_IMPLIES=PLUGIN APPLABEL DNSNX_IMPLIES= PLUGIN APPLABEL ENTROPY_IMPLIES=PAYLOAD P0FPRINT_IMPLIES= APPLABEL NONIP_IMPLIES= MPLS .include ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Update of port definition for YAF
Hello all, To whom do I send an updated YAF port definition? I updated the Makefile and the distinfo file and ran a build test through poudriere. I don't actually have the ports build installed on my VM test machine, so while I have added a lot more options to YAF, I don't have a good way to test that. (If they are supposed to show up in poudriere, then those are broken.) I've attached the updated files here. Do binary pkg files get generated automatically using poudriere? Is there anything else I should provide? Thanks, Chris Makefile Description: Binary data distinfo Description: Binary data ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: port dependencies with port options
On Fri, Apr 20, 2012 at 11:36 AM, Jeremy Messenger wrote: > On Fri, Apr 20, 2012 at 5:29 AM, Vitaly Magerya > wrote: > > Chris Inacio wrote: > >> I wanted to add an option to multiple ports - that is easy. But, those > >> ports have a dependency relationship, and I only want the last node in > the > >> port dependency graph to build with that option if the requisite ports > have > >> too. > >> > >> In real terms: > >> > >> net/spread <- net/libfixbuf <- net-mgmt/yaf > >> > >> I added a SPREAD option to net/libfixbuf & to net-mgmt/yaf. > net-mgmt/yaf > >> can only build a Spread version if libfixbuf was built with a Spread > >> version. > >> > >> Question 1) How do you construct such that if a user goes into > >> net-mgmt/yaf chooses Spread and fixbuf isn't already installed, it > builds > >> fixbuf with the spread option? > >> > >> Question 2) How do you ensure that if fixbuf is already installed, it > has > >> the Spread option enabled, or disallow/error the Yaf Spread option? > > > > One way to do this is to create a separate port net/libfixbuf-spread > > that either installs separate libfixbuf-spread.so or just conflicts with > > net/libfixbuf, and then make net-mgmt/yaf depend on that if SPREAD > > option is on. > > Please do not create a split port that will end up conflict with the > each others. It creates more problems rather than solve. > > Either split port without have conflict to the each others or enable > SPREAD by default. If enable by default then add a check error if > libfixbuf-spread.so does not exist then give user a head up to enable > SPREAD back on. > > Split port without conflict is always best opinion, but if it's > complicate to do it then do the enable SPREAD by default instead. > > Cheers, > Mezz > > > So let me see if I understand the conversation so far correctly: (*) If I want to detect it, then I would need something like a new library name output from from fixbuf based on the build. (This currently doesn't exist.) (*) I could do some split port, but (even being a noob) sounds pretty bad. (*) There isn't a current method that directly queries build options from one port to another. Am I capturing current state? Chris -- > mezz.free...@gmail.com - m...@freebsd.org > FreeBSD GNOME Team > http://www.FreeBSD.org/gnome/ - gn...@freebsd.org > ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
port dependencies with port options
Hello ports wizards, I wanted to add an option to multiple ports - that is easy. But, those ports have a dependency relationship, and I only want the last node in the port dependency graph to build with that option if the requisite ports have too. In real terms: net/spread <- net/libfixbuf <- net-mgmt/yaf I added a SPREAD option to net/libfixbuf & to net-mgmt/yaf. net-mgmt/yaf can only build a Spread version if libfixbuf was built with a Spread version. Question 1) How do you construct such that if a user goes into net-mgmt/yaf chooses Spread and fixbuf isn't already installed, it builds fixbuf with the spread option? Question 2) How do you ensure that if fixbuf is already installed, it has the Spread option enabled, or disallow/error the Yaf Spread option? Thanks, Chris Inacio ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: lsof / tinderbox port build error
On Sun, Apr 15, 2012 at 7:28 PM, Larry Rosenman wrote: > ** Is this the same sources you have done a make buildworld buildkernel > installworld installkernel > > With? > > I would bet not - unfortunately, I don't remember enough / know enough about cvsup/csup to know if I just got head-of-line, or anything related to my install (8.3 -Release). Although this is just a VM; I could wipe it out and try again at this point without too much trouble. Sounds like, in some ways, that might be easier. Chris > -- > Sent from my Android phone with K-9 Mail. Please excuse my brevity. > > Chris Inacio wrote: >> >> The solution is apparently to install the system src. There doesn't >> appear to be a ports/package to manage that. >> >> The solutions was supposed to be to install the system source. I used >> csup to install the system source, and it got further, with a different >> error: >> >> >> ===> Building for lsof-4.86B,6 >> (cd lib; make DEBUG="-O2" CFGF="-pipe -fno-strict-aliasing >> -DHASEFFNLINK=i_effnlink -DHASF_VNODE -DHASSBSTATE -DHAS_KVM_VNODE >> -DHAS_UFS1_2 -DHAS_VM_MEMATTR_T -DHAS_CDEV2PRIV -DHAS_NO_SI_UDEV >> -DHAS_SYS_SX_H -DHAS_ZFS -DHAS_V_LOCKF -DHAS_LOCKF_ENTRY -DHAS_NO_6PORT >> -DHAS_NO_6PPCB -DFREEBSDV=8030 -DHASFDESCFS=2 -DHASPSEUDOFS -DHASNULLFS >> -DHASIPv6 -DHAS_STRFTIME -DLSOF_VSTR=\"8.3-RELEASE\"") >> cc -pipe -fno-strict-aliasing -DHASEFFNLINK=i_effnlink -DHASF_VNODE >> -DHASSBSTATE -DHAS_KVM_VNODE -DHAS_UFS1_2 -DHAS_VM_MEMATTR_T >> -DHAS_CDEV2PRIV -DHAS_NO_SI_UDEV -DHAS_SYS_SX_H -DHAS_ZFS -DHAS_V_LOCKF >> -DHAS_LOCKF_ENTRY -DHAS_NO_6PORT -DHAS_NO_6PPCB -DFREEBSDV=8030 >> -DHASFDESCFS=2 -DHASPSEUDOFS -DHASNULLFS -DHASIPv6 -DHAS_STRFTIME >> -DLSOF_VSTR="8.3-RELEASE" -I/usr/src/sys -O2 -c ckkv.c >> In file included from ../dlsof.h:90, >> from ../lsof.h:195, >> from ckkv.c:43: >> /usr/src/sys/sys/conf.h:340: warning: parameter names (without types) in >> function declaration >> In file included from ../dlsof.h:127, >> from ../lsof.h:195, >> from ckkv.c:43: >> /usr/src/sys/sys/socket.h:39:28: error: machine/_align.h: No such file or >> directory >> In file included from /usr/src/sys/vm/pmap.h:89, >> from ../dlsof.h:400, >> from ../lsof.h:195, >> from ckkv.c:43: >> /usr/include/machine/pmap.h:247: error: expected specifier-qualifier-list >> before 'cpumask_t' >> *** Error code 1 >> >> Stop in /usr/ports/sysutils/lsof/work/lsof_4.86B.freebsd/lib. >> *** Error code 1 >> >> Stop in /usr/ports/sysutils/lsof/work/lsof_4.86B.freebsd. >> *** Error code 1 >> >> Stop in /usr/ports/sysutils/lsof. >> *** Error code 1 >> >> Stop in /usr/ports/ports-mgmt/tinderbox. >> *** Error code 1 >> >> Stop in /usr/ports/ports-mgmt/tinderbox. >> freebsd64_vm# >> >> >> >> On Sun, Apr 15, 2012 at 8:04 AM, Chris Inacio wrote: >> >>> >>> There was no config.log to attach to the report. This is the >>> (hopefully) relevant screen text. >>> >>> => Attempting to fetch >>> ftp://lsof.itap.purdue.edu/pub/tools/unix/lsof/NEW/lsof_4.86B.freebsd.tar.bz2 >>> lsof_4.86B.freebsd.tar.bz2100% of 468 kB 880 kBps >>> ===> Extracting for lsof-4.86B,6 >>> => SHA256 Checksum OK for lsof_4.86B.freebsd.tar.bz2. >>> ===> Patching for lsof-4.86B,6 >>> ===> Configuring for lsof-4.86B,6 >>> Creating ./lockf_owner.h from /usr/src/sys/kern/kern_lockf.c >>> FATAL ERROR: can't read /usr/src/sys/kern/kern_lockf.c >>> FATAL ERROR: ./lockf_owner.h creation failed (see 00FAQ) >>> ===> Script "Configure" failed unexpectedly. >>> Please report the problem to l...@lerctr.org [maintainer] and attach the >>> "/usr/ports/sysutils/lsof/work/lsof_4.86B.freebsd/config.log" including >>> the >>> output of the failure of your make command. Also, it might be a good >>> idea to >>> provide an overview of all packages installed on your system (e.g. an `ls >>> /var/db/pkg`). >>> *** Error code 1 >>> >>> Stop in /usr/ports/sysutils/lsof. >>> *** Error code 1 >>> >>> Stop in /usr/ports/ports-mgmt/tinderbox. >>> *** Error code 1 >>> >>> Stop in /usr/ports/ports-mgmt/tinderbox. >>> >>> >>> >>> >>> >>> >> ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: lsof / tinderbox port build error
The solution is apparently to install the system src. There doesn't appear to be a ports/package to manage that. The solutions was supposed to be to install the system source. I used csup to install the system source, and it got further, with a different error: ===> Building for lsof-4.86B,6 (cd lib; make DEBUG="-O2" CFGF="-pipe -fno-strict-aliasing -DHASEFFNLINK=i_effnlink -DHASF_VNODE -DHASSBSTATE -DHAS_KVM_VNODE -DHAS_UFS1_2 -DHAS_VM_MEMATTR_T -DHAS_CDEV2PRIV -DHAS_NO_SI_UDEV -DHAS_SYS_SX_H -DHAS_ZFS -DHAS_V_LOCKF -DHAS_LOCKF_ENTRY -DHAS_NO_6PORT -DHAS_NO_6PPCB -DFREEBSDV=8030 -DHASFDESCFS=2 -DHASPSEUDOFS -DHASNULLFS -DHASIPv6 -DHAS_STRFTIME -DLSOF_VSTR=\"8.3-RELEASE\"") cc -pipe -fno-strict-aliasing -DHASEFFNLINK=i_effnlink -DHASF_VNODE -DHASSBSTATE -DHAS_KVM_VNODE -DHAS_UFS1_2 -DHAS_VM_MEMATTR_T -DHAS_CDEV2PRIV -DHAS_NO_SI_UDEV -DHAS_SYS_SX_H -DHAS_ZFS -DHAS_V_LOCKF -DHAS_LOCKF_ENTRY -DHAS_NO_6PORT -DHAS_NO_6PPCB -DFREEBSDV=8030 -DHASFDESCFS=2 -DHASPSEUDOFS -DHASNULLFS -DHASIPv6 -DHAS_STRFTIME -DLSOF_VSTR="8.3-RELEASE" -I/usr/src/sys -O2 -c ckkv.c In file included from ../dlsof.h:90, from ../lsof.h:195, from ckkv.c:43: /usr/src/sys/sys/conf.h:340: warning: parameter names (without types) in function declaration In file included from ../dlsof.h:127, from ../lsof.h:195, from ckkv.c:43: /usr/src/sys/sys/socket.h:39:28: error: machine/_align.h: No such file or directory In file included from /usr/src/sys/vm/pmap.h:89, from ../dlsof.h:400, from ../lsof.h:195, from ckkv.c:43: /usr/include/machine/pmap.h:247: error: expected specifier-qualifier-list before 'cpumask_t' *** Error code 1 Stop in /usr/ports/sysutils/lsof/work/lsof_4.86B.freebsd/lib. *** Error code 1 Stop in /usr/ports/sysutils/lsof/work/lsof_4.86B.freebsd. *** Error code 1 Stop in /usr/ports/sysutils/lsof. *** Error code 1 Stop in /usr/ports/ports-mgmt/tinderbox. *** Error code 1 Stop in /usr/ports/ports-mgmt/tinderbox. freebsd64_vm# On Sun, Apr 15, 2012 at 8:04 AM, Chris Inacio wrote: > > There was no config.log to attach to the report. This is the (hopefully) > relevant screen text. > > => Attempting to fetch > ftp://lsof.itap.purdue.edu/pub/tools/unix/lsof/NEW/lsof_4.86B.freebsd.tar.bz2 > lsof_4.86B.freebsd.tar.bz2100% of 468 kB 880 kBps > ===> Extracting for lsof-4.86B,6 > => SHA256 Checksum OK for lsof_4.86B.freebsd.tar.bz2. > ===> Patching for lsof-4.86B,6 > ===> Configuring for lsof-4.86B,6 > Creating ./lockf_owner.h from /usr/src/sys/kern/kern_lockf.c > FATAL ERROR: can't read /usr/src/sys/kern/kern_lockf.c > FATAL ERROR: ./lockf_owner.h creation failed (see 00FAQ) > ===> Script "Configure" failed unexpectedly. > Please report the problem to l...@lerctr.org [maintainer] and attach the > "/usr/ports/sysutils/lsof/work/lsof_4.86B.freebsd/config.log" including the > output of the failure of your make command. Also, it might be a good idea > to > provide an overview of all packages installed on your system (e.g. an `ls > /var/db/pkg`). > *** Error code 1 > > Stop in /usr/ports/sysutils/lsof. > *** Error code 1 > > Stop in /usr/ports/ports-mgmt/tinderbox. > *** Error code 1 > > Stop in /usr/ports/ports-mgmt/tinderbox. > > > > > > ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
lsof / tinderbox port build error
There was no config.log to attach to the report. This is the (hopefully) relevant screen text. => Attempting to fetch ftp://lsof.itap.purdue.edu/pub/tools/unix/lsof/NEW/lsof_4.86B.freebsd.tar.bz2 lsof_4.86B.freebsd.tar.bz2100% of 468 kB 880 kBps ===> Extracting for lsof-4.86B,6 => SHA256 Checksum OK for lsof_4.86B.freebsd.tar.bz2. ===> Patching for lsof-4.86B,6 ===> Configuring for lsof-4.86B,6 Creating ./lockf_owner.h from /usr/src/sys/kern/kern_lockf.c FATAL ERROR: can't read /usr/src/sys/kern/kern_lockf.c FATAL ERROR: ./lockf_owner.h creation failed (see 00FAQ) ===> Script "Configure" failed unexpectedly. Please report the problem to l...@lerctr.org [maintainer] and attach the "/usr/ports/sysutils/lsof/work/lsof_4.86B.freebsd/config.log" including the output of the failure of your make command. Also, it might be a good idea to provide an overview of all packages installed on your system (e.g. an `ls /var/db/pkg`). *** Error code 1 Stop in /usr/ports/sysutils/lsof. *** Error code 1 Stop in /usr/ports/ports-mgmt/tinderbox. *** Error code 1 Stop in /usr/ports/ports-mgmt/tinderbox. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: port variants
On Apr 13, 2012, at 3:39 PM, Freddie Cash wrote: > On Fri, Apr 13, 2012 at 12:04 PM, Chris Inacio wrote: >> I was recently asked to do some FreeBSD ports support work. I mostly use a >> Mac and the MacPorts system. MacPorts has the concept of a variant for a >> port, but I can't find the analogue in the FreeBSD system. >> >> Does the FreeBSD ports system have the concept of a variant? If so, can >> someone point me in the right direction on how to create one? > > Describing what a "variant" is, how it works in MacPorts, and what you > are trying to do would help a lot. :) > > The closest guess I could make would be "slave port", but I don't > think that works the same way. > Sorry, you're right. For example, a port of say Emacs could have a variant of X11. So Emacs or Emacs+X11. The X11 variant would (somewhat obviously) include building regular Emacs but also the X11 toolbar etc. while Emacs wouldn't include any X11 features (& dependencies). On the Mac, we can build universal binaries (PowerPC, ia32, and x86_64), at the cost of disk space. So we can build almost any package with the +universal variant. Is that a reasonable explanation? Chris > -- > Freddie Cash > fjwc...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
port variants
Hello all, I was recently asked to do some FreeBSD ports support work. I mostly use a Mac and the MacPorts system. MacPorts has the concept of a variant for a port, but I can't find the analogue in the FreeBSD system. Does the FreeBSD ports system have the concept of a variant? If so, can someone point me in the right direction on how to create one? Thanks, Chris Inacio ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
