Re: Extra Clang Tools

2017-09-16 Thread blubee blubeeme 
Bug created: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222380

Can someone take a look? Different email addresses; it's fine I had the bug
created.

Best

On Sun, Sep 17, 2017 at 11:44 AM, Shane Ambler 
wrote:

> On 16/09/2017 23:22, blubee blubeeme wrote:
>
>> Howdy
>>
>> I made a few changes to the devel/llvm40/Makefile and added pp-trace as
>> the
>> last line of EXTRA_COMMANDS
>>
>> Then I rebuilt llvm40, then I noticed that the pp-trace executable is
>> built, here's a output of the work directory grepping for pp-trace:
>>
> 
>
>>
>> So it now gets built but not installed; is it possible to have the port
>> updated to move these files to the proper after they are built?
>>
>
> Create a new report at https://bugs.freebsd.org with a patch for the
> Makefile and pkg-plist. While the pp-trace binary has not been included,
> the docs for it are already in the existing packages, the makefile is
> done in a way that adding it to the command list adds it to the package.
>
> To make the following patch you would use
> diff -udp Makefile.orig Makefile
> diff -udp pkg-plist.orig pkg-plist
>
> --- Makefile.orig   2017-09-17 13:02:06.907563000 +0930
> +++ Makefile2017-09-17 13:02:16.043096000 +0930
> @@ -164,7 +164,8 @@ EXTRAS_COMMANDS+= \
> clang-reorder-fields \
> clang-tidy \
> find-all-symbols \
> -   modularize
> +   modularize \
> +   pp-trace
>  EXTRAS_LIBS=   libclangApplyReplacements \
> libclangChangeNamespace \
> libclangIncludeFixer \
> --- pkg-plist.orig  2017-05-26 17:46:41.237943000 +0930
> +++ pkg-plist   2017-09-17 12:46:44.526703000 +0930
> @@ -58,6 +58,7 @@ bin/sancov%%LLVM_SUFFIX%%
>  %%EXTRAS%%bin/clang-tidy%%LLVM_SUFFIX%%
>  %%EXTRAS%%bin/find-all-symbols%%LLVM_SUFFIX%%
>  %%EXTRAS%%bin/modularize%%LLVM_SUFFIX%%
> +%%EXTRAS%%bin/pp-trace%%LLVM_SUFFIX%%
>  %%LLD%%bin/lld%%LLVM_SUFFIX%%
>  %%LLD%%bin/lld-link%%LLVM_SUFFIX%%
>  %%LIT%%bin/lit%%LLVM_SUFFIX%%
>
>
>
> --
> FreeBSD - the place to B...Software Developing
>
> Shane Ambler
>
>
___
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: Extra Clang Tools

2017-09-16 Thread Shane Ambler 

On 16/09/2017 23:22, blubee blubeeme wrote:

Howdy

I made a few changes to the devel/llvm40/Makefile and added pp-trace as the
last line of EXTRA_COMMANDS

Then I rebuilt llvm40, then I noticed that the pp-trace executable is
built, here's a output of the work directory grepping for pp-trace:




So it now gets built but not installed; is it possible to have the port
updated to move these files to the proper after they are built?


Create a new report at https://bugs.freebsd.org with a patch for the
Makefile and pkg-plist. While the pp-trace binary has not been included,
the docs for it are already in the existing packages, the makefile is
done in a way that adding it to the command list adds it to the package.

To make the following patch you would use
diff -udp Makefile.orig Makefile
diff -udp pkg-plist.orig pkg-plist

--- Makefile.orig   2017-09-17 13:02:06.907563000 +0930
+++ Makefile2017-09-17 13:02:16.043096000 +0930
@@ -164,7 +164,8 @@ EXTRAS_COMMANDS+= \
clang-reorder-fields \
clang-tidy \
find-all-symbols \
-   modularize
+   modularize \
+   pp-trace
 EXTRAS_LIBS=   libclangApplyReplacements \
libclangChangeNamespace \
libclangIncludeFixer \
--- pkg-plist.orig  2017-05-26 17:46:41.237943000 +0930
+++ pkg-plist   2017-09-17 12:46:44.526703000 +0930
@@ -58,6 +58,7 @@ bin/sancov%%LLVM_SUFFIX%%
 %%EXTRAS%%bin/clang-tidy%%LLVM_SUFFIX%%
 %%EXTRAS%%bin/find-all-symbols%%LLVM_SUFFIX%%
 %%EXTRAS%%bin/modularize%%LLVM_SUFFIX%%
+%%EXTRAS%%bin/pp-trace%%LLVM_SUFFIX%%
 %%LLD%%bin/lld%%LLVM_SUFFIX%%
 %%LLD%%bin/lld-link%%LLVM_SUFFIX%%
 %%LIT%%bin/lit%%LLVM_SUFFIX%%


--
FreeBSD - the place to B...Software Developing

