Re: How to stop ports recompiling gcc, llvm, etc.?

[Kevin Oberman]

On Tue, Jun 13, 2017 at 3:07 PM, Rastko P  wrote:

> I used the portsnap fetch>extract>fetch>update
>
> then built portmaster,
>
> then used pkg version -l "<", which gave 2 out-of-date,
>
> then used portmaster -L, which gave 2 matching out-of-date,
>
> then used portmaster -a to update all ports, which pulled in a lot of
>
> dependencies, including llvm, cairo, openjdk, etc.
>
> then used 'df', just to find out not much space has been taken,
>
> then used postmaster --clean-distfiles,
>
> then used pkg clean (-a),
>
> then did some pkg and portsnap updates again, so forth.
>
>
> The compilation of thunderbird52.1.1 has stopped with an error
>
> mentioning a void reference, AFAIR, and I used make only, not make install,
>
> however, I am left with gcc5 installed, 2 versions of llvm installed, etc.
>
>
> Here's some output from pkg:
>
>
> Manually installed packages
>
> #
>
>
> $ pkg query -e '%a = 0' %o
> security/openssh-askpass
> ports-mgmt/dialog4ports
> misc/freebsd-doc-en
> www/firefox
> www/firefox-i18n
> security/gnome-ssh-askpass
> x11/gnome3
> editors/nano
> ports-mgmt/pkg
> ports-mgmt/portmaster
> lang/python
> lang/python36
> misc/freebsd-doc-sr
> security/sudo
> mail/thunderbird
> mail/thunderbird-i18n
> x11-fonts/urwfonts
> multimedia/vlc-qt4
> security/xca
> x11-drivers/xf86-video-intel
> x11/xorg
> graphics/xpdf
>
>
> Devel/Lang category automatically installed with -N dependencies at the end
>
> ##
>
>
> $ pkg query -e '%a = 1 && %o ~ lang* || %o ~ devel* && %#r > 0' %o-%#r |
> sort
> devel/autoconf-1
> devel/autoconf-wrapper-2
> devel/automake-wrapper-1
> devel/binutils-1
> devel/boehm-gc-2
> devel/boehm-gc-threaded-1
> devel/boost-libs-2
> devel/cmake-modules-1
> devel/dbus-20
> devel/dbus-glib-30
> devel/dconf-5
> devel/dconf-editor-1
> devel/desktop-file-utils-24
> devel/dotconf-2
> devel/gamin-1
> devel/gconf2-7
> devel/gettext-runtime-301
> devel/gettext-tools-2
> devel/glib20-255
> devel/glibmm-7
> devel/gobject-introspection-18
> devel/gsettings-desktop-schemas-15
> devel/gstreamer1-plugins-soup-1
> devel/gvfs-6
> devel/icu-9
>
> devel/json-glib-14
> devel/jsoncpp-1
> devel/libdaemon-1
> devel/libedit-3
> devel/libevent-2
> devel/libffi-13
> devel/libgdata-7
> devel/libgee-7
> devel/libgit2-1
> devel/libgit2-glib-1
> devel/libglade2-3
> devel/libgsf-27
> devel/libgtop-4
> devel/libical-2
> devel/libIDL-9
> devel/libinotify-1
> devel/libltdl-9
> devel/libnotify-15
> devel/libpciaccess-4
> devel/libpeas-7
> devel/libpthread-stubs-1
> devel/librest-5
> devel/libsigc++20-8
> devel/libsoup-17
> devel/libsoup-gnome-8
> devel/libunistring-4
> devel/libunwind-1
> devel/libuv-1
> devel/libvolume_id-1
> devel/llvm39-2
>
> devel/lua-bitop-1
> devel/lua-lpeg-1
> devel/m4-5
> devel/npth-1
> devel/nspr-9
> devel/ORBit2-8
> devel/orc-36
> devel/p5-Locale-gettext-1
> devel/pcre-3
> devel/popt-2
> devel/ptlib-1
> devel/py-babel-2
> devel/py-cffi-1
> devel/py-dbus-5
> devel/py-enum34-2
> devel/py-gobject-5
> devel/py-gobject3-6
> devel/py-iso8601-1
> devel/py-Jinja2-1
> devel/py-libpeas-1
> devel/py-notify-1
> devel/py-pyasn1-1
> devel/py-pycparser-1
> devel/py-pytz-1
> devel/py-six-4
> devel/py-xdg-1
> devel/py27-setuptools-29
> devel/py3-dbus-2
> devel/py3-gobject3-6
> devel/py3-libpeas-3
>
> devel/py3-xdg-2
> devel/py35-setuptools-1
> devel/pydbus-common-2
> devel/pygobject3-common-2
> devel/qt4-corelib-2
> devel/readline-11
> devel/sdl12-2
> devel/spice-protocol-1
> devel/talloc-3
> devel/tevent-2
> devel/xdg-utils-2
> lang/gcc-ecj45-1
> lang/gcc5-0
> lang/gjs-7
> lang/guile2-1
> lang/lua52-11
> lang/perl5.24-23
> lang/python2-31
> lang/python27-76
> lang/python3-14
> lang/python35-17
> lang/spidermonkey170-1
> lang/spidermonkey24-1
> lang/vala-1
>
>
>
> On 13.06.2017 20:09, Kevin Oberman wrote:
> > On Tue, Jun 13, 2017 at 9:19 AM, Rastko P  > > wrote:
> >
> > Nope, none of those, funny as it may sound, I was going by the
> > "Handbook" and tried to use "portmaster", as it reported some
> > upgradeable 'ports'.
> >
> > However, that was the first  time I launched portmaster, and it was
> > weird, because it kept prompting me to delete newer versions of
> > software
> > than that which had been built by the portmaster session, to which I
> > replied 'oh, no [n]o', which was the default.
> >
> > But in the end, it seems to have not installed anything (?!). Why
> > did it
> > pull in all those dependencies? Where are the binaries?
> >
> >
> > On 13.06.2017 17:54, Lowell Gilbert wrote:
> > > Rastko P >
> > writes:
> > >
> > >> I have a fresh 11-RELEASE dist. I am 'bootstrapping' the
> > environment.
> > >>
> > >> I am in the process of building mail/thunderbird-52.1.1,
> > because the
> > >> binary doesn't have support for 

