Re: This application failed to start because it could not find or load the Qt platform plugin "xcb" in ""

[Walter Schwarzenfeld]

Solved: Overlooked to downgrade two qt5 packages.

___
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"

This application failed to start because it could not find or load the Qt platform plugin "xcb" in ""

[Walter Schwarzenfeld]

The recent update of the qt5* ports puzzled some things, could not 
update cause of qt5-networking is broken with__libressl. I reverted the 
partial update.


After this I got this error: This application failed to start because it 
could not find or load the Qt platform plugin "xcb" in "".


Problem withvlc and xpdf (maybe, with some more).  Vlc and xpdf 
core-dumps on start.


Does anybody know how to fix this?

___
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: Packaging failures with devel/gvfs, devel/gnome-vfs

[Jonathan Chen]

On 18 May 2018 at 23:34, Jonathan Chen  wrote:
> Hi,
>
> On STABLE-11/amd64, with the ports tree at r470283, I am seeing
> packaging errors for gvfs and gnome-vfs when running synth:
[...]

With the latest update to samba46, the configure phase for devel/gvfs
and devel/gnome-vfs does *NOT* pick up Samba support, even when
--enable-samba is set. For gvfs, the logs indicate:

gvfs configuration summary:

gio module directory : ${exec_prefix}/lib/gio/modules

hotplug backend:  hal

Blu-ray metadata support: no
Google support:   yes
HTTP/WebDAV support:  yes
Samba support:no
...

-- 
Jonathan Chen 
___
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: Why portmaster uses g++ not g++6 nor clang++?

[Koichiro Iwao]

On Fri, May 18, 2018 at 08:30:38PM +0200, Stefan Esser wrote:
> Sorry, this was my fault and I hope it is fixed with the follow-up commit
> to portmaster version 3.19-10.

Thanks! Works for me now.

-- 
meta 
___
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: Practice of "Sponsored by" in commit messages

[Eitan Adler]

On 18 May 2018 at 11:20, Kurt Jaeger  wrote:
> Hi!
>
>>  The FreeBSD project could help by asking committers to qualify
>>  "Sponsored by" lines to indicate which participant(s) is(are) sponsored,
>>  in way that is equivalent to the way that the actual work itself is
>>  customarily attributed.
>
>> >>> This sounds reasonable, so I suggest that you submit a
>> >>> patch to the ports handbook that describes it for maintainers
>> >>> and committers.
>
>> >> One thing to note: FreeBSD has a custom patch to subversion to detect
>> >> "ORGANIZATION_NAME" and automatically append it to the default
>> >> template. This is likely why its getting added in unexpected places.
>
>> > How do you think I should handle that in my forthcoming doc patch? Is
>> > there a related bug I should file against services?
>
>> Its a client side patch of the subversion binary.  I'm not sure the
>> best way to handle it beyond perhaps changing the template a bit?
>
> What change would be needed ? There's already a Sponsored by field ?

My point is that the custom patch pre-fills the field, which is why
submitters often see it filled when they don't expect it: the
committer doesn't do it by hand.



-- 
Eitan Adler
___
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: Practice of "Sponsored by" in commit messages