Shane Ambler

___
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: slrn from ports segfaults when running

2017-09-16 Thread tech-lists 

On Sat, Sep 16, 2017 at 09:23:08PM +0200, Christoph Brinkhaus wrote:


I am happy with slrn with options as below.

slrn --version
slrn 1.0.3
S-Lang Library Version: 2.3.1
Operating System: FreeBSD

COMPILE TIME OPTIONS:
Backends: +nntp +slrnpull +spool
External programs / libs: -canlock -inews +ssl -uudeview +iconv
Features: +decoding +emphasized_text +end_of_thread +fake_refs +gen_msgid
   -grouplens -msgid_cache +piping +rnlock +spoilers -strict_from
Using 64 bit integers for article numbers.

DEFAULTS:
Default server object: nntp
Default posting mechanism: nntp

cat news_slrn/options
# This file is auto-generated by 'make config'.
# Options for slrn-1.0.3a
_OPTIONS_READ=slrn-1.0.3a
_FILE_COMPLETE_OPTIONS_LIST=DEVIEW DOCS NLS SSL
OPTIONS_FILE_UNSET+=DEVIEW
OPTIONS_FILE_SET+=DOCS
OPTIONS_FILE_UNSET+=NLS
OPTIONS_FILE_SET+=SSL


That's interesting. My options:

slrn 1.0.3
S-Lang Library Version: 2.3.1
Operating System: FreeBSD

COMPILE TIME OPTIONS:
Backends: +nntp +slrnpull +spool
External programs / libs: -canlock -inews +ssl -uudeview +iconv
Features: +decoding +emphasized_text +end_of_thread +fake_refs
+gen_msgid -grouplens -msgid_cache +piping +rnlock +spoilers -strict_from
Using 64 bit integers for article numbers.

DEFAULTS:

Default server object: nntp
Default posting mechanism: nntp
  
# Options for slrn-1.0.3a

_OPTIONS_READ=slrn-1.0.3a
_FILE_COMPLETE_OPTIONS_LIST=DEVIEW DOCS NLS SSL
OPTIONS_FILE_SET+=DEVIEW
OPTIONS_FILE_SET+=DOCS
OPTIONS_FILE_SET+=NLS
OPTIONS_FILE_SET+=SSL

I set my configure options to be like yours, make deinstall clean
distclean install and it still segfaults. In the meantime, compiling
slrn from the git repo, the resulting installed binary works without
segfaulting. 


The port also segfaults in the same way on a hardenedbsd system. I'll
file a bug.

thanks,
--
J.
___
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"

PyPI repositories are infiltrated with malware

2017-09-16 Thread Yuri 

PyPI got hacked and now contains some malware-infected packages.

Please do not try to save time and install anything from PyPI to quickly 
test or use something. Always use FreeBSD ports and packages.



https://arstechnica.com/information-technology/2017/09/devs-unknowingly-use-malicious-modules-put-into-official-python-repository/


Cheers!

Yuri


___
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: slrn from ports segfaults when running

