RE: disk space needs for source based system and ports?

[Thomas Mueller]

from Mark Millard:

> Thomas Mueller mueller6722 at twc.com wrote on Tue Mar 28 08:10:44 UTC 2017 :

> > This raises the question, how much diskspace is required or advised for a 
> > full
> > FreeBSD installation if both the base system and ports are built from 
> > source?

> I've only ever built a very small portion of all the ports. There are
> 10s of thousands of ports as I understand. (I've not tried to count
> them.) In the environment with the most ports I'v got 331 ports built.
> (I've had  more in the past.)

> [You do not mention if you are only interested in one TARGET_ARCH
> (such as amd64) or multiple/all of them.]

> Someone may be able to answer for how space is managed on official
> FreeBSD build servers.

> Various ports that I've built or tried to build were very dependent
> on the configuration (build options, compile options, etc.) for how big
> they end up being. Some fail to build at all with WITH_DEBUG= : bugzilla
> 206279 is about www/webkit-qt5 running into a file size limit and
> aborting: ar does not allow > 4 GiByte archives.

> Also I tend to leave the /usr/obj/ ports subtrees around uncleaned so
> that I have access to source and such if problems show up. (I clean
> before building, not after.) This uses large amounts of space.

> Environment with 331 ports: about  73 GiByte used
> Environment with 107 ports: about 227 GiBytes used
> But that last has the devel/llvm40 build with WITH_DEBUG= used based
> on a standard /usr/ports/Mk/bsd.ports.mk file. Just the related
> /usr/obj/ content for that is about 118 GiBytes and the installed
> llvm40 materials are about 49 GiBytes for the specific configuration:
> so about 167 GiBytes for llvm40 as I have tend to build things.

> [If I remember right I also thought at the time that webkit-qt5 used
> the WITH_DEBUG on its own independently of FreeBSD and so defining
> it for FreeBSD caused more than intended. I could have been wrong
> about this. I stopped using such and so have not tried again. Still
> I wish FreeBSD had piked something less likely to have potential
> conflicts/less-generic, say, possibly, FBSD_WITH_DEBUG.]

> > Some messages in this thread have raised the possibility of needing 49 to 
> > over
> > 100 GB, which is much more than I have allotted.

> If your goals allow avoiding WITH_DEBUG= that will help greatly because
> some ports turn into massive things built that way.

> So would building with clean-up after each port is built.

> > Also, what about space for a local repository when using synth for ports?

> I've never used synth and most environments that I use are not supported
> by synth. So I'm unlikely to use it.

> I've only done a few poudriere-devel experiments and none of my
> environments are based on it (so far).

> > I could run out of space on some of my partitions but could make a much 
> > bigger
> > separate partition if necessary, 500 GB or more.

> Without more detail on what is to be built with what build
> options and the like I doubt you will get a detailed figure.

> Also you give no hint that would help judge how long the builds
> might take. I've been told of people letting personal(?) machines
> run for weeks/months on end.

I use mainly FreeBSD-current amd64 but also sometimes i386; also stable, so 
that makes at most four different TARGET_ARCH and FreeBSD version combinations.

Generally I don't build WITH_DEBUG.  In some cases, such as synth, I might want 
to keep the source code, Ada being the big attraction in this case.

But in your position, I can see where you might need the debugging info.  I 
generally make a log of all builds: world, kernel and ports; especially useful 
if an error occurs.

Building FreeBSD base system also uses llvm following the switch from gcc-4.2.1 
to clang.

I build a lot of ports because I want the web browsers like Mozilla Seamonkey 
or Firefox; I would also like to try Midori, Xombrero, Netsurf, maybe Otter, 
maybe Chromium; I want multimedia as much as possible.

I would not need all those browsers on multiple FreeBSD installations, just 
want to try them out.

I've had builds going up to 18 or 21 hours, don't try to go that long if 
possible.

A big spare partition of maybe 500 GB might be a good idea just in case, could 
even be used with NetBSD.  Maybe 500 GB would be overkill, I might also need a 
similar partition for Linux.

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: devel/gvfs fails to build on 11-stable and ports r436799

[Koichiro IWAO]

It helped me too, thanks!

--
`whois vmeta.jp | nkf -w`
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: Cannot build x11/libX11 in poudriere

[Walter Schwarzenfeld]

The error is here:

libxcb Makefile:

NEEDED_LIBS=-L${LOCALBASE}/lib -lXau `pkg-config --libs pthread-stubs`

=> pkg-config --libs pthread-stubs` has to be removed.

___
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: Cannot build x11/libX11 in poudriere addendum: x11/xcb-util, too

[Chris H]

Apologies for the top post. But I think your answer is here:

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

HTH

--Chris


On Wed, 29 Mar 2017 21:06:08 +0200 "O. Hartmann"  wrote

> Am Wed, 29 Mar 2017 19:13:13 +0200
> Miroslav Lachman <000.f...@quip.cz> schrieb:
> 
> > I am trying to upgrade my package repository which was working fine for 
> > a long time. I didn't change any options. Run just usual commands
> > 
> > # poudriere ports -u -p default
> > 
> > # poudriere options -z global -p default -f 
> > /usr/local/etc/poudriere.d/pkglists/global
> > 
> > # poudriere bulk -v -j 10_3_amd64 -z global -p default -f 
> > /usr/local/etc/poudriere.d/pkglists/global
> > 
> > but it failed with the following error:
> > 
> > [00:00:14] >> [01][00:00:00] Starting build of x11/libX11
> > [00:00:14] >> [01][00:00:00] Status for build x11/libX11: check-sanity
> > [00:00:14] >> [01][00:00:00] Status for build x11/libX11: pkg-depends
> > [00:00:15] >> [01][00:00:01] Status for build x11/libX11: fetch-depends
> > [00:00:15] >> [01][00:00:01] Status for build x11/libX11: fetch
> > [00:00:15] >> [01][00:00:01] Status for build x11/libX11: distfiles 
> > /vol0/poudriere/distfiles -> 
> > /vol0/poudriere/data/.m/10_3_amd64-default-global/01/portdistfiles
> > [00:00:15] >> [01][00:00:01] Status for build x11/libX11: checksum
> > [00:00:15] >> [01][00:00:01] Status for build x11/libX11: distfiles 
> > /vol0/poudriere/data/.m/10_3_amd64-default-global/01/portdistfiles -> 
> > /vol0/poudriere/distfiles
> > [00:00:15] >> [01][00:00:01] Status for build x11/libX11: 
> > extract-depends
> > [00:00:15] >> [01][00:00:01] Status for build x11/libX11: extract
> > [00:00:15] >> [01][00:00:01] Status for build x11/libX11: patch-depends
> > [00:00:15] >> [01][00:00:01] Status for build x11/libX11: patch
> > [00:00:15] >> [01][00:00:01] Status for build x11/libX11: build-depends
> > [00:00:17] >> [01][00:00:03] Status for build x11/libX11: lib-depends
> > [00:00:17] >> [01][00:00:03] Status for build x11/libX11: configure
> > [00:00:19] >> [01][00:00:05] Finished build of x11/libX11: Failed: 
> > configure
> > [00:00:19] >> [01][00:00:05] Skipping build of devel/apache-ant: 
> > Dependent port x11/libX11 failed
> > [00:00:19] >> [01][00:00:05] Skipping build of 
> > textproc/elasticsearch: Dependent port x11/libX11 failed
> > [00:00:19] >> [01][00:00:05] Skipping build of textproc/fop: 
> > Dependent port x11/libX11 failed
> > [00:00:19] >> [01][00:00:05] Skipping build of java/sigar: Dependent 
> > port x11/libX11 failed
> > [00:00:19] >> [01][00:00:05] Skipping build of x11/libXext: 
> > Dependent port x11/libX11 failed
> > [00:00:19] >> [01][00:00:05] Skipping build of x11/libXrender: 
> > Dependent port x11/libX11 failed
> > [00:00:19] >> [01][00:00:05] Skipping build of x11-toolkits/libXt: 
> > Dependent port x11/libX11 failed
> > [00:00:19] >> [01][00:00:05] Skipping build of java/openjdk7: 
> > Dependent port x11/libX11 failed
> > [00:00:19] >> [01][00:00:05] Skipping build of java/openjdk8: 
> > Dependent port x11/libX11 failed
> > [00:00:19] >> [01][00:00:05] Skipping build of 
> > converters/wkhtmltopdf: Dependent port x11/libX11 failed
> > [00:00:19] >> Stopping 8 builders
> > 
> > 
> > Poudriere log + work/libX11-1.6.5/config.log are attached.
> > 
> > Miroslav Lachman
> > ___
> > freebsd-...@freebsd.org mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-x11
> > To unsubscribe, send any mail to "freebsd-x11-unsubscr...@freebsd.org"
> 
> On several building machines (3) the same failure after updating just right
> now the ports tree and trying rebuilding everything (see below). Every X11
> related ports fails to build :-(
> 
> [...]
> checking for XCB... no
> configure: error: Package requirements (xcb >= 1.4) were not met:
> 
> Package pthread-stubs was not found in the pkg-config search path.
> Perhaps you should add the directory containing 'pthread-stubs.pc'
> to the PKG_CONFIG_PATH environment variable
> Package 'pthread-stubs', required by 'xcb', not found
> 
> Consider adjusting the PKG_CONFIG_PATH environment variable if you
> installed software in a non-standard prefix.
> 
> Alternatively, you may set the environment variables XCB_CFLAGS
> and XCB_LIBS to avoid the need to call pkg-config.
> See the pkg-config man page for more details.
> ===>  Script "configure" failed unexpectedly.
> Please report the problem to ga...@freebsd.org [maintainer] and attach the
> "/wrkdirs/usr/ports/x11/xcb-util/work/xcb-util-0.4.0/config.log" including
> the output of the failure of your make command. Also, it might be a good idea
> to provide an overview of all packages installed on your system (e.g. a
> /usr/local/sbin/pkg-static info -g -Ea).
> *** Error code 1
> 
> Stop.
> make: stopped in /usr/ports/x11/xcb-util
> >> 

Re: Cannot build x11/libX11 in poudriere addendum: x11/xcb-util, too

[O. Hartmann]

Am Wed, 29 Mar 2017 19:13:13 +0200
Miroslav Lachman <000.f...@quip.cz> schrieb:

> I am trying to upgrade my package repository which was working fine for 
> a long time. I didn't change any options. Run just usual commands
> 
> # poudriere ports -u -p default
> 
> # poudriere options -z global -p default -f 
> /usr/local/etc/poudriere.d/pkglists/global
> 
> # poudriere bulk -v -j 10_3_amd64 -z global -p default -f 
> /usr/local/etc/poudriere.d/pkglists/global
> 
> but it failed with the following error:
> 
> [00:00:14] >> [01][00:00:00] Starting build of x11/libX11
> [00:00:14] >> [01][00:00:00] Status for build x11/libX11: check-sanity
> [00:00:14] >> [01][00:00:00] Status for build x11/libX11: pkg-depends
> [00:00:15] >> [01][00:00:01] Status for build x11/libX11: fetch-depends
> [00:00:15] >> [01][00:00:01] Status for build x11/libX11: fetch
> [00:00:15] >> [01][00:00:01] Status for build x11/libX11: distfiles 
> /vol0/poudriere/distfiles -> 
> /vol0/poudriere/data/.m/10_3_amd64-default-global/01/portdistfiles
> [00:00:15] >> [01][00:00:01] Status for build x11/libX11: checksum
> [00:00:15] >> [01][00:00:01] Status for build x11/libX11: distfiles 
> /vol0/poudriere/data/.m/10_3_amd64-default-global/01/portdistfiles -> 
> /vol0/poudriere/distfiles
> [00:00:15] >> [01][00:00:01] Status for build x11/libX11: 
> extract-depends
> [00:00:15] >> [01][00:00:01] Status for build x11/libX11: extract
> [00:00:15] >> [01][00:00:01] Status for build x11/libX11: patch-depends
> [00:00:15] >> [01][00:00:01] Status for build x11/libX11: patch
> [00:00:15] >> [01][00:00:01] Status for build x11/libX11: build-depends
> [00:00:17] >> [01][00:00:03] Status for build x11/libX11: lib-depends
> [00:00:17] >> [01][00:00:03] Status for build x11/libX11: configure
> [00:00:19] >> [01][00:00:05] Finished build of x11/libX11: Failed: 
> configure
> [00:00:19] >> [01][00:00:05] Skipping build of devel/apache-ant: 
> Dependent port x11/libX11 failed
> [00:00:19] >> [01][00:00:05] Skipping build of 
> textproc/elasticsearch: Dependent port x11/libX11 failed
> [00:00:19] >> [01][00:00:05] Skipping build of textproc/fop: 
> Dependent port x11/libX11 failed
> [00:00:19] >> [01][00:00:05] Skipping build of java/sigar: Dependent 
> port x11/libX11 failed
> [00:00:19] >> [01][00:00:05] Skipping build of x11/libXext: 
> Dependent port x11/libX11 failed
> [00:00:19] >> [01][00:00:05] Skipping build of x11/libXrender: 
> Dependent port x11/libX11 failed
> [00:00:19] >> [01][00:00:05] Skipping build of x11-toolkits/libXt: 
> Dependent port x11/libX11 failed
> [00:00:19] >> [01][00:00:05] Skipping build of java/openjdk7: 
> Dependent port x11/libX11 failed
> [00:00:19] >> [01][00:00:05] Skipping build of java/openjdk8: 
> Dependent port x11/libX11 failed
> [00:00:19] >> [01][00:00:05] Skipping build of 
> converters/wkhtmltopdf: Dependent port x11/libX11 failed
> [00:00:19] >> Stopping 8 builders
> 
> 
> Poudriere log + work/libX11-1.6.5/config.log are attached.
> 
> Miroslav Lachman
> ___
> freebsd-...@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-x11
> To unsubscribe, send any mail to "freebsd-x11-unsubscr...@freebsd.org"

On several building machines (3) the same failure after updating just right now 
the ports
tree and trying rebuilding everything (see below). Every X11 related ports 
fails to
build :-(

[...]
checking for XCB... no
configure: error: Package requirements (xcb >= 1.4) were not met:

Package pthread-stubs was not found in the pkg-config search path.
Perhaps you should add the directory containing `pthread-stubs.pc'
to the PKG_CONFIG_PATH environment variable
Package 'pthread-stubs', required by 'xcb', not found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables XCB_CFLAGS
and XCB_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
===>  Script "configure" failed unexpectedly.
Please report the problem to ga...@freebsd.org [maintainer] and attach the
"/wrkdirs/usr/ports/x11/xcb-util/work/xcb-util-0.4.0/config.log" including
the output of the failure of your make command. Also, it might be a good idea
to provide an overview of all packages installed on your system (e.g. a
/usr/local/sbin/pkg-static info -g -Ea).
*** Error code 1

Stop.
make: stopped in /usr/ports/x11/xcb-util
>> Cleaning up wrkdir
===>  Cleaning for xcb-util-0.4.0_2,1
>> Warning: Leftover processes:
USER   PID %CPU %MEM   VSZ  RSS TT  STAT STARTEDTIME COMMAND
root 97275  0.0  0.0  6332 1332  0  S+J  18:54   0:00.00 sleep 1
build of x11/xcb-util ended at Wed Mar 29 18:54:07 UTC 2017
build time: 00:00:03
!!! build failure encountered !!!


-- 
O. Hartmann

Ich widerspreche der Nutzung oder 

Re: Undefined symbol "shadowUpdatePacked"

[Jan Beich]

Henk van Oers  writes:

> [   707.153] (EE) Failed to load 
> /usr/local/lib/xorg/modules/drivers/modesetting_drv.so: 
> /usr/local/lib/xorg/modules/drivers/modesetting_drv.so: Undefined symbol 
> "shadowUpdatePacked"

See bug 218153 for workarounds. Something in your xorg.conf(5) prevents
dependent modules from being loaded.

Either remove xorg.conf or limit it to "Device" section that specifies
the desired Driver and maybe BusID.
___
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: Cannot build x11/libX11 in poudriere

[Miroslav Lachman]

Anton Yuzhaninov wrote on 2017/03/29 19:18:

I also can't build x11/libX11 in poudriere:

checking for X11... no
configure: error: Package requirements (xproto >= 7.0.17 xextproto
xtrans xcb >= 1.11.1 kbproto inputproto) were not met:

Package pthread-stubs was not found in the pkg-config search path.
Perhaps you should add the directory containing `pthread-stubs.pc'
to the PKG_CONFIG_PATH environment variable
Package 'pthread-stubs', required by 'xcb', not found

Is anybody working on this problem?


If I reverted libxcb to previous version of Makefile:
https://reviews.freebsd.org/D10182

Then x11/libX11 can be built

Miroslav Lachman


___
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: x11/xscreensaver

[Kurt Jaeger]

Hi!

> Please update to the most recent available.

Done, see https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213575

-- 
p...@opsec.eu+49 171 3101372 3 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: Cannot build x11/libX11 in poudriere

[Kurt Jaeger]

Hi!

> I also can't build x11/libX11 in poudriere:
> 
> checking for X11... no
> configure: error: Package requirements (xproto >= 7.0.17 xextproto
> xtrans xcb >= 1.11.1 kbproto inputproto) were not met:
> 
> Package pthread-stubs was not found in the pkg-config search path.
> Perhaps you should add the directory containing `pthread-stubs.pc'
> to the PKG_CONFIG_PATH environment variable
> Package 'pthread-stubs', required by 'xcb', not found
> 
> Is anybody working on this problem?

Yes:

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

-- 
p...@opsec.eu+49 171 3101372 3 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: FYI: what it takes for RAM+swap to build devel/llvm40 with 4 processors or cores and WITH__DEBUG= (powerpc64 example)

[Dimitry Andric]

On 29 Mar 2017, at 17:53, Brooks Davis  wrote:
> 
> On Mon, Mar 27, 2017 at 03:25:04AM -0700, Mark Millard wrote:
...
>> This is extreme enough that next time I synchronize
>> /usr/ports and it has a devel/llvm40 update I'll
>> likely rebuild devel/llvm40 without using WITH_DEBUG= .
>> I'm more concerned with the time it takes than with
>> the file system space involved.
> 
> In the case of LLVM, enabling debug builds does a LOT more than adding
> symbols.  It's much more like enabling WITNESS and INVARIANTS in your
> kernel, except that the performance of the resulting binary is much
> worse than a WITNESS kernel (more like 10x slowdown).
> 
> As Dimitry points out, these builds are of questionable value in ports
> so garbage collecting the knob might be the sensable thing to do.

I suggest that for the LLVM ports, the DEBUG option should set the
RelWithDebInfo build type for CMake.  That will give you binaries which
can produce good backtraces, and a fair chance at debugging, in a pinch.

-Dimitry



signature.asc
Description: Message signed with OpenPGP

Re: Cannot build x11/libX11 in poudriere

[Anton Yuzhaninov]

I also can't build x11/libX11 in poudriere:

checking for X11... no
configure: error: Package requirements (xproto >= 7.0.17 xextproto
xtrans xcb >= 1.11.1 kbproto inputproto) were not met:

Package pthread-stubs was not found in the pkg-config search path.
Perhaps you should add the directory containing `pthread-stubs.pc'
to the PKG_CONFIG_PATH environment variable
Package 'pthread-stubs', required by 'xcb', not found

Is anybody working on this problem?
___
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"

Cannot build x11/libX11 in poudriere

[Miroslav Lachman]

I am trying to upgrade my package repository which was working fine for 
a long time. I didn't change any options. Run just usual commands


# poudriere ports -u -p default

# poudriere options -z global -p default -f 
/usr/local/etc/poudriere.d/pkglists/global


# poudriere bulk -v -j 10_3_amd64 -z global -p default -f 
/usr/local/etc/poudriere.d/pkglists/global


but it failed with the following error:

[00:00:14] >> [01][00:00:00] Starting build of x11/libX11
[00:00:14] >> [01][00:00:00] Status for build x11/libX11: check-sanity
[00:00:14] >> [01][00:00:00] Status for build x11/libX11: pkg-depends
[00:00:15] >> [01][00:00:01] Status for build x11/libX11: fetch-depends
[00:00:15] >> [01][00:00:01] Status for build x11/libX11: fetch
[00:00:15] >> [01][00:00:01] Status for build x11/libX11: distfiles 
/vol0/poudriere/distfiles -> 
/vol0/poudriere/data/.m/10_3_amd64-default-global/01/portdistfiles

[00:00:15] >> [01][00:00:01] Status for build x11/libX11: checksum
[00:00:15] >> [01][00:00:01] Status for build x11/libX11: distfiles 
/vol0/poudriere/data/.m/10_3_amd64-default-global/01/portdistfiles -> 
/vol0/poudriere/distfiles
[00:00:15] >> [01][00:00:01] Status for build x11/libX11: 
extract-depends

[00:00:15] >> [01][00:00:01] Status for build x11/libX11: extract
[00:00:15] >> [01][00:00:01] Status for build x11/libX11: patch-depends
[00:00:15] >> [01][00:00:01] Status for build x11/libX11: patch
[00:00:15] >> [01][00:00:01] Status for build x11/libX11: build-depends
[00:00:17] >> [01][00:00:03] Status for build x11/libX11: lib-depends
[00:00:17] >> [01][00:00:03] Status for build x11/libX11: configure
[00:00:19] >> [01][00:00:05] Finished build of x11/libX11: Failed: 
configure
[00:00:19] >> [01][00:00:05] Skipping build of devel/apache-ant: 
Dependent port x11/libX11 failed
[00:00:19] >> [01][00:00:05] Skipping build of 
textproc/elasticsearch: Dependent port x11/libX11 failed
[00:00:19] >> [01][00:00:05] Skipping build of textproc/fop: 
Dependent port x11/libX11 failed
[00:00:19] >> [01][00:00:05] Skipping build of java/sigar: Dependent 
port x11/libX11 failed
[00:00:19] >> [01][00:00:05] Skipping build of x11/libXext: 
Dependent port x11/libX11 failed
[00:00:19] >> [01][00:00:05] Skipping build of x11/libXrender: 
Dependent port x11/libX11 failed
[00:00:19] >> [01][00:00:05] Skipping build of x11-toolkits/libXt: 
Dependent port x11/libX11 failed
[00:00:19] >> [01][00:00:05] Skipping build of java/openjdk7: 
Dependent port x11/libX11 failed
[00:00:19] >> [01][00:00:05] Skipping build of java/openjdk8: 
Dependent port x11/libX11 failed
[00:00:19] >> [01][00:00:05] Skipping build of 
converters/wkhtmltopdf: Dependent port x11/libX11 failed

[00:00:19] >> Stopping 8 builders


Poudriere log + work/libX11-1.6.5/config.log are attached.

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

Undefined symbol "shadowUpdatePacked"

[Henk van Oers]

After updating all my ports and a reboot
,I can not start my X GUI on my workstation.

(10.3)

[   707.153] (II) LoadModule: "modesetting"
[   707.153] (II) Loading 
/usr/local/lib/xorg/modules/drivers/modesetting_drv.so
[   707.153] (EE) Failed to load 
/usr/local/lib/xorg/modules/drivers/modesetting
_drv.so: /usr/local/lib/xorg/modules/drivers/modesetting_drv.so: Undefined 
symbo

l "shadowUpdatePacked"
[   707.153] (II) UnloadModule: "modesetting"
[   707.153] (II) Unloading modesetting
[   707.154] (EE) Failed to load module "modesetting" (loader failed, 7)

Which port am I missing?

TIA
Henk
___
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: FYI: what it takes for RAM+swap to build devel/llvm40 with 4 processors or cores and WITH__DEBUG= (powerpc64 example)

[Brooks Davis]

On Mon, Mar 27, 2017 at 03:25:04AM -0700, Mark Millard wrote:
> On 2017-Mar-27, at 2:41 AM, Dimitry Andric  wrote:
> 
> > On 26 Mar 2017, at 23:36, Mark Millard  wrote:
> >> 
> >> I upgraded from llvm40 r4 to final. An interesting result was
> >> its creation of a backup package for llvm40-4.0.0.r4:
> >> 
> >> about 13 cpu-core-hours running pkg create
> >> 
> >> (Remember: I've been building with WITH_DEBUG= ) Its
> >> single-threaded status stands out via elapsed time
> >> approximately matching.
> >> 
> >> I'll note that it was somewhat under 6 elapsed hours for
> >> staging to have been populated (-j4 with 4 cores present
> >> helps for this part).
> >> 
> >> (Of course these elapsed-time figures are rather system
> >> dependent, although the ratio might be more stable.)
> >> 
> >> 
> >> 
> >> Also interesting was:
> >> 
> >> Installed packages to be REMOVED:
> >>llvm40-4.0.0.r4
> >> 
> >> Number of packages to be removed: 1
> >> 
> >> The operation will free 49 GiB.
> > 
> > Yes, this is big.  But there is no real need to build the llvm ports
> > with debug information, unless you want to hack on llvm itself.  And
> > in that case, you are better served by a Subversion checkout or Git
> > clone from upstream instead.
> > 
> > -Dimitry
> 
> FYI:
> 
> Historically unless something extreme like this ends up
> involved I build everything using WITH_DEBUG=  or explicit
> -g's in order to have better information on any failure.
> 
> This is extreme enough that next time I synchronize
> /usr/ports and it has a devel/llvm40 update I'll
> likely rebuild devel/llvm40 without using WITH_DEBUG= .
> I'm more concerned with the time it takes than with
> the file system space involved.

In the case of LLVM, enabling debug builds does a LOT more than adding
symbols.  It's much more like enabling WITNESS and INVARIANTS in your
kernel, except that the performance of the resulting binary is much
worse than a WITNESS kernel (more like 10x slowdown).

As Dimitry points out, these builds are of questionable value in ports
so garbage collecting the knob might be the sensable thing to do.

-- Brooks


signature.asc
Description: PGP signature

Re: Upgrade of libpthread-stubs-0.3_6 to libpthread-stubs-0.4 -- ??!?

[David Wolfskill]

On Wed, Mar 29, 2017 at 03:51:35PM +0200, Walter Schwarzenfeld wrote:
> There is a PR
> 
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218208
> 

OK; thanks.  Now that I have a working X11 environment, I'll update
that.

What I did to fix the problem (as I use portmaster to update ports on
the systems where I update the base system daily via sources):

portmaster `pkg shlib -R libpthread-stubs.so.0 | tail +2`

In my case, that affected:

===>>> The following actions were performed:
Re-installation of libxcb-1.12
Re-installation of gbm-13.0.5
Re-installation of libEGL-13.0.5

Peace,
david
-- 
David H. Wolfskill  da...@catwhisker.org
Who would have thought that a "hotelier" would be so ... unwelcoming?  Sad.

See http://www.catwhisker.org/~david/publickey.gpg for my public key.


signature.asc
Description: PGP signature

Re: Upgrade of libpthread-stubs-0.3_6 to libpthread-stubs-0.4 -- ??!?

[Walter Schwarzenfeld]

There is a PR

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

___
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: Upgrade of libpthread-stubs-0.3_6 to libpthread-stubs-0.4 -- ??!?

[Walter Schwarzenfeld]

I don't really know if it is the correct way. But I solved my problems, 
before your

post with deleting xcb and recompiling all depend packages.
(I read the README now, I don't know this before).
___
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: Upgrade of libpthread-stubs-0.3_6 to libpthread-stubs-0.4 -- ??!?

[duglas]

I was having troubles with vim after the libpthread-stubs-0.4 upgrade.
The error when trying to run vim after the upgrade was "Shared object 
"libpthread-stubs.so.0" not found, required by "libxcb.so.1""


If you're a port upgrade user you could try this:

portupgrade -fr x11/libxcb

I tried a few things but think that was the one that allowed me to get 
vim deinstalled and installed again successfully afterwards.


Please note I'm not an expert or even advanced user, try at your own risk.

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

___
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: Upgrade of libpthread-stubs-0.3_6 to libpthread-stubs-0.4 -- ??!?

[Walter Schwarzenfeld]

pkg info -r xcb.

Deinstall xcb and recompile all packages of the output of the above command.

___
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: Upgrade of libpthread-stubs-0.3_6 to libpthread-stubs-0.4 -- ??!?

[David Wolfskill]

On Wed, Mar 29, 2017 at 03:13:11PM +0200, Walter Schwarzenfeld wrote:
> /usr/ports/devel/libpthread-stubs/work/libpthread-stubs-0.4/README
> 
> Project description
> ---
> 
> Currently the project provides only a pkg-config [.pc] file, 
> pthread-stubs.pc.The latter contains the Cflags/Libs flags applicable to 
> programs/libraries
> that use only lightweight pthread API. See the next sections for the 
> reasoning
> and implementation details.
> 

Thank you for the quick response!

Wow.  That comes as rather a surprise.  (And since the "work" hierarchy
is transient, it would be a bit hard to find unless one knew to look
for it.)  Might an UPDATING entry be appropriate for this?

Unfortunately (for me, anyway), after looking at the file in question,
I remain clueless as to what I can do about ports that attempt to link
to libpthread-stubs.so.0 (such as xdm).

I suppose I could try rebuilding xdm; if that works, the circumvention
is sufficiently straightforward

Peace,
david
-- 
David H. Wolfskill  da...@catwhisker.org
Who would have thought that a "hotelier" would be so ... unwelcoming?  Sad.

See http://www.catwhisker.org/~david/publickey.gpg for my public key.


signature.asc
Description: PGP signature

Re: Upgrade of libpthread-stubs-0.3_6 to libpthread-stubs-0.4 -- ??!?

[Walter Schwarzenfeld]

/usr/ports/devel/libpthread-stubs/work/libpthread-stubs-0.4/README

Project description
---

Currently the project provides only a pkg-config [.pc] file, 
pthread-stubs.pc.The latter contains the Cflags/Libs flags applicable to 
programs/libraries
that use only lightweight pthread API. See the next sections for the 
reasoning

and implementation details.

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

Upgrade of libpthread-stubs-0.3_6 to libpthread-stubs-0.4 -- ??!?

[David Wolfskill]

After performing the above upgrade (apparently "successfully"), I have
no libpthread-stubs.so.0:

From "pkg info --list-files devel/libpthread-stubs" on a system I have
yet to update:
libpthread-stubs-0.3_6:
/usr/local/lib/libpthread-stubs.a
/usr/local/lib/libpthread-stubs.so
/usr/local/lib/libpthread-stubs.so.0
/usr/local/lib/libpthread-stubs.so.0.0.0
/usr/local/libdata/pkgconfig/pthread-stubs.pc

From "pkg info --list-files devel/libpthread-stubs" on my laptop (after
the update):
libpthread-stubs-0.4:
/usr/local/libdata/pkgconfig/pthread-stubs.pc

This tends to make (e.g.) xdm rather unhappy.

Above was from a ports working copy at r437189, built on:
FreeBSD 11.0-STABLE #295  r316129M/316133:1100510: Wed Mar 29 05:05:10 PDT 2017 
r...@g1-252.catwhisker.org:/common/S1/obj/usr/src/sys/CANARY  amd64

Any hints for recovery?

Peace,
david
-- 
David H. Wolfskill  da...@catwhisker.org
Who would have thought that a "hotelier" would be so ... unwelcoming?  Sad.

See http://www.catwhisker.org/~david/publickey.gpg for my public key.


signature.asc
Description: PGP signature

RE: disk space needs for source based system and ports?

[Mark Millard]

[This derives from the thread starting with:
https://lists.freebsd.org/pipermail/freebsd-toolchain/2017-March/002780.html
]

Thomas Mueller mueller6722 at twc.com wrote on Tue Mar 28 08:10:44 UTC 2017 :

> This raises the question, how much diskspace is required or advised for a full
> FreeBSD installation if both the base system and ports are built from source?

I've only ever built a very small portion of all the ports. There are
10s of thousands of ports as I understand. (I've not tried to count
them.) In the environment with the most ports I'v got 331 ports built.
(I've had  more in the past.)

[You do not mention if you are only interested in one TARGET_ARCH
(such as amd64) or multiple/all of them.]

Someone may be able to answer for how space is managed on official
FreeBSD build servers.

Various ports that I've built or tried to build were very dependent
on the configuration (build options, compile options, etc.) for how big
they end up being. Some fail to build at all with WITH_DEBUG= : bugzilla
206279 is about www/webkit-qt5 running into a file size limit and
aborting: ar does not allow > 4 GiByte archives.

Also I tend to leave the /usr/obj/ ports subtrees around uncleaned so
that I have access to source and such if problems show up. (I clean
before building, not after.) This uses large amounts of space.

Environment with 331 ports: about  73 GiByte used
Environment with 107 ports: about 227 GiBytes used

But that last has the devel/llvm40 build with WITH_DEBUG= used based
on a standard /usr/ports/Mk/bsd.ports.mk file. Just the related
/usr/obj/ content for that is about 118 GiBytes and the installed
llvm40 materials are about 49 GiBytes for the specific configuration:
so about 167 GiBytes for llvm40 as I have tend to build things.

[If I remember right I also thought at the time that webkit-qt5 used
the WITH_DEBUG on its own independently of FreeBSD and so defining
it for FreeBSD caused more than intended. I could have been wrong
about this. I stopped using such and so have not tried again. Still
I wish FreeBSD had piked something less likely to have potential
conflicts/less-generic, say, possibly, FBSD_WITH_DEBUG.]

> Some messages in this thread have raised the possibility of needing 49 to over
> 100 GB, which is much more than I have allotted.

If your goals allow avoiding WITH_DEBUG= that will help greatly because
some ports turn into massive things built that way.

So would building with clean-up after each port is built.

> Also, what about space for a local repository when using synth for ports?

I've never used synth and most environments that I use are not supported
by synth. So I'm unlikely to use it.

I've only done a few poudriere-devel experiments and none of my
environments are based on it (so far).

> I could run out of space on some of my partitions but could make a much bigger
> separate partition if necessary, 500 GB or more.

Without more detail on what is to be built with what build
options and the like I doubt you will get a detailed figure.

Also you give no hint that would help judge how long the builds
might take. I've been told of people letting personal(?) machines
run for weeks/months on end.

> If this question diverges from the proper thread topic, feel free to change 
> the
> subject line and respond to freebsd-ports if that is more appropriate, so I
> won't be accused of hijacking this thread.

Done.

===
Mark Millard
markmi at dsl-only.net

___
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

[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
+-+
comms/gammu | 1.38.1  | 1.38.2
+-+
devel/jrtplib   | 3.11.0  | 3.11.1
+-+
multimedia/vdr  | 1.7.29  | 2.3.3
+-+


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: port of nss-passwords

[Matthias Apitz]

El día martes, marzo 28, 2017 a las 12:30:01p. m. +0200, Matthias Apitz 
escribió:

> Yes, thank you. It is even in the head of our ports.
> This brings it on step further:
> 
> $ gmake
> ocamlfind ocamlc -g -package fileutils.str,sqlite3 -c main.ml
> ocamlfind: Package `fileutils.str' not found
> gmake: *** [Makefile:20: main.cmo] Error 2+
> 
> (the 'sqlite3' can be installed with the port databases/ocaml-sqlite3).
> 
> Something like ports/*/ocaml-file* we do not have.

I manged to compile and install ocaml-fileutils directly from its source
and could gmake the tool nss-passwords. It works nicely but only on the
old signons.sqlite database, not on the logins.json file of Mozilla.

Perhaps one could write a script to insert the records from logins.json
into the old (now unused) signons.sqlite db.

matthias

-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/  ☎ 
+49-176-38902045
___
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"

x11/xscreensaver

[The Doctor]

Please update to the most recent available.

-- 
Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca
Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist rising!
http://www.fullyfollow.me/rootnl2k  Look at Psalms 14 and 53 on Atheism
God is dead! Yahweh lives! Jesus his only begotten Son is the Risen Saviour!!
___
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"