Re: Synth: copying installation to second computer

[Jonathan Chen]

On 14 June 2017 at 10:51, Thomas Mueller  wrote:

> I think my main concern is getting packages into a synth-recognized 
> repository.
>
> I would use NFS rather than http.  I would need to be sure to disable 
> freebsd.org server in the conf, think I just did, now need to check on the 
> other computer.
>
> I don't really want to have to rebuild synth and dependencies redundantly 
> after all are installed on first build-host computer.
>
> But I would want to use synth on either computer without depending on the 
> other computer; what I am concerned with now is getting started.

The synth repository is just the standard pkg-repository(5), based (by
default) at /var/synth/live_packages. As long as you're using the same
architecture and the same /usr/ports tree, you should be okay. YMMV.

Cheers.
-- 
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: Synth: copying installation to second computer

[Thomas Mueller]

> On 13 June 2017 at 18:01, Thomas Mueller  wrote:

> > I just managed to install (first part) ports-mgmt/synth on FreeBSD 
> > 11.1-PRERELEASE amd64, using portmaster after deleting all packages except 
> > pkg and portmaster.  Those old packages were no good anyway due to shared 
> > libraaries being out of sync.

> >  Now I want to convert packages to synth repository format and copy this 
> > installation to another computer with same FreeBSD 11.1-PRERELEASE using 
> > NFS, doing as little recompilation as possible.

> >  This is my first (partway) success after an attempt to build synth on 
> > FreeBSD-CURRENT amd64, before ino64, was stopped by a system crash and 
> > reboot while I was sleeping.

> > I looked through README.md and man synth, but there are still some hazy 
> > points.  Or is it easier than I think?

> The thing to note is that ports-mgmt/synth is a repository builder.
> Coming from portupgrade or portmaster, a user may think that it is
> rebuilding too many packages for a simple port change, but what it is
> doing is verifying that the chain of construction for each port is
> working as expected. The first build is always going to be long, but
> will do concurrent builds as much as it much as possible.

> Once you have a complete repo on one of your machines, you can simply
> serve up the /var/synth/live_packages using www/apache24 or even ssh.
> On each of the remote hosts, all you have to do is to add a
> /usr/local/etc/pkg/repos/my-local-repo.conf entry, eg:
#
> # Locally built packages
#
> localrepo: {
>   url  : http://my-build-host/live_packages,
>   priority : 20,
>   enabled  : yes,
}

> And then you're good to go with "pkg upgrade -r localrepo" on each of
> the remote hosts.

> Cheers.

> Jonathan Chen

I think my main concern is getting packages into a synth-recognized repository.

I would use NFS rather than http.  I would need to be sure to disable 
freebsd.org server in the conf, think I just did, now need to check on the 
other computer.

I don't really want to have to rebuild synth and dependencies redundantly after 
all are installed on first build-host computer.

But I would want to use synth on either computer without depending on the other 
computer; what I am concerned with now is getting started.

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: How to stop ports recompiling gcc, llvm, etc.?

[Rastko P]

I used the portsnap fetch>extract>fetch>update

then built portmaster,

then used pkg version -l "<", which gave 2 out-of-date,

then used portmaster -L, which gave 2 matching out-of-date,

then used portmaster -a to update all ports, which pulled in a lot of

dependencies, including llvm, cairo, openjdk, etc.

then used 'df', just to find out not much space has been taken,

then used postmaster --clean-distfiles,

