Re: Makefile RUN_DEPENDS=option

2017-11-15 Thread Chris H
On Wed, 15 Nov 2017 22:40:18 +0100 Mathieu Arnold wrote > Le 15/11/2017 à 01:20, Chris H a écrit : > > On Tue, 14 Nov 2017 14:15:39 -0700 Adam Weinberger wrote > > > >>> On 14 Nov, 2017, at 14:05, Ernie Luzar wrote: > >>> > >>> Have a

FreeBSD Port: multimedia/mythtv

2017-11-15 Thread Austin C Phelps
I have been working for a couple of month and finally got MythTV 29 working in FreeBSD 11. So I been working toward update the ports to create a new package. I'm not fully understanding all the ins and outs of it creation. As long as I set up the environment before hand, I can compile and have

Re: What is the correct way to require a specific version of clang?

2017-11-15 Thread Brooks Davis
On Wed, Nov 15, 2017 at 01:43:29PM -0800, Yuri wrote: > On 11/15/17 11:58, Brooks Davis wrote: > > You'll need to start a shell in your poudreire instance and see what is > > failing. I'd expect that to work. > > > > Note that it is possible to misconfigure the llvm38 port such that this > >

Re: What is the correct way to require a specific version of clang?

2017-11-15 Thread Yuri
On 11/15/17 11:58, Brooks Davis wrote: You'll need to start a shell in your poudreire instance and see what is failing. I'd expect that to work. Note that it is possible to misconfigure the llvm38 port such that this config is broken by disabling the CLANG option. What's happening is that

Re: Makefile RUN_DEPENDS=option

2017-11-15 Thread Mathieu Arnold
Le 15/11/2017 à 01:20, Chris H a écrit : > On Tue, 14 Nov 2017 14:15:39 -0700 Adam Weinberger wrote > >>> On 14 Nov, 2017, at 14:05, Ernie Luzar wrote: >>> >>> Have a simple port that needs wget to work. >>> >>> I want RUN_DEPENDS to first check if wget is

Re: r450663 (basic flavors) breaks WRKDIRPREFIX='' for complex ports

2017-11-15 Thread Bryan Drewery
On 11/15/2017 11:57 AM, Lev Serebryakov wrote: > On 15.11.2017 22:27, Bryan Drewery wrote: > >>> % make WRKDIRPREFIX='' extract >>> make[1]: don't know how to make >>> /usr/home/lev/FreeBSD/ports/devel/subversion/work/.extract_done.subversion._usr_local. >>> Stop >>> >>> make[1]: stopped in

Re: What is the correct way to require a specific version of clang?

2017-11-15 Thread Brooks Davis
On Wed, Nov 15, 2017 at 10:37:37AM -0800, Yuri wrote: > There is no such thing as USES=clang:38, for example. > > When I try this: > > .include > > .if ${OPSYS} == FreeBSD && ${OSVERSION} < 110 > BUILD_DEPENDS=?? clang38:lang/clang38 > RUN_DEPENDS=?? clang38:lang/clang38 >

Re: r450663 (basic flavors) breaks WRKDIRPREFIX='' for complex ports

2017-11-15 Thread Lev Serebryakov
On 15.11.2017 22:27, Bryan Drewery wrote: >> % make WRKDIRPREFIX='' extract >> make[1]: don't know how to make >> /usr/home/lev/FreeBSD/ports/devel/subversion/work/.extract_done.subversion._usr_local. >> Stop >> >> make[1]: stopped in /usr/home/lev/FreeBSD/ports/devel/subversion >> *** Error code

Re: r450663 (basic flavors) breaks WRKDIRPREFIX='' for complex ports

2017-11-15 Thread Lev Serebryakov
On 15.11.2017 22:27, Bryan Drewery wrote: > You did not set WRKDIRPREFIX='' here as a make argument. So yeah it's > going to fallback to /usr/local/build/ports. Yes, to demonstrate that default WRKDIRPREFIX from /etc/make.conf is used (which is very inconvenient for ports developer). >> % make

Re: r450663 (basic flavors) breaks WRKDIRPREFIX='' for complex ports

2017-11-15 Thread Bryan Drewery
On 11/15/2017 11:08 AM, Lev Serebryakov wrote: > On 15.11.2017 21:07, Bryan Drewery wrote: > >> First, using "WRKDIRPREFIX=''" doesn't seem like a "supported feature". >> If there's docs or a specific commit to support such a thing then sure. > I've used it from my first day as ports committer.

Re: r450663 (basic flavors) breaks WRKDIRPREFIX='' for complex ports

2017-11-15 Thread Lev Serebryakov
On 15.11.2017 21:07, Bryan Drewery wrote: > First, using "WRKDIRPREFIX=''" doesn't seem like a "supported feature". > If there's docs or a specific commit to support such a thing then sure. I've used it from my first day as ports committer. Maybe, it was not supported, but it worked for tens of

What is the correct way to require a specific version of clang?

2017-11-15 Thread Yuri
There is no such thing as USES=clang:38, for example. When I try this: .include .if ${OPSYS} == FreeBSD && ${OSVERSION} < 110 BUILD_DEPENDS=  clang38:lang/clang38 RUN_DEPENDS=    clang38:lang/clang38 CC= clang38 CXX=    clang++38 .endif It prints warnings in

Re: r450663 (basic flavors) breaks WRKDIRPREFIX='' for complex ports

2017-11-15 Thread Bryan Drewery
On 11/15/2017 6:47 AM, Lev Serebryakov wrote: > > I have WRKDIRPREFIX set to /usr/local/build/ports in /etc/make.conf. > > when I want to test port changes in my home directory I'm using > > % make WRKDIRPREFIX='' check-plist > ... > > It worked for me till r450663 every time and for every

r450663 (basic flavors) breaks WRKDIRPREFIX='' for complex ports

2017-11-15 Thread Lev Serebryakov
I have WRKDIRPREFIX set to /usr/local/build/ports in /etc/make.conf. when I want to test port changes in my home directory I'm using % make WRKDIRPREFIX='' check-plist ... It worked for me till r450663 every time and for every port. For example, it worked for 'devel/subversion': % pwd

Re: A project with it's own Makefiles

2017-11-15 Thread Adam Weinberger
> On 15 Nov, 2017, at 1:08, blubee blubeeme wrote: > > I have a port that has a it's own Makefiles that you're suppose to call to > build for example the folder structure is like this: > > project > --subfolderA > ---subfolderA-src > ---subfolderA-Makefile > > --subfolderB

FreeBSD ports you maintain which are out of date

2017-11-15 Thread portscout
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated,

A project with it's own Makefiles

2017-11-15 Thread blubee blubeeme
I have a port that has a it's own Makefiles that you're suppose to call to build for example the folder structure is like this: project --subfolderA ---subfolderA-src ---subfolderA-Makefile --subfolderB ---subfolderB-src ---subfolderB-Makefile --subfolderC ---subfolderC-src