[John W. O'Brien]

On 2018/05/18 07:38, John W. O'Brien wrote:
> On 2018/05/18 00:15, Kurt Jaeger wrote:
>> Hi!
>>
>>> The FreeBSD project could help by asking committers to qualify
>>> "Sponsored by" lines to indicate which participant(s) is(are) sponsored,
>>> in way that is equivalent to the way that the actual work itself is
>>> customarily attributed.
>>
>> This sounds reasonable, so I suggest that you submit a
>> patch to the ports handbook that describes it for maintainers
>> and committers. 
>>
> 
> Thank you. I will prepare a patch. It seems like it should be against
> the Committers' Guide [0], though. Also, since this would apply to trees
> besides ports, is there a venue besides this list where I should solicit
> feedback?
> 
> [0]
> https://www.freebsd.org/doc/en_US.ISO8859-1/articles/committers-guide/article.html#commit-log-message
> 

Patch away [0]!

[0] https://bugs.freebsd.org/228353

-- 
John W. O'Brien
OpenPGP keys:
0x33C4D64B895DBF3B



signature.asc
Description: OpenPGP digital signature

Re: Why portmaster uses g++ not g++6 nor clang++?

[Rozhuk Ivan]

On Fri, 18 May 2018 22:46:15 +0200
Stefan Esser  wrote:

> I'm working on a completely new re-implementation of portmaster and
> the new version will get these points right. Fixing the current port
> version is too hard and wasted effort, since only the features and
> command line options are carried over, but none of the code of the
> current version.

Thanks!
I see code, take parts frome there for my work purposes and old portmaster
have bad design. 


As one more future request.
Current pkg create use only one thread to compress.

I do small set of benchmarks on Ryzen 2700x:

root@rimwks# /usr/bin/time -h pkg create --format tar -o /tmp/ llvm60
7.01s real  6.11s user  0.72s sys
796,5 MB

root@rimwks# /usr/bin/time -h pkg create --format tbz -o /tmp/ llvm60
1m3.56s real1m1.48s user0.38s sys
209,9 MB

root@rimwks# /usr/bin/time -h pkg create --format tgz -o /tmp/ llvm60
36.54s real 35.10s user 0.48s sys
244,8 MB

root@rimwks# /usr/bin/time -h pkg create --format txz -o /tmp/ llvm60
5m42.69s real   5m33.15s user   0.53s sys
154,7 MB

root@rimwks# /usr/bin/time -h pbzip2 -k -p16 /tmp/llvm60-6.0.0_3.tar
7.47s real  1m40.36s user   5.34s sys
210,7 MB

root@rimwks# /usr/bin/time -h tar --use-compress-program=pigz -cf 
/tmp/llvm60-6.0.0_3.tar.gz /tmp/llvm60-6.0.0_3.tar
2.85s real  40.44s user 0.75s sys
244,6 MB

root@rimwks# /usr/bin/time -h xz -T 0 --compress /tmp/llvm60-6.0.0_3.tar
49.96s real 9m30.88s user   33.84s sys
156,9 MB


5m42.69s - for compress, compile time ~ 15 minutes. Terrable!!!
49.96s - is mutch better.

Can you try to implement option to chose at least tar/txz, and probably
for txz use "xz -T 0 --compress" ?

___
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: Why portmaster uses g++ not g++6 nor clang++?

[Stefan Esser]

Am 18.05.18 um 22:17 schrieb Rozhuk Ivan:
> On Fri, 18 May 2018 20:30:38 +0200
> Stefan Esser  wrote:
> 
>> Sorry, this was my fault and I hope it is fixed with the follow-up
>> commit to portmaster version 3.19-10.
>>
> 
> Sorry for offtopic, but if portmaster install some build dep or run dep
> if does not mark it as autoinstalled, and:
> pkg query -e '%a = 0' %o
> show autotools, help2man and other build only crap as user install it,
> pkg autoremove
> does not remove this.
> 
> Also --delete-build-only broken.
> 
> portmaster -BgvDa -y --delete-build-only 
> --local-packagedir=/usr/ports/packages --packages-local
> if found some package - install it, and after install create package and 
> overwrite original.
> pkg create -n will prevent this, or additional checks, or just keep remember 
> that pkg allready
> exist because port just installed from it.

I'm working on a completely new re-implementation of portmaster and the new
version will get these points right. Fixing the current port version is too
hard and wasted effort, since only the features and command line options are
carried over, but none of the code of the current version.

The current port master port was written at the time of the "old" package
management tools (pre PKG-NG). It took me quite some time and effort to
implement flavors support in that version, and I found that it is much
harder to maintain that version than to rewrite it with the current package
tools in mind.

The new version is already able to upgrade ports, but it lacks some of the
features of the old version (e.g. installation from local packages). But it
is already better at tracking changes, e.g. as in the recent KDE4 port and
package renaming (where both port directory and package name were changed
at the same time and the current portmaster in ports has no way to track
this change and to upgrade the affected ports).

But I'm not going to implement all features of the current portmaster. E.g.
I have no plan to implement dependency tracking via the INDEX file or the
installation of packages from a remote repository (since mixing locally
compiled and official packages is not well supported). But I plan to offer
the installation of build dependencies from locally cached packages (and
the deinstallation after they are no longer required).

But the use case you described in your mail will be covered.

I hope to have the new version ready for testing as a portmaster-devel port
before the end of June.

Regards, STefan
___
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: Practice of "Sponsored by" in commit messages

[John W. O'Brien]

On 5/18/18 14:20, Kurt Jaeger wrote:
> Hi!
> 
>> The FreeBSD project could help by asking committers to qualify
>> "Sponsored by" lines to indicate which participant(s) is(are) sponsored,
>> in way that is equivalent to the way that the actual work itself is
>> customarily attributed.
> 
> This sounds reasonable, so I suggest that you submit a
> patch to the ports handbook that describes it for maintainers
> and committers.
> 
 One thing to note: FreeBSD has a custom patch to subversion to detect
 "ORGANIZATION_NAME" and automatically append it to the default
 template. This is likely why its getting added in unexpected places.
> 
>>> How do you think I should handle that in my forthcoming doc patch? Is
>>> there a related bug I should file against services?
> 
>> Its a client side patch of the subversion binary.  I'm not sure the
>> best way to handle it beyond perhaps changing the template a bit?
> 
> What change would be needed ? There's already a Sponsored by field ?
> 
> The custom patch is here:
> 
> https://svnweb.freebsd.org/ports/head/devel/subversion/files/extra-patch-fbsd-template?revision=411397=markup

I agree that this won't necessarily need to change. If anything, a very
small reminder to committers, or suggestive wording change, to fix-up
the the sponsorship line when applicable. I will submit a separate bug
with a candidate change that depends on the doc bug. I won't mind if the
doc bug is accepted and the subversion portbug is closed WONTFIX upon
review.

-- 
John W. O'Brien
OpenPGP keys:
0x33C4D64B895DBF3B



signature.asc
Description: OpenPGP digital signature

Re: Why portmaster uses g++ not g++6 nor clang++?

[Rozhuk Ivan]

On Fri, 18 May 2018 20:30:38 +0200
Stefan Esser  wrote:

> Sorry, this was my fault and I hope it is fixed with the follow-up
> commit to portmaster version 3.19-10.
> 

Sorry for offtopic, but if portmaster install some build dep or run dep
if does not mark it as autoinstalled, and:
pkg query -e '%a = 0' %o
show autotools, help2man and other build only crap as user install it,
pkg autoremove
does not remove this.

Also --delete-build-only broken.

portmaster -BgvDa -y --delete-build-only --local-packagedir=/usr/ports/packages 
--packages-local
if found some package - install it, and after install create package and 
overwrite original.
pkg create -n will prevent this, or additional checks, or just keep remember 
that pkg allready
exist because port just installed from it.
___
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: Why portmaster uses g++ not g++6 nor clang++?

[Walter Schwarzenfeld]

Thanks, fixes problem for me.

___
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: Why portmaster uses g++ not g++6 nor clang++?

[Stefan Esser]

Am 18.05.18 um 17:13 schrieb Koichiro Iwao:
> Hi,
> 
> I'm building devel/qt5-make by portmaster. Somehow portmaster incorrectly
> detects gcc6 and uses g++ despite it is actually installed as g++6. If I > 
> build it without portmaster, clang++ is used and build finishes successfully.

Sorry, this was my fault and I hope it is fixed with the follow-up commit
to portmaster version 3.19-10.

I had received a proposed patch to significantly speed-up portmaster by
caching of a few parameters in environment variables. My commit was meant
to work around a side effect of the proposed patch (sourcing of a script
imported several unused subroutines into portmaster and I wanted to just
use the result of execution of the one relevant subroutine, but missed the
fact that the quoting came out wrong ...).

(If you are interested: The environment variable _CXXINTERNAL_acaad9ca
should contain the literal character sequence "-lc++" including the
double quotes, when I use eval as in the defective version, I either get
no quotes around -lc++ or I get extra double-quotes around the whole
variable, if I eval the script output piped through sed s:":\\:" ...)

Since I did not manage to get the correct result without sourcing the
script, I gave in and accept the fact, that these subroutines are now
imported into portmaster.

Anyway, I hope my latest commit has fixed the problem ...

Regards, STefan
___
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: Practice of "Sponsored by" in commit messages

[Kurt Jaeger]

Hi!

>  The FreeBSD project could help by asking committers to qualify
>  "Sponsored by" lines to indicate which participant(s) is(are) sponsored,
>  in way that is equivalent to the way that the actual work itself is
>  customarily attributed.

> >>> This sounds reasonable, so I suggest that you submit a
> >>> patch to the ports handbook that describes it for maintainers
> >>> and committers.

> >> One thing to note: FreeBSD has a custom patch to subversion to detect
> >> "ORGANIZATION_NAME" and automatically append it to the default
> >> template. This is likely why its getting added in unexpected places.

> > How do you think I should handle that in my forthcoming doc patch? Is
> > there a related bug I should file against services?

> Its a client side patch of the subversion binary.  I'm not sure the
> best way to handle it beyond perhaps changing the template a bit?

What change would be needed ? There's already a Sponsored by field ?

The custom patch is here:

https://svnweb.freebsd.org/ports/head/devel/subversion/files/extra-patch-fbsd-template?revision=411397=markup

-- 
p...@opsec.eu+49 171 31013722 years to go !
___
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: Practice of "Sponsored by" in commit messages

[Eitan Adler]

On 18 May 2018 at 04:40, John W. O'Brien  wrote:
> On 2018/05/18 00:43, Eitan Adler wrote:
>> On 17 May 2018 at 21:15, Kurt Jaeger  wrote:
>>> Hi!
>>>
 The FreeBSD project could help by asking committers to qualify
 "Sponsored by" lines to indicate which participant(s) is(are) sponsored,
 in way that is equivalent to the way that the actual work itself is
 customarily attributed.
>>>
>>> This sounds reasonable, so I suggest that you submit a
>>> patch to the ports handbook that describes it for maintainers
>>> and committers.
>>
>> One thing to note: FreeBSD has a custom patch to subversion to detect
>> "ORGANIZATION_NAME" and automatically append it to the default
>> template. This is likely why its getting added in unexpected places.
>>
>
> How do you think I should handle that in my forthcoming doc patch? Is
> there a related bug I should file against services?

Its a client side patch of the subversion binary.  I'm not sure the
best way to handle it beyond perhaps changing the template a bit?


-- 
Eitan Adler
___
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: help2man fails to build saying p5-Locale-gettext>=0 - not found

[Lars Schotte]

OK, reextraction of the ports tree with "portsnap extract" helped.
Looks like my suspicion was right and
===>   Registering installation for help2man-1.47.6
the port got trough.

I havent done any clean operations, like you suggested.
Maybe that would have helped too, but I think that in that case the
problem would manifestate itself somehow differently.

On Fri, 18 May 2018 17:35:07 +0200
Lars Schotte  wrote:

> Yes, I ll try that, but first I did extract the ports tree again,
> because this looks suspiciously, I noticed that on a jail it had
> built, so it may have something to do with my ports tree that I
> updated maybe too often.
> 
> On Fri, 18 May 2018 16:48:52 +0200
> Walter Schwarzenfeld  wrote:
> 
> > Sometimes the depends are not proper cleaned and "make clean
> > depends" helps.
> > 
> > ___
> > 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"
> 
> 
> 



-- 
 Lars Schotte
 Mudroňova 13
92101 Piešťany
___
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: Why portmaster uses g++ not g++6 nor clang++?

[Walter Schwarzenfeld]

I got another error with portmaster and qt5-qmake:

qt5-qmake

/usr/local/lib/compat/libstdc++.so.6: version CXXABI_1.3.8 required by 
/ram/usr/ports/devel/qt5-qmake/work/qtbase-everywhere-src-5.10.1/bin/qmake 
not found


but works in the 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: help2man fails to build saying p5-Locale-gettext>=0 - not found

[Lars Schotte]

Yes, I ll try that, but first I did extract the ports tree again,
because this looks suspiciously, I noticed that on a jail it had built,
so it may have something to do with my ports tree that I updated maybe
too often.

On Fri, 18 May 2018 16:48:52 +0200
Walter Schwarzenfeld  wrote:

> Sometimes the depends are not proper cleaned and "make clean depends"
> helps.
> 
> ___
> 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"



-- 
 Lars Schotte
 Mudroňova 13
92101 Piešťany
___
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"

Why portmaster uses g++ not g++6 nor clang++?

[Koichiro Iwao]

Hi,

I'm building devel/qt5-make by portmaster. Somehow portmaster 
incorrectly detects gcc6 and
uses g++ despite it is actually installed as g++6. If I build it without 
portmaster, clang++

is used and build finishes successfully.

$ pkg info | grep gcc
gcc-ecj-4.5Eclipse Java Compiler used to build GCC 
Java

gcc6-6.4.0_7   GNU Compiler Collection 6
gcc6-aux-20170802_1Version of GCC 6 with full Ada support
gccmakedep-1.0.3   Create dependencies in makefiles using 
'gcc -M'


# portmaster devel/qt5-qmake
(snip)
===>  License LGPL21 accepted by the user
===>   qt5-qmake-5.10.1 depends on file: /usr/local/sbin/pkg - found
===> Fetching all distfiles required by qt5-qmake-5.10.1 for building
===>  Extracting for qt5-qmake-5.10.1
=> SHA256 Checksum OK for 
KDE/Qt/5.10.1/qtbase-everywhere-src-5.10.1.tar.xz.

===>  Patching for qt5-qmake-5.10.1
===>  Applying extra patch 
/usr/ports/devel/qt5/files/extrapatch-configure
===>  Applying extra patch 
/usr/ports/devel/qt5/files/extrapatch-mkspecs_features_create__cmake.prf
===>  Applying extra patch 
/usr/ports/devel/qt5/files/extrapatch-mkspecs_features_qt__module.prf
===>  Applying extra patch 
/usr/ports/devel/qt5/files/extrapatch-mkspecs_common_bsd_bsd.conf

===>  Applying FreeBSD patches for qt5-qmake-5.10.1
/usr/bin/sed -i "" -e "/DEFAULT_LIBDIRS=/ 
s,\"n,n/usr/local/lib&,"  
/ssd/tmp/ports/usr/ports/devel/qt5-qmake/work/qtbase-everywhere-src-5.10.1/configure

===>   qt5-qmake-5.10.1 depends on executable: gmake - found
===>   qt5-qmake-5.10.1 depends on package: pkgconf>=1.3.0_1 - found
===>   qt5-qmake-5.10.1 depends on file: /usr/local/bin/python2.7 - 
found

===>   qt5-qmake-5.10.1 depends on executable: gcc6 - found
===>   qt5-qmake-5.10.1 depends on file: /usr/local/bin/as - found
===>  Configuring for qt5-qmake-5.10.1
/bin/mkdir -p 
/ssd/tmp/ports/usr/ports/devel/qt5-qmake/work/qtbase-everywhere-src-5.10.1
echo 'CMAKE_MODULE_TESTS = -' > 
/ssd/tmp/ports/usr/ports/devel/qt5-qmake/work/qtbase-everywhere-src-5.10.1/.qmake.cache
echo 'QMAKE_LIBDIR_FLAGS = 
-L/ssd/tmp/ports/usr/ports/devel/qt5-qmake/work/qtbase-everywhere-src-5.10.1/lib' 
>> /ssd/tmp/ports/usr/ports/devel/qt5-qmake/work/qtbase-everywhere-src-5.10.1/.qmake.cache

Creating qmake...
===>  Building for qt5-qmake-5.10.1
gmake[1]: Entering directory 
'/ssd/tmp/ports/usr/ports/devel/qt5-qmake/work/qtbase-everywhere-src-5.10.1/qmake'
g++ -c -o main.o   -std=c++11 -ffunction-sections -g -g  
-I/ssd/tmp/ports/usr/ports/devel/qt5-qmake/work/qtbase-everywhere-src-5.10.1/qmake 
-I/ssd/tmp/ports/usr/ports/devel/qt5-qmake/work/qtbase-everywhere-src-5.10.1/qmake/library 
-I/ssd/tmp/ports/usr/ports/devel/qt5-qmake/work/qtbase-everywhere-src-5.10.1/qmake/generators 
-I/ssd/tmp/ports/usr/ports/devel/qt5-qmake/work/qtbase-everywhere-src-5.10.1/qmake/generators/unix 
-I/ssd/tmp/ports/usr/ports/devel/qt5-qmake/work/qtbase-everywhere-src-5.10.1/qmake/generators/win32 
-I/ssd/tmp/ports/usr/ports/devel/qt5-qmake/work/qtbase-everywhere-src-5.10.1/qmake/generators/mac 
-I/ssd/tmp/ports/usr/ports/devel/qt5-qmake/work/qtbase-everywhere-src-5.10.1/include 
-I/ssd/tmp/ports/usr/ports/devel/qt5-qmake/work/qtbase-everywhere-src-5.10.1/include/QtCore 
-I/ssd/tmp/ports/usr/ports/devel/qt5-qmake/work/qtbase-everywhere-src-5.10.1/include/QtCore/5.10.1 
-I/ssd/tmp/ports/usr/ports/devel/qt5-qmake/work/qtbase-everywhere-src-5.10.1/include/QtCore/5.10.1/QtCore 
-I../src/corelib/global 
-I/ssd/tmp/ports/usr/ports/devel/qt5-qmake/work/qtbase-everywhere-src-5.10.1/mkspecs/freebsd-g++ 
-DQT_VERSION_STR=\"5.10.1\" -DQT_VERSION_MAJOR=5 -DQT_VERSION_MINOR=10 
-DQT_VERSION_PATCH=1 -DQT_BUILD_QMAKE -DQT_BOOTSTRAPPED 
-DPROEVALUATOR_FULL -DQT_NO_FOREACH 
/ssd/tmp/ports/usr/ports/devel/qt5-qmake/work/qtbase-everywhere-src-5.10.1/qmake/main.cpp
gmake[1]: Leaving directory 
'/ssd/tmp/ports/usr/ports/devel/qt5-qmake/work/qtbase-everywhere-src-5.10.1/qmake'

===> Compilation failed unexpectedly.
Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure 
to

the maintainer.
*** Error code 1

# make -C /usr/ports/devel/qt5-make
-> builds successfully using clang++

--
meta
___
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: help2man fails to build saying p5-Locale-gettext>=0 - not found

[Walter Schwarzenfeld]

Sometimes the depends are not proper cleaned and "make clean depends" helps.

___
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"

help2man fails to build saying p5-Locale-gettext>=0 - not found

[Lars Schotte]

Hi,

I am trying to build /usr/ports/mail/opensmtpd and it fails on:

/usr/ports/mail/opensmtpd # make BATCH=yes install
===>   opensmtpd-5.9.2p1_6,1 depends on
file: /usr/local/lib/libcrypto.so.43 - found ===>
opensmtpd-5.9.2p1_6,1 depends on shared library: libevent.so - not
found ===>   libevent-2.1.8_1 depends on executable: autoconf-2.69 -
not found ===>   autoconf-2.69_1 depends on executable: gm4 - not found
===>   m4-1.4.18,1 depends on executable: makeinfo - not found ===>
texinfo-6.5,1 depends on executable: help2man - not found ===>
help2man-1.47.6 depends on package: p5-Locale-gettext>=0 - not found
===>   help2man-1.47.6 depends on package: p5-Locale-gettext>=0 - not
found *** Error code 1

Stop.
make[5]: stopped in /usr/ports/misc/help2man
*** Error code 1

Stop.
make[4]: stopped in /usr/ports/print/texinfo
*** Error code 1

Stop.
make[3]: stopped in /usr/ports/devel/m4
*** Error code 1

Stop.
make[2]: stopped in /usr/ports/devel/autoconf
*** Error code 1

Stop.
make[1]: stopped in /usr/ports/devel/libevent
*** Error code 1

Stop.
make: stopped in /usr/ports/mail/opensmtpd


and help2man itself also:
/usr/ports/misc/help2man # make BATCH=yes install
===>   help2man-1.47.6 depends on package: p5-Locale-gettext>=0 - not
found ===>   help2man-1.47.6 depends on package: p5-Locale-gettext>=0 -
not found *** Error code 1

Stop.
make: stopped in /usr/ports/misc/help2man

Lately I am getting strange results, like when I do make install
somewhere it stops with $? == 0. And does nothing.

Is it possible that my ports tree got somehow corrupted or sth?
I am using portsnap to keep it in sync.

Thanks.

-- 
 Lars Schotte
 Mudroňova 13
92101 Piešťany
___
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: Practice of "Sponsored by" in commit messages

[John W. O'Brien]

On 2018/05/18 00:43, Eitan Adler wrote:
> On 17 May 2018 at 21:15, Kurt Jaeger  wrote:
>> Hi!
>>
>>> The FreeBSD project could help by asking committers to qualify
>>> "Sponsored by" lines to indicate which participant(s) is(are) sponsored,
>>> in way that is equivalent to the way that the actual work itself is
>>> customarily attributed.
>>
>> This sounds reasonable, so I suggest that you submit a
>> patch to the ports handbook that describes it for maintainers
>> and committers.
> 
> One thing to note: FreeBSD has a custom patch to subversion to detect
> "ORGANIZATION_NAME" and automatically append it to the default
> template. This is likely why its getting added in unexpected places.
> 

How do you think I should handle that in my forthcoming doc patch? Is
there a related bug I should file against services?

-- 
John W. O'Brien
OpenPGP keys:
0x33C4D64B895DBF3B



signature.asc
Description: OpenPGP digital signature

Re: Practice of "Sponsored by" in commit messages

[John W. O'Brien]

On 2018/05/18 00:15, Kurt Jaeger wrote:
> Hi!
> 
>> The FreeBSD project could help by asking committers to qualify
>> "Sponsored by" lines to indicate which participant(s) is(are) sponsored,
>> in way that is equivalent to the way that the actual work itself is
>> customarily attributed.
> 
> This sounds reasonable, so I suggest that you submit a
> patch to the ports handbook that describes it for maintainers
> and committers. 
> 

Thank you. I will prepare a patch. It seems like it should be against
the Committers' Guide [0], though. Also, since this would apply to trees
besides ports, is there a venue besides this list where I should solicit
feedback?

[0]
https://www.freebsd.org/doc/en_US.ISO8859-1/articles/committers-guide/article.html#commit-log-message

-- 
John W. O'Brien
OpenPGP keys:
0x33C4D64B895DBF3B



signature.asc
Description: OpenPGP digital signature

Packaging failures with devel/gvfs, devel/gnome-vfs

[Jonathan Chen]

Hi,

On STABLE-11/amd64, with the ports tree at r470283, I am seeing
packaging errors for gvfs and gnome-vfs when running synth:

===>  Building package for gvfs-1.26.3_9
pkg-static: Unable to access file
/construction/xports/devel/gvfs/work/stage/usr/local/libexec/gvfsd-smb:No
such file or directory
pkg-static: Unable to access file
/construction/xports/devel/gvfs/work/stage/usr/local/libexec/gvfsd-smb-browse:No
such file or directory
pkg-static: Unable to access file
/construction/xports/devel/gvfs/work/stage/usr/local/share/GConf/gsettings/gvfs-smb.convert:No
such file or directory
pkg-static: Unable to access file
/construction/xports/devel/gvfs/work/stage/usr/local/share/gvfs/mounts/smb-browse.mount:No
such file or directory
pkg-static: Unable to access file
/construction/xports/devel/gvfs/work/stage/usr/local/share/gvfs/mounts/smb.mount:No
such file or directory
pkg-static: Unable to access file
/construction/xports/devel/gvfs/work/stage/usr/local/share/glib-2.0/schemas/org.gnome.system.smb.gschema.xml:No
such file or d
irectory
*** Error code 1

===>  Building package for gnome-vfs-2.24.4_8
pkg-static: Unable to access file
/construction/xports/devel/gnome-vfs/work/stage/usr/local/etc/gnome-vfs-2.0/modules/smb-module.conf:No
such file or directory
pkg-static: Unable to access file
/construction/xports/devel/gnome-vfs/work/stage/usr/local/lib/gnome-vfs-2.0/modules/libsmb.a:No
such file or directory
pkg-static: Unable to access file
/construction/xports/devel/gnome-vfs/work/stage/usr/local/lib/gnome-vfs-2.0/modules/libsmb.la:No
such file or directory
pkg-static: Unable to access file
/construction/xports/devel/gnome-vfs/work/stage/usr/local/lib/gnome-vfs-2.0/modules/libsmb.so:No
such file or directory
*** Error code 1

Anyone else seeing this?
-- 
Jonathan Chen 
___
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"