then used pkg clean (-a),

then did some pkg and portsnap updates again, so forth.


The compilation of thunderbird52.1.1 has stopped with an error

mentioning a void reference, AFAIR, and I used make only, not make install,

however, I am left with gcc5 installed, 2 versions of llvm installed, etc.


Here's some output from pkg:


Manually installed packages

#


$ pkg query -e '%a = 0' %o
security/openssh-askpass
ports-mgmt/dialog4ports
misc/freebsd-doc-en
www/firefox
www/firefox-i18n
security/gnome-ssh-askpass
x11/gnome3
editors/nano
ports-mgmt/pkg
ports-mgmt/portmaster
lang/python
lang/python36
misc/freebsd-doc-sr
security/sudo
mail/thunderbird
mail/thunderbird-i18n
x11-fonts/urwfonts
multimedia/vlc-qt4
security/xca
x11-drivers/xf86-video-intel
x11/xorg
graphics/xpdf


Devel/Lang category automatically installed with -N dependecies at the end

##


$ pkg query -e '%a = 1 && %o ~ lang* || %o ~ devel* && %#r > 0' %o-%#r |
sort
devel/autoconf-1
devel/autoconf-wrapper-2
devel/automake-wrapper-1
devel/binutils-1
devel/boehm-gc-2
devel/boehm-gc-threaded-1
devel/boost-libs-2
devel/cmake-modules-1
devel/dbus-20
devel/dbus-glib-30
devel/dconf-5
devel/dconf-editor-1
devel/desktop-file-utils-24
devel/dotconf-2
devel/gamin-1
devel/gconf2-7
devel/gettext-runtime-301
devel/gettext-tools-2
devel/glib20-255
devel/glibmm-7
devel/gobject-introspection-18
devel/gsettings-desktop-schemas-15
devel/gstreamer1-plugins-soup-1
devel/gvfs-6
devel/icu-9

devel/json-glib-14
devel/jsoncpp-1
devel/libdaemon-1
devel/libedit-3
devel/libevent-2
devel/libffi-13
devel/libgdata-7
devel/libgee-7
devel/libgit2-1
devel/libgit2-glib-1
devel/libglade2-3
devel/libgsf-27
devel/libgtop-4
devel/libical-2
devel/libIDL-9
devel/libinotify-1
devel/libltdl-9
devel/libnotify-15
devel/libpciaccess-4
devel/libpeas-7
devel/libpthread-stubs-1
devel/librest-5
devel/libsigc++20-8
devel/libsoup-17
devel/libsoup-gnome-8
devel/libunistring-4
devel/libunwind-1
devel/libuv-1
devel/libvolume_id-1
devel/llvm39-2

devel/lua-bitop-1
devel/lua-lpeg-1
devel/m4-5
devel/npth-1
devel/nspr-9
devel/ORBit2-8
devel/orc-36
devel/p5-Locale-gettext-1
devel/pcre-3
devel/popt-2
devel/ptlib-1
devel/py-babel-2
devel/py-cffi-1
devel/py-dbus-5
devel/py-enum34-2
devel/py-gobject-5
devel/py-gobject3-6
devel/py-iso8601-1
devel/py-Jinja2-1
devel/py-libpeas-1
devel/py-notify-1
devel/py-pyasn1-1
devel/py-pycparser-1
devel/py-pytz-1
devel/py-six-4
devel/py-xdg-1
devel/py27-setuptools-29
devel/py3-dbus-2
devel/py3-gobject3-6
devel/py3-libpeas-3

devel/py3-xdg-2
devel/py35-setuptools-1
devel/pydbus-common-2
devel/pygobject3-common-2
devel/qt4-corelib-2
devel/readline-11
devel/sdl12-2
devel/spice-protocol-1
devel/talloc-3
devel/tevent-2
devel/xdg-utils-2
lang/gcc-ecj45-1
lang/gcc5-0
lang/gjs-7
lang/guile2-1
lang/lua52-11
lang/perl5.24-23
lang/python2-31
lang/python27-76
lang/python3-14
lang/python35-17
lang/spidermonkey170-1
lang/spidermonkey24-1
lang/vala-1