2017-09-16 Thread Christoph Brinkhaus 
On Sat, Sep 16, 2017 at 08:19:27PM +0700, Eugene Grosbein wrote:
> 16.09.2017 8:46, tech-lists wrote:
> 
> > # gdb ./slrn ./slrn.core
> > GNU gdb 6.1.1 [FreeBSD]
> > Copyright 2004 Free Software Foundation, Inc.
> > GDB is free software, covered by the GNU General Public License, and
> > you are
> > welcome to change it and/or distribute copies of it under certain
> > conditions.
> > Type "show copying" to see the conditions.
> > There is absolutely no warranty for GDB.  Type "show warranty" for
> > details.
> > This GDB was configured as "amd64-marcel-freebsd"...
> > Core was generated by ./slrn'.
> > Program terminated with signal 11, Segmentation fault.
> > Reading symbols from /usr/local/lib/libslang.so.2...done.
> > Loaded symbols for /usr/local/lib/libslang.so.2
> > Reading symbols from /usr/local/lib/libuu.so.3...done.
> > Loaded symbols for /usr/local/lib/libuu.so.3
> > Reading symbols from /usr/local/lib/libssl.so.43...done.
> > Loaded symbols for /usr/local/lib/libssl.so.43
> > Reading symbols from /usr/local/lib/libcrypto.so.41...done.
> > Loaded symbols for /usr/local/lib/libcrypto.so.41
> > Reading symbols from /usr/local/lib/libintl.so.8...done.
> > Loaded symbols for /usr/local/lib/libintl.so.8
> > Reading symbols from /lib/libncurses.so.8...Reading symbols from
> > /usr/lib/debug//lib/libncurses.so.8.debug...done.
> > done.
> > Loaded symbols for /lib/libncurses.so.8
> > Reading symbols from /lib/libc.so.7...Reading symbols from
> > /usr/lib/debug//lib/libc.so.7.debug...done.
> > done.
> > Loaded symbols for /lib/libc.so.7
> > Reading symbols from /lib/libm.so.5...Reading symbols from
> > /usr/lib/debug//lib/libm.so.5.debug...done.
> > done.
> > Loaded symbols for /lib/libm.so.5
> > Reading symbols from /usr/lib/i18n/libiconv_std.so.4...Reading symbols
> > from /usr/lib/debug//usr/lib/i18n/libiconv_std.so.4.debug...done.
> > done.
> > Loaded symbols for /usr/lib/i18n/libiconv_std.so.4
> > Reading symbols from /usr/lib/i18n/libmapper_serial.so.4...Reading
> > symbols from
> > /usr/lib/debug//usr/lib/i18n/libmapper_serial.so.4.debug...done.
> > done.
> > Loaded symbols for /usr/lib/i18n/libmapper_serial.so.4
> > Reading symbols from /usr/lib/i18n/libmapper_none.so.4...Reading
> > symbols from
> > /usr/lib/debug//usr/lib/i18n/libmapper_none.so.4.debug...done.
> > done.
> > Loaded symbols for /usr/lib/i18n/libmapper_none.so.4
> > Reading symbols from /usr/lib/i18n/libmapper_646.so.4...Reading
> > symbols from
> > /usr/lib/debug//usr/lib/i18n/libmapper_646.so.4.debug...done.
> > done.
> > Loaded symbols for /usr/lib/i18n/libmapper_646.so.4
> > Reading symbols from /libexec/ld-elf.so.1...Reading symbols from
> > /usr/lib/debug//libexec/ld-elf.so.1.debug...done.
> > done.
> > Loaded symbols for /libexec/ld-elf.so.1
> > #0  _citrus_NONE_stdenc_mbtocs (ce=,csid= > optimized out>, idx=0x7fffe870, s=0x7fffe868,n= > optimized out>, ps=0x0, nresult=0x7fffe860,
> > hooks=0x0)
> >at /storage/usr/src/lib/libc/iconv/citrus_none.c:96
> >96*idx = (_index_t)(unsigned char)*(*s)++;
> >(gdb)
> > backtrace:
> > 
> > (gdb) bt
> > #0  _citrus_NONE_stdenc_mbtocs (ce=,csid= > optimized out>, idx=0x7fffe870, s=0x7fffe868,n= > optimized out>, ps=0x0, nresult=0x7fffe860,
> > hooks=0x0)
> >at /storage/usr/src/lib/libc/iconv/citrus_none.c:96
> 
> You could try to remove --with-non-gnu-iconv from port's Makefile
> and rebuild slrn. Any way, you better fill a PR attaching this debugging 
> output
> you already collected.
> 
I am happy with slrn with options as below.

slrn --version
slrn 1.0.3
S-Lang Library Version: 2.3.1
Operating System: FreeBSD

COMPILE TIME OPTIONS:
 Backends: +nntp +slrnpull +spool
 External programs / libs: -canlock -inews +ssl -uudeview +iconv
 Features: +decoding +emphasized_text +end_of_thread +fake_refs +gen_msgid
-grouplens -msgid_cache +piping +rnlock +spoilers -strict_from
 Using 64 bit integers for article numbers.

DEFAULTS:
 Default server object: nntp
 Default posting mechanism: nntp

cat news_slrn/options
# This file is auto-generated by 'make config'.
# Options for slrn-1.0.3a
_OPTIONS_READ=slrn-1.0.3a
_FILE_COMPLETE_OPTIONS_LIST=DEVIEW DOCS NLS SSL
OPTIONS_FILE_UNSET+=DEVIEW
OPTIONS_FILE_SET+=DOCS
OPTIONS_FILE_UNSET+=NLS
OPTIONS_FILE_SET+=SSL

May be this information is somehow of help.

Kind regards,
Christoph
___
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: How to make www/npm pick www/node4 and www/node6 instead of www/node?

2017-09-16 Thread Julian Elischer 

On 16/9/17 9:40 pm, Sunpoet Po-Chuan Hsieh wrote:

On Sun, Sep 10, 2017 at 4:25 AM, Marcin Cieslak  wrote:


Hello,

in the past (before r414303[1])
[1] https://svnweb.freebsd.org/ports/head/www/npm/Makefile?view=
log=414303

npm had a couple of OPTIONS to select which node engine should be used.

Now this is all gone and replaced with

RUN_DEPENDS=node>=0.8.0:www/node


I am trying to build node-sass binaries for FreeBSD (I used to publish
them in the past)
and that requires running poudriere against multiple engines.

The following attempt to cheat does not help:

  poudriere bulk -j node4_10_3_i386 -p exp www/node4
textproc/node-sass

(textproc/node-sass is my custom port https://github.com/saper/ports
-exp/tree/master/textproc/node-sass)

since poudriere starts to build www/node4 and www/node in parallel.


