Re: MOVED file on Current breaks portupgrade

Hi! > Bad format in last entry of /usr/ports/MOVED breaks portupgrade: Thanks, fixed in r413958. -- p...@opsec.eu+49 171 3101372 4 years to go ! ___ freebsd-ports@freebsd.org mailing list

MOVED file on Current breaks portupgrade

Bad format in last entry of /usr/ports/MOVED breaks portupgrade: #portupgrade -av /usr/local/lib/ruby/site_ruby/2.2/pkgtools/portsdb.rb:118:in `block (2 levels) in fill': MOVED file format error (PortsDB::MOVEDError) from /usr/local/lib/ruby/site_ruby/2.2/pkgtools/portsdb.rb:112:in

Re: port's svn commit: r413746 - in head "many ports: mark broken on powerpc64": for what toolchains?

Hi, On 04/24/16 10:16 AM, Mark Millard wrote: > > For all the port update activity (including ruby) I used gcc49, > /etc/make.conf being: > > # more /etc/make.conf DEFAULT_VERSIONS+=perl5=5.22 > WRKDIRPREFIX=/usr/obj/portswork > WITH_DEBUG= > WITH_DEBUG_FILES= > MALLOC_PRODUCTION= > # > # >

Re: port's svn commit: r413746 - in head "many ports: mark broken on powerpc64": for what toolchains?

On 2016-Apr-24, at 5:58 AM, Steve Wills wrote: > > So lang/gcc6-devel builds fine using gcc49 (which builds fine and isn't > currently marked broken. Can we patch the lang/gcc6-devel port so that > it uses gcc49 when building on powerpc64? > > Also, which compiler are you

Re: port's svn commit: r413746 - in head "many ports: mark broken on powerpc64": for what toolchains?

So lang/gcc6-devel builds fine using gcc49 (which builds fine and isn't currently marked broken. Can we patch the lang/gcc6-devel port so that it uses gcc49 when building on powerpc64? Also, which compiler are you using for building ruby? Steve On 04/24/16 03:19 AM, Mark Millard wrote: > [A

Re: Making a port - debugging cmake check_include_file

You mean that the checks are passed, but actual support of V4L - is not? V4L is the optional feature, so lack of it is not a critical error. From what I see in cmake files is that header files are detected and several knobs are set. Should I check that these headers somehow used ? I don't have

Re: Making a port - debugging cmake check_include_file

On Sun, Apr 24, 2016 at 12:48:58PM +0300 I heard the voice of abi, and lo! it spake thus: > > I passed -DCMAKE_REQUIRED_INCLUDES:STRING="${LOCALBASE}/include" from > port Makefile. > Looks like the best solution - no need to poke upstream or make patch. Interesting. It's not clear from the docs

Re: Making a port - debugging cmake check_include_file

I passed -DCMAKE_REQUIRED_INCLUDES:STRING="${LOCALBASE}/include" from port Makefile. Looks like the best solution - no need to poke upstream or make patch. On 24.04.2016 12:43, Matthew D. Fuller wrote: On Sun, Apr 24, 2016 at 12:09:53PM +0300 I heard the voice of abi, and lo! it spake thus:

Re: Making a port - debugging cmake check_include_file

On Sun, Apr 24, 2016 at 12:09:53PM +0300 I heard the voice of abi, and lo! it spake thus: > On 24.04.2016 12:00, Matthew D. Fuller wrote: > > get_property(idirs DIRECTORY ${CMAKE_CURRENT_SOURCE_DIR} PROPERTY > > INCLUDE_DIRECTORIES) > > set(CMAKE_REQUIRED_INCLUDES ${idirs}) > > > >

Re: Making a port - debugging cmake check_include_file

Nope, the same behavior. ZM has OS detection block, I added there set(CMAKE_REQUIRED_INCLUDES "/usr/include" "/usr/local/include") if system is BSD. Now I have -- Looking for libv4l1-videodev.h -- Looking for libv4l1-videodev.h - found -- Looking for linux/videodev2.h -- Looking for

Re: Making a port - debugging cmake check_include_file

On Sun, Apr 24, 2016 at 11:44:31AM +0300 I heard the voice of abi, and lo! it spake thus: > > I go the first way, however it seems that include directory is ignored > in include tests. Oh, right. That's annoying. > Should I try CMAKE_REQUIRED_INCLUDES ? However, I don't know the > effect of

Re: Failure compiling java/openjdk8

Am 23.04.2016 um 12:02 schrieb Willem Offermans: > Dear FreeBSD friends, > > In my attempt to juvenile an old FreeBSD beast, I encountered another > hurdle: a failure compiling java/openjdk8 > > > gmake[4]: Leaving directory '/usr/ports/java/openjdk8/work/openjdk/jdk/make' > gmake[4]: Entering

Re: Making a port - debugging cmake check_include_file

I go the first way, however it seems that include directory is ignored in include tests. -- Found PkgConfig: /usr/local/bin/pkg-config (found version "0.28") -- Checking for module 'libv4l1' -- Found libv4l1, version 1.6.3 gmake[3]: Entering directory

Re: port's svn commit: r413746 - in head "many ports: mark broken on powerpc64": for what toolchains?

[A top-post of the results of my test build of lang/gcc6-devel using gcc49 to do the build (until it switches over to xgcc). I do not have lang/gcc or lang/gcc48 installed.] lang/gcc6-devel's update built fine in my powerpc64-xtoolchain-gcc/powerpc64-gcc and gcc49 environment on a powerpc64