On 13.06.2017 20:09, Kevin Oberman wrote:
> On Tue, Jun 13, 2017 at 9:19 AM, Rastko P  > wrote:
>
> Nope, none of those, funny as it may sound, I was going by the
> "Handbook" and tried to use "portmaster", as it reported some
> upgradeable 'ports'.
>
> However, that was the first  time I launched portmaster, and it was
> weird, because it kept prompting me to delete newer versions of
> software
> than that which had been built by the portmaster session, to which I
> replied 'oh, no [n]o', which was the default.
>
> But in the end, it seems to have not installed anything (?!). Why
> did it
> pull in all those dependencies? Where are the binaries?
>
>
> On 13.06.2017 17:54, Lowell Gilbert wrote:
> > Rastko P >
> writes:
> >
> >> I have a fresh 11-RELEASE dist. I am 'bootstrapping' the
> environment.
> >>
> >> I am in the process of building mail/thunderbird-52.1.1,
> because the
> >> binary doesn't have support for Lightning calendar extension.
> >>
> >> Yesterday, a documentation port build pulled in a lot of
> dependencies,
> >> including GCC, LLVM, and a lot of others. 6+ hours of compile-time.
> >>
> >> After it finished I immediately issued a 'df' cmd, and
> lo-and-behold,
> >> not more than 1GB was taken by the build process. Now that you've
> >> mentioned it, pkg says GCC or LLVM are not to be found
> installed. I am
> >> missing 