Would that help if the npm dependency were changed to

RUN_DEPENDS=node:www/node

so that only existing executable is needed? How could I tell poudriere to
pick node4 first?

I used to maintain a private copy of the npm port with lots of OPTIONS and
this is a PITA.



I have separate poudriere jails for all architectures I have decided to
support:

$ poudriere jail -ln | grep ^node
node4_10_3_amd64
node4_10_3_i386
node6_10_3_amd64
node6_10_3_i386
node8_10_3_amd64
node8_10_3_i386

In the past those had OPTIONS set to pick a proper engine as a www/npm
dependency.


How to do it cleanly now?

Marcin


Hello,

I could add options for older node versions.
You could use these options to select different node versions for your
poudriere builds.

On the other hand, I'm planning a change for npm port.
It includes:
- Add slave ports of npm (e.g. npm-node4, npm-node6) for older node
versions.
- Remove www/npm{2,3,4}.

With this change, npm packages of different node version could be built by
FreeBSD cluster.

I'm looking forward to bhughes@'s comment.

Regards,
sunpoet

we use the npm 3 port at work with node 6
hopefully we will able to upgrade soon but please dont take them away yet.


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

Re: How to make www/npm pick www/node4 and www/node6 instead of www/node?

2017-09-16 Thread Adam Weinberger 
> On 16 Sep, 2017, at 7:40, Sunpoet Po-Chuan Hsieh  wrote:
> 
> On Sun, Sep 10, 2017 at 4:25 AM, Marcin Cieslak  wrote:
> 
>> Hello,
>> 
>> in the past (before r414303[1])
>> [1] https://svnweb.freebsd.org/ports/head/www/npm/Makefile?view=
>> log=414303
>> 
>> npm had a couple of OPTIONS to select which node engine should be used.
>> 
>> Now this is all gone and replaced with
>> 
>> RUN_DEPENDS=node>=0.8.0:www/node
>> 
>> 
>> I am trying to build node-sass binaries for FreeBSD (I used to publish
>> them in the past)
>> and that requires running poudriere against multiple engines.
>> 
>> The following attempt to cheat does not help:
>> 
>> poudriere bulk -j node4_10_3_i386 -p exp www/node4
>> textproc/node-sass
>> 
>> (textproc/node-sass is my custom port https://github.com/saper/ports
>> -exp/tree/master/textproc/node-sass)
>> 
>> since poudriere starts to build www/node4 and www/node in parallel.
>> 
>> 
>> Would that help if the npm dependency were changed to
>> 
>> RUN_DEPENDS=node:www/node
>> 
>> so that only existing executable is needed? How could I tell poudriere to
>> pick node4 first?
>> 
>> I used to maintain a private copy of the npm port with lots of OPTIONS and
>> this is a PITA.
>> 
>> 
>> 
>> I have separate poudriere jails for all architectures I have decided to
>> support:
>> 
>> $ poudriere jail -ln | grep ^node
>> node4_10_3_amd64
>> node4_10_3_i386
>> node6_10_3_amd64
>> node6_10_3_i386
>> node8_10_3_amd64
>> node8_10_3_i386
>> 
>> In the past those had OPTIONS set to pick a proper engine as a www/npm
>> dependency.
>> 
>> 
>> How to do it cleanly now?
>> 
>> Marcin
> 
> 
> Hello,
> 
> I could add options for older node versions.
> You could use these options to select different node versions for your
> poudriere builds.
> 
> On the other hand, I'm planning a change for npm port.
> It includes:
> - Add slave ports of npm (e.g. npm-node4, npm-node6) for older node
> versions.
> - Remove www/npm{2,3,4}.
> 
> With this change, npm packages of different node version could be built by
> FreeBSD cluster.
> 
> I'm looking forward to bhughes@'s comment.
> 
> Regards,
> sunpoet

I'd hold off on that for now, sunpoet. Either USES=node or subpackages (both in 
progress) will be viable alternatives soon. I'd wait and see if one of those 
does what you want first.

# Adam


-- 
Adam Weinberger
ad...@adamw.org
https://www.adamw.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"

Re: Extra Clang Tools

2017-09-16 Thread blubee blubeeme 
Howdy

I made a few changes to the devel/llvm40/Makefile and added pp-trace as the
last line of EXTRA_COMMANDS

Then I rebuilt llvm40, then I noticed that the pp-trace executable is
built, here's a output of the work directory grepping for pp-trace:
/usr/local/share/doc/llvm38/clang-tools/html/_sources/pp-trace.txt
/usr/local/share/doc/llvm38/clang-tools/html/pp-trace.html
/usr/local/share/doc/llvm39/clang-tools/html/_sources/pp-trace.txt
/usr/local/share/doc/llvm39/clang-tools/html/pp-trace.html
/usr/local/share/doc/llvm40/clang-tools/html/_sources/pp-trace.txt
/usr/local/share/doc/llvm40/clang-tools/html/pp-trace.html
/usr/ports/devel/llvm40/work/.build/bin/pp-trace
/usr/ports/devel/llvm40/work/.build/tools/clang/tools/extra/docs/_doctrees-html/pp-trace.doctree
/usr/ports/devel/llvm40/work/.build/tools/clang/tools/extra/docs/_doctrees-man/pp-trace.doctree
/usr/ports/devel/llvm40/work/.build/tools/clang/tools/extra/docs/html/_sources/pp-trace.txt
/usr/ports/devel/llvm40/work/.build/tools/clang/tools/extra/docs/html/pp-trace.html
/usr/ports/devel/llvm40/work/.build/tools/clang/tools/extra/pp-trace
/usr/ports/devel/llvm40/work/.build/tools/clang/tools/extra/pp-trace/CMakeFiles
/usr/ports/devel/llvm40/work/.build/tools/clang/tools/extra/pp-trace/CMakeFiles/pp-trace.dir
/usr/ports/devel/llvm40/work/.build/tools/clang/tools/extra/pp-trace/CMakeFiles/pp-trace.dir/PPCallbacksTracker.cpp.o
/usr/ports/devel/llvm40/work/.build/tools/clang/tools/extra/pp-trace/CMakeFiles/pp-trace.dir/PPTrace.cpp.o
/usr/ports/devel/llvm40/work/.build/tools/clang/tools/extra/pp-trace/cmake_install.cmake
/usr/ports/devel/llvm40/work/llvm-4.0.1.src/tools/clang/tools/extra/docs/pp-trace.rst
/usr/ports/devel/llvm40/work/llvm-4.0.1.src/tools/clang/tools/extra/pp-trace
/usr/ports/devel/llvm40/work/llvm-4.0.1.src/tools/clang/tools/extra/pp-trace/CMakeLists.txt
/usr/ports/devel/llvm40/work/llvm-4.0.1.src/tools/clang/tools/extra/pp-trace/PPCallbacksTracker.cpp
/usr/ports/devel/llvm40/work/llvm-4.0.1.src/tools/clang/tools/extra/pp-trace/PPCallbacksTracker.h
/usr/ports/devel/llvm40/work/llvm-4.0.1.src/tools/clang/tools/extra/pp-trace/PPTrace.cpp
/usr/ports/devel/llvm40/work/llvm-4.0.1.src/tools/clang/tools/extra/test/pp-trace
/usr/ports/devel/llvm40/work/llvm-4.0.1.src/tools/clang/tools/extra/test/pp-trace/Inputs
/usr/ports/devel/llvm40/work/llvm-4.0.1.src/tools/clang/tools/extra/test/pp-trace/Inputs/Level1A.h
/usr/ports/devel/llvm40/work/llvm-4.0.1.src/tools/clang/tools/extra/test/pp-trace/Inputs/Level1B.h
/usr/ports/devel/llvm40/work/llvm-4.0.1.src/tools/clang/tools/extra/test/pp-trace/Inputs/Level2A.h
/usr/ports/devel/llvm40/work/llvm-4.0.1.src/tools/clang/tools/extra/test/pp-trace/Inputs/Level2B.h
/usr/ports/devel/llvm40/work/llvm-4.0.1.src/tools/clang/tools/extra/test/pp-trace/Inputs/ModularizeList.txt
/usr/ports/devel/llvm40/work/llvm-4.0.1.src/tools/clang/tools/extra/test/pp-trace/Inputs/module.map
/usr/ports/devel/llvm40/work/llvm-4.0.1.src/tools/clang/tools/extra/test/pp-trace/pp-trace-conditional.cpp
/usr/ports/devel/llvm40/work/llvm-4.0.1.src/tools/clang/tools/extra/test/pp-trace/pp-trace-ident.cpp
/usr/ports/devel/llvm40/work/llvm-4.0.1.src/tools/clang/tools/extra/test/pp-trace/pp-trace-include.cpp
/usr/ports/devel/llvm40/work/llvm-4.0.1.src/tools/clang/tools/extra/test/pp-trace/pp-trace-macro.cpp
/usr/ports/devel/llvm40/work/llvm-4.0.1.src/tools/clang/tools/extra/test/pp-trace/pp-trace-modules.cpp
/usr/ports/devel/llvm40/work/llvm-4.0.1.src/tools/clang/tools/extra/test/pp-trace/pp-trace-pragma-general.cpp
/usr/ports/devel/llvm40/work/llvm-4.0.1.src/tools/clang/tools/extra/test/pp-trace/pp-trace-pragma-ms.cpp
/usr/ports/devel/llvm40/work/llvm-4.0.1.src/tools/clang/tools/extra/test/pp-trace/pp-trace-pragma-opencl.cpp
/usr/ports/devel/llvm40/work/stage/usr/local/share/doc/llvm40/clang-tools/html/_sources/pp-trace.txt
/usr/ports/devel/llvm40/work/stage/usr/local/share/doc/llvm40/clang-tools/html/pp-trace.html