anyone can work on /usr/ports/Mk/*

[René Ladan]

Hi,

this is a reminder that you do not have to be in portmgr@ or be a ports
committer to be able to work on /usr/ports/Mk/* . So if you have an
idea, fix, or other patch, feel free to send in a PR [1] or open a
review [2]. Some files in /usr/ports/Mk/ (like bsd.port.mk) do however
require portmgr@ approval for committing to.

[1] https://bugs.freebsd.org/bugzilla/
[2] https://reviews.freebsd.org/

René on behalf of portmgr@



signature.asc
Description: OpenPGP digital signature

12.0-current 'fstat' problem [ workaround in place... ]

[Jeffrey Bouquet via freebsd-ports]

Many ports newly report 'fstat' and refuse to run, and as many don't build 
until I
get around to a buildworld cycle, the workaround is to run v11 pkg 
pkg install -f ...
 on this v12 system, then lock the new port from being re-from-package
or re-built 
..
 Otoh, some like sqlite3 do build, but also have to be locked so they don't
revert to packaging upstream, as in WHERE IS THE  FILE some file somwhere
makes locally built ports freebsd:..v11  ABI rather than the actual uname,
v12.0-CURRENT. 
.
  A... some one /usr/src/usr.bin or something,  or a /lib/ equivalent, that
can be reinstalled singly to omit the fstat error.
  B... another whole problem, why are ports v11 ABI when built on a
ABI machine of v12


  Hoping procedures for this type of breakage are documented in the future
both for these and for other similar problems, such as in a new file
/usr/src/PKG-UPDATING , and a companion /usr/ports/PKG-UPDATING
or some such file more ad-hoc readable without a browser, as in the
wiki... [ for instance the main browser here broke til I installed just within
a few days ago, the v11 gnutls txz ... pkg install -f ... and then locked gnutls
IIRC. ] 
..
___
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 stop ports recompiling gcc, llvm, etc.?

[Kevin Oberman]

On Tue, Jun 13, 2017 at 9:19 AM, Rastko P  wrote:

> Nope, none of those, funny as it may sound, I was going by the
> "Handbook" and tried to use "portmaster", as it reported some
> upgradeable 'ports'.
>
> However, that was the first  time I launched portmaster, and it was
> weird, because it kept prompting me to delete newer versions of software
> than that which had been built by the portmaster session, to which I
> replied 'oh, no [n]o', which was the default.
>
> But in the end, it seems to have not installed anything (?!). Why did it
> pull in all those dependencies? Where are the binaries?
>
>
> On 13.06.2017 17:54, Lowell Gilbert wrote:
> > Rastko P  writes:
> >
> >> I have a fresh 11-RELEASE dist. I am 'bootstrapping' the environment.
> >>
> >> I am in the process of building mail/thunderbird-52.1.1, because the
> >> binary doesn't have support for Lightning calendar extension.
> >>
> >> Yesterday, a documentation port build pulled in a lot of dependencies,
> >> including GCC, LLVM, and a lot of others. 6+ hours of compile-time.
> >>
> >> After it finished I immediately issued a 'df' cmd, and lo-and-behold,
> >> not more than 1GB was taken by the build process. Now that you've
> >> mentioned it, pkg says GCC or LLVM are not to be found installed. I am
> >> missing something huge here.
> > Are you using synth, or poudriere? A normal port build would leave those
> > things installed if it needed them at build time.
>

What command are you using? Specifically, what options are you using with
portmaster? Are you installing from /usr/ports? Installing into /usr/local?

Clearly, something odd is going on. While building llvm is big, I don't
have to do it very often. Only when the port, itself, is updated. Anything
in you environment that might be unexpected?

When you run portmaster, you should get a list of ports to be installed and
a request for confirmation that you want to proceed. Are you seeing this?
Or, is the build of the port triggering the rebuild of the compiler.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
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 stop ports recompiling gcc, llvm, etc.?

[Rastko P]

Nope, none of those, funny as it may sound, I was going by the
"Handbook" and tried to use "portmaster", as it reported some
upgradeable 'ports'.

However, that was the first  time I launched portmaster, and it was
weird, because it kept prompting me to delete newer versions of software
than that which had been built by the portmaster session, to which I
replied 'oh, no [n]o', which was the default. 

But in the end, it seems to have not installed anything (?!). Why did it
pull in all those dependencies? Where are the binaries?





On 13.06.2017 17:54, Lowell Gilbert wrote:
> Rastko P  writes:
>
>> I have a fresh 11-RELEASE dist. I am 'bootstrapping' the environment.
>>
>> I am in the process of building mail/thunderbird-52.1.1, because the
>> binary doesn't have support for Lightning calendar extension.
>>
>> Yesterday, a documentation port build pulled in a lot of dependencies,
>> including GCC, LLVM, and a lot of others. 6+ hours of compile-time.
>>
>> After it finished I immediately issued a 'df' cmd, and lo-and-behold,
>> not more than 1GB was taken by the build process. Now that you've
>> mentioned it, pkg says GCC or LLVM are not to be found installed. I am
>> missing something huge here.
> Are you using synth, or poudriere? A normal port build would leave those
> things installed if it needed them at build time.

___
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 stop ports recompiling gcc, llvm, etc.?

[Lowell Gilbert]

Rastko P  writes:

> I have a fresh 11-RELEASE dist. I am 'bootstrapping' the environment.
>
> I am in the process of building mail/thunderbird-52.1.1, because the
> binary doesn't have support for Lightning calendar extension.
>
> Yesterday, a documentation port build pulled in a lot of dependencies,
> including GCC, LLVM, and a lot of others. 6+ hours of compile-time.
>
> After it finished I immediately issued a 'df' cmd, and lo-and-behold,
> not more than 1GB was taken by the build process. Now that you've
> mentioned it, pkg says GCC or LLVM are not to be found installed. I am
> missing something huge here.

Are you using synth, or poudriere? A normal port build would leave those
things installed if it needed them at build time.
___
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 stop ports recompiling gcc, llvm, etc.?

[Eugene Grosbein]

13.06.2017 22:25, Rastko P пишет:
> I have some experience with FreeBSD. I don't mind building ports. You
> know sometimes it's necessary (most FreeBSD software is ported, and
> needs to be configured)
> 
> 
> But I cannot find in the documentation how to prevent a port
> re-compiling different versions of GCC or other such monsters, when I
> already compiled them.

Port build process won't rebuild a compiler if it is already built and 
installed.
You'll get no definite answer until you supply details such as port you need in 
first place
and at least the beginning of its building log.


___
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 stop ports recompiling gcc, llvm, etc.?

[Rastko P]

Hi Eugene,

I have a fresh 11-RELEASE dist. I am 'bootstrapping' the environment.

I am in the process of building mail/thunderbird-52.1.1, because the
binary doesn't have support for Lightning calendar extension.

Yesterday, a documentation port build pulled in a lot of dependencies,
including GCC, LLVM, and a lot of others. 6+ hours of compile-time.

After it finished I immediately issued a 'df' cmd, and lo-and-behold,
not more than 1GB was taken by the build process. Now that you've
mentioned it, pkg says GCC or LLVM are not to be found installed. I am
missing something huge here.

Cheers.



On 13.06.2017 17:33, Eugene Grosbein wrote:
> 13.06.2017 22:25, Rastko P пишет:
>> I have some experience with FreeBSD. I don't mind building ports. You
>> know sometimes it's necessary (most FreeBSD software is ported, and
>> needs to be configured)
>>
>>
>> But I cannot find in the documentation how to prevent a port
>> re-compiling different versions of GCC or other such monsters, when I
>> already compiled them.
> Port build process won't rebuild a compiler if it is already built and 
> installed.
> You'll get no definite answer until you supply details such as port you need 
> in first place
> and at least the beginning of its building log.
>
>

___
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 stop ports recompiling gcc, llvm, etc.?

[Rastko P]

I have some experience with FreeBSD. I don't mind building ports. You
know sometimes it's necessary (most FreeBSD software is ported, and
needs to be configured)


But I cannot find in the documentation how to prevent a port
re-compiling different versions of GCC or other such monsters, when I
already compiled them.


Any clear-cut solutions?


I know you can install binary packages, that is not relevant to my
question, unless you are being somewhat cynical.


On 13.06.2017 17:05, Dimitry Andric wrote:
> On 13 Jun 2017, at 15:51, Rastko P  wrote:
>> I think my machine will die from severe dehydration if every other port
>> keeps recompiling compilers.
>>
>> The last make for the "documentation translation" port took 6 hours or
>> more.  What's that in fan oil costs?
>>
>>
>> How to prevent this?
> Install binary packages.
>
> -Dimitry
>

___
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 stop ports recompiling gcc, llvm, etc.?

[Dimitry Andric]

On 13 Jun 2017, at 15:51, Rastko P  wrote:
> 
> I think my machine will die from severe dehydration if every other port
> keeps recompiling compilers.
> 
> The last make for the "documentation translation" port took 6 hours or
> more.  What's that in fan oil costs?
> 
> 
> How to prevent this?

Install binary packages.

-Dimitry



signature.asc
Description: Message signed with OpenPGP

Re: svnup is b0rken!

[Maxim Sobolev]

P.S. John, the patch does fix it indeed, thanks!

On Tue, Jun 13, 2017 at 7:51 AM, Maxim Sobolev  wrote:

> John, should I drop this into the port as a patch? Approved by: maintainer?
>
> -Max
>
> On Mon, Jun 12, 2017 at 4:10 PM, John Mehr  wrote:
>
>> Hello,
>>
>> It looks like the latest version of Subversion has become more strict
>> with regards to CR+LFs and the attached patch should get things working for
>> you again.  Please give it a try and let me know how it goes.
>>
>> I've got a couple other fixes I'm working on and I'm hoping to have 1.08
>> rolled out in the next week or so.  I used to host the tarball on my
>> personal web server (which due to an ISP change is no longer available) and
>> I'm looking into finding a new place to host it (probably github).
>>
>> On Mon, Jun 12, 2017 at 1:03 PM, Maxim Sobolev 
>> wrote:
>>
>>> Hi, latest version of the svnup package is broken on several of my
>>> boxes. I've tried few public svn mirrors makes no difference.
>>>
>>> -Max
>>>
>>> [sobomax@van01 ~/projects/softswitch]$ svnup ports
>>> # Revision: 443456
>>>
>>> Command Failure: HTTP/1.1 400 Bad Request
>>> Date: Mon, 12 Jun 2017 18:01:09 GMT
>>> Server: Apache
>>> Connection: close
>>> Content-Type: text/html; charset=iso-8859-1
>>>
>>> 
>>> 
>>> 400 Bad Request
>>> 
>>> Bad Request
>>> Your browser sent a request that this server could not understand.>> />
>>> 
>>> 
>>>
>>>
>>
>>
>> --
>> John Mehr
>> Software Developer / Database Administrator
>> Humphrey School of Public Affairs, University of Minnesota
>>
>
>


-- 
Maksym Sobolyev
Sippy Software, Inc.
Internet Telephony (VoIP) Experts
Tel (Canada): +1-778-783-0474
Tel (Toll-Free): +1-855-747-7779
Fax: +1-866-857-6942
Web: http://www.sippysoft.com
MSN: sa...@sippysoft.com
Skype: SippySoft
___
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: svnup is b0rken!

[Maxim Sobolev]

John, should I drop this into the port as a patch? Approved by: maintainer?

-Max

On Mon, Jun 12, 2017 at 4:10 PM, John Mehr  wrote:

> Hello,
>
> It looks like the latest version of Subversion has become more strict with
> regards to CR+LFs and the attached patch should get things working for you
> again.  Please give it a try and let me know how it goes.
>
> I've got a couple other fixes I'm working on and I'm hoping to have 1.08
> rolled out in the next week or so.  I used to host the tarball on my
> personal web server (which due to an ISP change is no longer available) and
> I'm looking into finding a new place to host it (probably github).
>
> On Mon, Jun 12, 2017 at 1:03 PM, Maxim Sobolev 
> wrote:
>
>> Hi, latest version of the svnup package is broken on several of my boxes.
>> I've tried few public svn mirrors makes no difference.
>>
>> -Max
>>
>> [sobomax@van01 ~/projects/softswitch]$ svnup ports
>> # Revision: 443456
>>
>> Command Failure: HTTP/1.1 400 Bad Request
>> Date: Mon, 12 Jun 2017 18:01:09 GMT
>> Server: Apache
>> Connection: close
>> Content-Type: text/html; charset=iso-8859-1
>>
>> 
>> 
>> 400 Bad Request
>> 
>> Bad Request
>> Your browser sent a request that this server could not understand.> />
>> 
>> 
>>
>>
>
>
> --
> John Mehr
> Software Developer / Database Administrator
> Humphrey School of Public Affairs, University of Minnesota
>
___
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"

How to stop ports recompiling gcc, llvm, etc.?

[Rastko P]

I think my machine will die from severe dehydration if every other port
keeps recompiling compilers.

The last make for the "documentation translation" port took 6 hours or
more.  What's that in fan oil costs?


How to prevent 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: problem about port need /proc to build

[Jov]

It is not the NEW PORT need /proc, it is the tool used to build the port
need /proc, which is bazel.And I know the /proc is not the way FreeBSD to
do it and I really do not like it.

Anyway ,I submitted a patch to bazel to use procstat_getpathname replace
the /proc method: https://github.com/bazelbuild/bazel/pull/3179

2017-06-13 20:04 GMT+08:00 Konstantin Belousov :

> On Tue, Jun 13, 2017 at 06:57:40PM +0800, Jov wrote:
> > Hi ports hackers,
> >
> > I am porting tensorflow to FreeBSD, It uses bazel to manage the
> > dependencies and do the build.The port work now is mostly done (see:
> > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219609,I have local
> patch
> > to fix the network need for do-configure) except one problem which I am
> not
> > sure. So I write this mail to ask.
> >
> > The problem is bazel use /proc to locate its binary when start,
> > see:
> > https://github.com/bazelbuild/bazel/blob/255953740813414433eceedc99c2be
> f3c3f6e307/src/main/cpp/blaze_util_freebsd.cc
> > :
> > string GetSelfPath() {
> > char buffer[PATH_MAX] = {};
> > ssize_t bytes = readlink("/proc/curproc/file", buffer, sizeof(buffer));
> > if (bytes == sizeof(buffer)) {
> > // symlink contents truncated
> > bytes = -1;
> > errno = ENAMETOOLONG;
> > }
> > I am not sure this is acceptable for FreeBSD ports.I now set
> USE_PROCFS=yes
> > for poudriere and it can pass the testport.
> >
> > If port needs /proc is not acceptable, I will patch devel/bazel to use
> > sysctl get its binary path.
>
> It is not a question about being acceptable or not to use /proc, but
> about user convenience.  FreeBSD does not automatically configure
> procfs mount and base utilities function without procfs.  As result,
> users typically do not need it.
>
> If your port adds dependency on procfs, then it also adds requirements on
> the machine configuration and some inconvenience to its users.  Some
> programs cannot function without procfs, e.g. jvm.  But if it can be
> trivially avoided, it is better to avoid.
>
___
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: problem about port need /proc to build

[Konstantin Belousov]

On Tue, Jun 13, 2017 at 06:57:40PM +0800, Jov wrote:
> Hi ports hackers,
> 
> I am porting tensorflow to FreeBSD, It uses bazel to manage the
> dependencies and do the build.The port work now is mostly done (see:
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219609,I have local patch
> to fix the network need for do-configure) except one problem which I am not
> sure. So I write this mail to ask.
> 
> The problem is bazel use /proc to locate its binary when start,
> see:
> https://github.com/bazelbuild/bazel/blob/255953740813414433eceedc99c2bef3c3f6e307/src/main/cpp/blaze_util_freebsd.cc
> :
> string GetSelfPath() {
> char buffer[PATH_MAX] = {};
> ssize_t bytes = readlink("/proc/curproc/file", buffer, sizeof(buffer));
> if (bytes == sizeof(buffer)) {
> // symlink contents truncated
> bytes = -1;
> errno = ENAMETOOLONG;
> }
> I am not sure this is acceptable for FreeBSD ports.I now set USE_PROCFS=yes
> for poudriere and it can pass the testport.
> 
> If port needs /proc is not acceptable, I will patch devel/bazel to use
> sysctl get its binary path.

It is not a question about being acceptable or not to use /proc, but
about user convenience.  FreeBSD does not automatically configure
procfs mount and base utilities function without procfs.  As result,
users typically do not need it.

If your port adds dependency on procfs, then it also adds requirements on
the machine configuration and some inconvenience to its users.  Some
programs cannot function without procfs, e.g. jvm.  But if it can be
trivially avoided, it is better to avoid.
___
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"

problem about port need /proc to build

[Jov]

Hi ports hackers,

I am porting tensorflow to FreeBSD, It uses bazel to manage the
dependencies and do the build.The port work now is mostly done (see:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219609,I have local patch
to fix the network need for do-configure) except one problem which I am not
sure. So I write this mail to ask.

The problem is bazel use /proc to locate its binary when start,
see:
https://github.com/bazelbuild/bazel/blob/255953740813414433eceedc99c2bef3c3f6e307/src/main/cpp/blaze_util_freebsd.cc
:
string GetSelfPath() {
char buffer[PATH_MAX] = {};
ssize_t bytes = readlink("/proc/curproc/file", buffer, sizeof(buffer));
if (bytes == sizeof(buffer)) {
// symlink contents truncated
bytes = -1;
errno = ENAMETOOLONG;
}
I am not sure this is acceptable for FreeBSD ports.I now set USE_PROCFS=yes
for poudriere and it can pass the testport.

If port needs /proc is not acceptable, I will patch devel/bazel to use
sysctl get its binary path.

Best,
Jov
___
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: Looking for python-pecan

[Kubilay Kocak]

On 6/13/17 5:37 PM, Willem Jan Withagen wrote:
> On 12-6-2017 17:09, Dimitry Andric wrote:
>> On 12 Jun 2017, at 13:29, Willem Jan Withagen  wrote:
>>>
>>> For one the Ceph port I'm doing I'm going to need python-pecan in het
>>> close future.
>>>
>>> Not sure how this works with python-modules since it is something that
>>> is only used by the ceph-ports. But my guess is that I won't be
>>> able/allowed to just have a post execute like:
>>>
>>> ping install python-pecan.
>>
>> Normally you would use pip, ping is something entirely different. :)
> 
> 8-D, yup. Some commands are an automaton. Think P, and ping comes out.
> 
> 
>> Here is a patch to add a devel/py-pecan port, plus one of its
>> dependencies that is not yet in the ports tree, devel/py-logutils.
>>
>> Tested only very lightly, please take care.
> 
> It will get tested more now.
> And now I do not have to make a Pecan port. :)
> Did you submit this (and py-logutils) for acceptance?
> 
> --WjW

Hi Willem,

If you are offering to maintain these ports, I would recommend
submitting them yourself, but feel free to CC Dimitry (thank you for
helping to create them) and python@freebsdorg so our python team
committers are notified

Also, prior to submitting them, please confirm the ports (and any future
changes) pass QA (portlint, poudriere, et al). For more information and
instructions see:

https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/testing.html

___
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: copying installation to second computer

[Jonathan Chen]

On 13 June 2017 at 18:01, Thomas Mueller  wrote:
> I just managed to install (first part) ports-mgmt/synth on FreeBSD 
> 11.1-PRERELEASE amd64, using portmaster after deleting all packages except 
> pkg and portmaster.  Those old packages were no good anyway due to shared 
> libraaries being out of sync.
>
> Now I want to convert packages to synth repository format and copy this 
> installation to another computer with same FreeBSD 11.1-PRERELEASE using NFS, 
> doing as little recompilation as possible.
>
> This is my first (partway) success after an attempt to build synth on 
> FreeBSD-CURRENT amd64, before ino64, was stopped by a system crash and reboot 
> while I was sleeping.
>
> I looked through README.md and man synth, but there are still some hazy 
> points.  Or is it easier than I think?

The thing to note is that ports-mgmt/synth is a repository builder.
Coming from portupgrade or portmaster, a user may think that it is
rebuilding too many packages for a simple port change, but what it is
doing is verifying that the chain of construction for each port is
working as expected. The first build is always going to be long, but
will do concurrent builds as much as it much as possible.

Once you have a complete repo on one of your machines, you can simply
serve up the /var/synth/live_packages using www/apache24 or even ssh.
On each of the remote hosts, all you have to do is to add a
/usr/local/etc/pkg/repos/my-local-repo.conf entry, eg:
#
# Locally built packages
#
localrepo: {
  url  : http://my-build-host/live_packages,
  priority : 20,
  enabled  : yes,
}

And then you're good to go with "pkg upgrade -r localrepo" on each of
the remote hosts.

Cheers.
-- 
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"

Please commit the Tor update. It contains security fixes.

[Yuri]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219863

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219864


Thanks,

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: wget 1.19 missed IRI supporting

[Vasil Dimov]

On Tue, Jun 13, 2017 at 05:49:21 +0800, Martin Wilke wrote:
> Approved.

Merged (443488).

-- 
Vasil Dimov
gro.DSBeerF@dv
%
It is better to live rich than to die rich.
-- Samuel Johnson


signature.asc
Description: PGP signature

Re: Looking for python-pecan

[Willem Jan Withagen]

On 12-6-2017 17:09, Dimitry Andric wrote:
> On 12 Jun 2017, at 13:29, Willem Jan Withagen  wrote:
>>
>> For one the Ceph port I'm doing I'm going to need python-pecan in het
>> close future.
>>
>> Not sure how this works with python-modules since it is something that
>> is only used by the ceph-ports. But my guess is that I won't be
>> able/allowed to just have a post execute like:
>>
>>  ping install python-pecan.
> 
> Normally you would use pip, ping is something entirely different. :)

8-D, yup. Some commands are an automaton. Think P, and ping comes out.


> Here is a patch to add a devel/py-pecan port, plus one of its
> dependencies that is not yet in the ports tree, devel/py-logutils.
> 
> Tested only very lightly, please take care.

It will get tested more now.
And now I do not have to make a Pecan port. :)
Did you submit this (and py-logutils) for acceptance?

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

Synth: copying installation to second computer

[Thomas Mueller]

I just managed to install (first part) ports-mgmt/synth on FreeBSD 
11.1-PRERELEASE amd64, using portmaster after deleting all packages except pkg 
and portmaster.  Those old packages were no good anyway due to shared 
libraaries being out of sync.

Now I want to convert packages to synth repository format and copy this 
installation to another computer with same FreeBSD 11.1-PRERELEASE using NFS, 
doing as little recompilation as possible.

This is my first (partway) success after an attempt to build synth on 
FreeBSD-CURRENT amd64, before ino64, was stopped by a system crash and reboot 
while I was sleeping.

I looked through README.md and man synth, but there are still some hazy points. 
 Or is it easier than I think?


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"