So it now gets built but not installed; is it possible to have the port
updated to move these files to the proper after they are built?

I made a one line change to the Makefile:
# $FreeBSD: head/devel/llvm40/Makefile 449591 2017-09-10 20:55:38Z gerald $

EXTRAS_COMMANDS+= \
clang-apply-replacements \
clang-change-namespace \
clang-include-fixer \
clang-modernize \
clang-query \
clang-rename \
clang-reorder-fields \
clang-tidy \
find-all-symbols \
modularize \
pp-trace #===# My edit

Best

On Sat, Sep 16, 2017 at 2:01 PM, Shane Ambler  wrote:

> On 16/09/2017 11:59, blubee blubeeme wrote:
>
>> FreeBSD switched to clang as it's compiler some time ago; was clang extra
>> tools: http://clang.llvm.org/extra/index.html ever ported over?
>>
>> If yes, where is it located?
>>
>
> You will find them included in the llvm ports with EXTRAS enabled
>
> clang-tidy is in llvm 3.8+
> clang-include-fixer is in llvm 3.9+
> modularize is in llvm 3.8+
> pp-trace doesn't appear to exist
> clang-rename

Re: How to make www/npm pick www/node4 and www/node6 instead of www/node?

2017-09-16 Thread Sunpoet Po-Chuan Hsieh 
On Sun, Sep 10, 2017 at 4:25 AM, Marcin Cieslak  wrote:

> Hello,
>
> in the past (before r414303[1])
> [1] https://svnweb.freebsd.org/ports/head/www/npm/Makefile?view=
> log=414303
>
> npm had a couple of OPTIONS to select which node engine should be used.
>
> Now this is all gone and replaced with
>
> RUN_DEPENDS=node>=0.8.0:www/node
>
>
> I am trying to build node-sass binaries for FreeBSD (I used to publish
> them in the past)
> and that requires running poudriere against multiple engines.
>
> The following attempt to cheat does not help:
>
>  poudriere bulk -j node4_10_3_i386 -p exp www/node4
> textproc/node-sass
>
> (textproc/node-sass is my custom port https://github.com/saper/ports
> -exp/tree/master/textproc/node-sass)
>
> since poudriere starts to build www/node4 and www/node in parallel.
>
>
> Would that help if the npm dependency were changed to
>
> RUN_DEPENDS=node:www/node
>
> so that only existing executable is needed? How could I tell poudriere to
> pick node4 first?
>
> I used to maintain a private copy of the npm port with lots of OPTIONS and
> this is a PITA.
>
>
>
> I have separate poudriere jails for all architectures I have decided to
> support:
>
> $ poudriere jail -ln | grep ^node
> node4_10_3_amd64
> node4_10_3_i386
> node6_10_3_amd64
> node6_10_3_i386
> node8_10_3_amd64
> node8_10_3_i386
>
> In the past those had OPTIONS set to pick a proper engine as a www/npm
> dependency.
>
>
> How to do it cleanly now?
>
> Marcin


Hello,

I could add options for older node versions.
You could use these options to select different node versions for your
poudriere builds.

On the other hand, I'm planning a change for npm port.
It includes:
- Add slave ports of npm (e.g. npm-node4, npm-node6) for older node
versions.
- Remove www/npm{2,3,4}.

With this change, npm packages of different node version could be built by
FreeBSD cluster.

I'm looking forward to bhughes@'s comment.

Regards,
sunpoet
___
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: slrn from ports segfaults when running

2017-09-16 Thread Eugene Grosbein 
16.09.2017 8:46, tech-lists wrote:

> # gdb ./slrn ./slrn.core
> GNU gdb 6.1.1 [FreeBSD]
> Copyright 2004 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and
> you are
> welcome to change it and/or distribute copies of it under certain
> conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB.  Type "show warranty" for
> details.
> This GDB was configured as "amd64-marcel-freebsd"...
> Core was generated by ./slrn'.
> Program terminated with signal 11, Segmentation fault.
> Reading symbols from /usr/local/lib/libslang.so.2...done.
> Loaded symbols for /usr/local/lib/libslang.so.2
> Reading symbols from /usr/local/lib/libuu.so.3...done.
> Loaded symbols for /usr/local/lib/libuu.so.3
> Reading symbols from /usr/local/lib/libssl.so.43...done.
> Loaded symbols for /usr/local/lib/libssl.so.43
> Reading symbols from /usr/local/lib/libcrypto.so.41...done.
> Loaded symbols for /usr/local/lib/libcrypto.so.41
> Reading symbols from /usr/local/lib/libintl.so.8...done.
> Loaded symbols for /usr/local/lib/libintl.so.8
> Reading symbols from /lib/libncurses.so.8...Reading symbols from
> /usr/lib/debug//lib/libncurses.so.8.debug...done.
> done.
> Loaded symbols for /lib/libncurses.so.8
> Reading symbols from /lib/libc.so.7...Reading symbols from
> /usr/lib/debug//lib/libc.so.7.debug...done.
> done.
> Loaded symbols for /lib/libc.so.7
> Reading symbols from /lib/libm.so.5...Reading symbols from
> /usr/lib/debug//lib/libm.so.5.debug...done.
> done.
> Loaded symbols for /lib/libm.so.5
> Reading symbols from /usr/lib/i18n/libiconv_std.so.4...Reading symbols
> from /usr/lib/debug//usr/lib/i18n/libiconv_std.so.4.debug...done.
> done.
> Loaded symbols for /usr/lib/i18n/libiconv_std.so.4
> Reading symbols from /usr/lib/i18n/libmapper_serial.so.4...Reading
> symbols from
> /usr/lib/debug//usr/lib/i18n/libmapper_serial.so.4.debug...done.
> done.
> Loaded symbols for /usr/lib/i18n/libmapper_serial.so.4
> Reading symbols from /usr/lib/i18n/libmapper_none.so.4...Reading
> symbols from
> /usr/lib/debug//usr/lib/i18n/libmapper_none.so.4.debug...done.
> done.
> Loaded symbols for /usr/lib/i18n/libmapper_none.so.4
> Reading symbols from /usr/lib/i18n/libmapper_646.so.4...Reading
> symbols from
> /usr/lib/debug//usr/lib/i18n/libmapper_646.so.4.debug...done.
> done.
> Loaded symbols for /usr/lib/i18n/libmapper_646.so.4
> Reading symbols from /libexec/ld-elf.so.1...Reading symbols from
> /usr/lib/debug//libexec/ld-elf.so.1.debug...done.
> done.
> Loaded symbols for /libexec/ld-elf.so.1
> #0  _citrus_NONE_stdenc_mbtocs (ce=,csid= optimized out>, idx=0x7fffe870, s=0x7fffe868,n= optimized out>, ps=0x0, nresult=0x7fffe860,
> hooks=0x0)
>at /storage/usr/src/lib/libc/iconv/citrus_none.c:96
>96*idx = (_index_t)(unsigned char)*(*s)++;
>(gdb)
> backtrace:
> 
> (gdb) bt
> #0  _citrus_NONE_stdenc_mbtocs (ce=,csid= optimized out>, idx=0x7fffe870, s=0x7fffe868,n= optimized out>, ps=0x0, nresult=0x7fffe860,
> hooks=0x0)
>at /storage/usr/src/lib/libc/iconv/citrus_none.c:96

You could try to remove --with-non-gnu-iconv from port's Makefile
and rebuild slrn. Any way, you better fill a PR attaching this debugging output
you already collected.

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

INDEX now builds successfully on 10.x

2017-09-16 Thread Ports Index build 

___
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: Extra Clang Tools

2017-09-16 Thread Dimitry Andric 
On 16 Sep 2017, at 04:29, blubee blubeeme  wrote:
> 
> FreeBSD switched to clang as it's compiler some time ago; was clang extra
> tools: http://clang.llvm.org/extra/index.html ever ported over?
> 
> If yes, where is it located?

Those tools (clang-tidy, clang-include-fixer, etc) are not available in
the base system.  Install one of the devel/llvm ports, and enable the
EXTRAS option.

-Dimitry



signature.asc
Description: Message signed with OpenPGP

INDEX build failed for 10.x

2017-09-16 Thread Ports Index build 
INDEX build failed with errors:
Generating INDEX-10 - please wait..--- describe.accessibility ---
--- describe.arabic ---
--- describe.archivers ---
--- describe.astro ---
--- describe.audio ---
--- describe.benchmarks ---
--- describe.biology ---
--- describe.cad ---
--- describe.chinese ---
--- describe.comms ---
--- describe.converters ---
--- describe.databases ---
--- describe.deskutils ---
--- describe.devel ---
--- describe.dns ---
--- describe.editors ---
--- describe.emulators ---
--- describe.finance ---
--- describe.french ---
--- describe.ftp ---
[...]
--- describe.print ---
--- describe.russian ---
--- describe.science ---
--- describe.security ---
--- describe.shells ---
--- describe.sysutils ---
--- describe.textproc ---
--- describe.ukrainian ---
--- describe.vietnamese ---
--- describe.www ---
--- describe.x11 ---
--- describe.x11-clocks ---
--- describe.x11-drivers ---
--- describe.x11-fm ---
--- describe.x11-fonts ---
--- describe.x11-servers ---
--- describe.x11-themes ---
--- describe.x11-toolkits ---
--- describe.x11-wm ---
 Done.
make_index: /home/indexbuild/tindex/ports/misc/kdeutils4: no entry for 
/home/indexbuild/tindex/ports/sysutils/filelight-kde4

Committers on the hook:
 gerald olgeni sunpoet tcberner 

Most recent SVN update was:
Updating '.':
Udevel/rubygem-aws-sdk-core/Makefile
Udevel/rubygem-aws-sdk-core/distinfo
Udevel/py-pytest-mock/Makefile
Udevel/py-pytest-mock/distinfo
Udevel/py-twilio/Makefile
Udevel/py-twilio/distinfo
Uwww/py-planet/Makefile
Uwww/py-planet/distinfo
Umath/py-numexpr/Makefile
Umath/py-numexpr/distinfo
Usecurity/keybase/Makefile
Usecurity/keybase/distinfo
Ulang/gcc6-devel/Makefile
Ulang/gcc6-devel/distinfo
Ulang/gcc5-aux/Makefile
UMOVED
Dsysutils/filelight-kde4
Usysutils/Makefile
Asysutils/filelight
Asysutils/filelight/Makefile
Asysutils/filelight/distinfo
Asysutils/filelight/pkg-plist
Asysutils/filelight/pkg-descr
Updated to revision 449952.
___
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 you maintain which are out of date

2017-09-16 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, you can
safely ignore the entry.

You will not be e-mailed again for any of the port/version combinations
below.

Full details can be found at the following URL:
http://portscout.freebsd.org/po...@freebsd.org.html


Port| Current version | New version
+-+
science/gromacs | 5.0.6   | 2016.4
+-+


If any of the above results are invalid, please check the following page
for details on how to improve portscout's detection and selection of
distfiles on a per-port basis:

http://portscout.freebsd.org/info/portscout-portconfig.txt

Thanks.
___
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: synth install ... builds but does not always install named packages

2017-09-16 Thread Thomas Mueller 
> On 16 September 2017 at 09:01, Thomas Mueller  wrote:
> > Some of the packages not installed are widespread build dependencies, such 
> > as nasm, and are better installed than rebuilt or temporarily reinstalled 
> > every time.

> synth doesn't rebuild build-dependencies if it isn't required. It
> stores the dependancies as a packages in the local package repository
> and unpacks it for each build. In fact, there is no need to install
> build dependancies on your local system, as it will *never* get used
> by synth, as synth uses a clean chroot'd environment for all its
> builds.

> [...]
> > And then it was irritating when some specifically named packages were not 
> > installed (math/gnumeric, editors/abiword-docs, mail/metamail, for 
> > instance).

> I would check:
>  1. did the packages get built, and are present in the local package 
> repository.
>  2. what sort of error messages you are getting from just a "pkg
> install ${package}" from the local package repo.

> Cheers.

> Jonathan Chen 


Those packages that were built but not installed appeared in 
/var/synth/live-packages/All , otherwise I would not have complained about 
failure to install.

I didn't "pkg install ${package}" from local package repo, I installed some by 
rerunning "synth install category/package" (using actual category/package 
names).

I see also that graphics/epdfview built but didn't install, don't remember if I 
named this port, but would like to install it now.  Maybe also graphics/evince.

I still want to install build dependencies, or at least some of them, to be 
able to cross-compile Haiku and Linux toolchains (such as buildroot, OpenWRT, 
crosstool-ng, Pengutronix ptxdist and Cross Linux Fom Scratch).

Their advice about host build system requirements guides me on what I need to 
be installed, since this is out of synth territory, out of FreeBSD ports 
territory.

Tom

___
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: Extra Clang Tools

2017-09-16 Thread Shane Ambler 

On 16/09/2017 11:59, blubee blubeeme wrote:

FreeBSD switched to clang as it's compiler some time ago; was clang extra
tools: http://clang.llvm.org/extra/index.html ever ported over?

If yes, where is it located?


You will find them included in the llvm ports with EXTRAS enabled

clang-tidy is in llvm 3.8+
clang-include-fixer is in llvm 3.9+
modularize is in llvm 3.8+
pp-trace doesn't appear to exist
clang-rename is in llvm 3.8+
clangd is in llvm-devel (5.0)

Note that llvm ports append the version to the app name - they can be
found in /usr/local/bin and /usr/local/llvm-/bin/

Building base WITH_CLANG_EXTRAS offers a different set of extras which
are also in the llvm ports.
As listed in 11-STABLE from /usr/src/usr.bin/clang/Makefile

bugpoint clang-format llc lli llvm-ar llvm-as llvm-bcanalyzer llvm-cov
llvm-cxxdump llvm-cxxfilt llvm-diff llvm-dis llvm-dwarfdump llvm-extract
llvm-link llvm-lto llvm-lto2 llvm-mc llvm-modextract llvm-nm
llvm-pdbdump llvm-profdata llvm-rtdyld llvm-symbolizer llvm-xray opt


--
FreeBSD - the place to B...Software Developing

Shane Ambler

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