On 2021-May-20, at 21:10, Chris wrote:
> On 2021-05-20 13:47, Mark Millard wrote:
>> Chris portmaster at bsdforge.com wrote on
>> Thu May 20 20:09:29 UTC 2021 :
>>> On 2021-05-20 12:21, Kevin Oberman wrote:
>>> > . . .
>>> >>
>>> > You can greatly reduce the build-time for devel/llvm* by chang
Kevin Oberman rkoberman at gmail.com wrote on
Thu May 20 21:37:28 UTC 2021 :
> On Thu, May 20, 2021 at 12:48 PM Mark Millard wrote:
>
> > Kevin Oberman rkoberman at gmail.com wrote on
> > Thu May 20 19:21:24 UTC 2021 :
> >
> > > You can greatly reduce the build-time for devel/llvm* by changing t
Chris portmaster at bsdforge.com wrote on
Thu May 20 20:09:29 UTC 2021 :
> On 2021-05-20 12:21, Kevin Oberman wrote:
> > . . .
> >>
> > You can greatly reduce the build-time for devel/llvm* by changing the
> > config to BE_NATIVE to avoid building backends for all FreeBSD supported
> > platforms.
Kevin Oberman rkoberman at gmail.com wrote on
Thu May 20 19:21:24 UTC 2021 :
> You can greatly reduce the build-time for devel/llvm* by changing the
> config to BE_NATIVE to avoid building backends for all FreeBSD supported
> platforms. Obviously this is not acceptable for many cases, but if you
>
On 2021-May-20, at 11:11, Mark Millard wrote:
> Andrea Venturoli ml at netfence.it wrote on
> Thu May 20 14:54:50 UTC 2021 :
>
>> On 5/20/21 4:11 PM, Alexis Praga wrote:
>>>
>>> Thanks for the suggestions.
>>>
At least, if your machine is powerful enough, you can edit your
/usr/lo
Andrea Venturoli ml at netfence.it wrote on
Thu May 20 14:54:50 UTC 2021 :
> On 5/20/21 4:11 PM, Alexis Praga wrote:
> >
> > Thanks for the suggestions.
> >
> >> At least, if your machine is powerful enough, you can edit your
> >> /usr/local/etc/poudriere.conf and list these big ports in
> >> AL
I was doing a poudriere pkgclean under:
# uname -apKU
FreeBSD CA72_16Gp_ZFS 13.0-RELEASE FreeBSD 13.0-RELEASE #0
releng/13.0-n244733-ea31abc261ff-dirty: Thu Apr 29 21:53:20 PDT 2021
root@CA72_4c8G_ZFS:/usr/obj/BUILDs/13_0R-CA72-nodbg-clang/usr/13_0R-src/arm64.aarch64/sys/GENERIC-NODBG-CA72
On 2021-May-19, at 14:17, Mark Millard wrote:
> On 2021-May-19, at 10:29, Mark Millard wrote:
>
>> bob prohaska fbsd at www.zefox.net wrote on
>> Wed May 19 16:09:32 UTC 2021 :
>>
>>> On Tue, May 18, 2021 at 09:24:00AM +0200, Stefan Esser wrote:
>>>
>>> [portmaster background omitted]
On 2021-May-19, at 10:29, Mark Millard wrote:
> bob prohaska fbsd at www.zefox.net wrote on
> Wed May 19 16:09:32 UTC 2021 :
>
>> On Tue, May 18, 2021 at 09:24:00AM +0200, Stefan Esser wrote:
>>>
>>
>> [portmaster background omitted]
>>
>>> If you want to give the attached port a try, it
bob prohaska fbsd at www.zefox.net wrote on
Wed May 19 16:09:32 UTC 2021 :
> On Tue, May 18, 2021 at 09:24:00AM +0200, Stefan Esser wrote:
> >
>
> [portmaster background omitted]
>
> > If you want to give the attached port a try, it will install LUA and some
>
>
> I tried ports-mgmt/portma
bob prohaska fbsd at www.zefox.net wrote on
Mon May 17 23:46:38 UTC 2021 :
> On Mon, May 17, 2021 at 12:28:24PM -0700, Mark Millard via freebsd-ports
> wrote:
> > bob prohaska fbsd at www.zefox.net wrote on
> > Mon May 17 15:55:21 UTC 2021 :
> >
> > > The exis
bob prohaska fbsd at www.zefox.net wrote on
Mon May 17 15:55:21 UTC 2021 :
> The existing conflict between versions of python strikes me as more of a
> planning problem than a software bug. It may be naive, but I don't see
> why python37 and python38 can't use distinct names for files placed in
>
On 2021-May-16, at 15:33, Tatsuki Makino wrote:
> Mark Millard wrote on 2021/05/16 17:11:
>> On 2021-May-16, at 00:16, Tatsuki Makino
>> wrote:
>>
>>> poudriere jail -c -j main -m 'src=/usr/src' -v `make -C /usr/src/release/
>>> -V VERSION VERSION=\$\{REVISION:Q\}-\$\{BRANCH:Q\}`
>>>
>> Bob
On 2021-May-16, at 00:16, Tatsuki Makino wrote:
> Mark Millard via freebsd-ports wrote on 2021/05/16 10:57:
>> In the form that I use poudriere I use something
>> like the following. I presume here that /usr/src
>> is populated and has the source for the system
>> i
Something I've not asked about or otherwise referenced
is if you use non-default port options for any of the
ports that you build.
There is:
poudriere options -jmain -c -f ~root/origins/main-origins.txt
or:
poudriere options -jmain -C -f ~root/origins/main-origins.txt
where -c vs. -C is:
QUOTE
On 2021-May-15, at 16:37, bob prohaska wrote:
> On Fri, May 14, 2021 at 07:29:15PM -0700, Mark Millard wrote:
>> bob prohaska fbsd at www.zefox.net wrote on
>> Fri May 14 01:35:28 UTC 2021 :
>>
>>> Would use of poudriere help with this sort of problem?
>>> It isn't trivial to configure, but t
bob prohaska fbsd at www.zefox.net wrote on
Fri May 14 01:35:28 UTC 2021 :
> On Thu, May 13, 2021 at 01:35:50PM -0700, Mark Millard wrote:
> > You have apparently chosen to build/update ports via a
> > technique that requires you to manage the dependencies, at
> > least some of the time. (Not that
On 2021-May-13, at 14:27, Tatsuki Makino wrote:
> 20210425 of UPDATING doesn't take into care the environment where python37
> and python38 are installed at the same time.
> This is a problem for people who installed 3.8 when 3.7 was the default.
> (e.g. user of graphics/blender)
>
> Can you e
bob prohaska fbsd at www.zefox.net wrote on
Thu May 13 15:39:41 UTC 2021 :
> On Thu, May 13, 2021 at 08:13:07AM +0200, Jan Beich wrote:
> > >
> > > Moving to /usr/ports/json-glib and using
> > > make -DBATCH MAKE_JOBS_UNSAFE=yes MAKE_JOBS_NUMBER=4
> > > DISABLE_VULNERABILITIES=yes > make.log
> >
On 2021-May-12, at 23:13, Mark Millard wrote:
>
> On 2021-May-12, at 22:28, bob prohaska wrote:
>
>> On Wed, May 12, 2021 at 09:16:29PM -0700, Mark Millard via freebsd-ports
>> wrote:
>>> On 2021-May-12, at 20:48, bob prohaska wrote:
>>>
>&g
On 2021-May-12, at 22:28, bob prohaska wrote:
> On Wed, May 12, 2021 at 09:16:29PM -0700, Mark Millard via freebsd-ports
> wrote:
>> On 2021-May-12, at 20:48, bob prohaska wrote:
>>
>>>
>>> Moving to /usr/ports/json-glib and using
>>> make -D
On 2021-May-12, at 20:48, bob prohaska wrote:
> On Wed, May 12, 2021 at 05:17:37PM -0700, Mark Millard via freebsd-ports
> wrote:
>> bob prohaska fbsd at www.zefox.net wrote on
>> Wed May 12 21:10:02 UTC 2021 :
>>
>>> Attempts to compile x11/x11-wm/lxqt on a P
bob prohaska fbsd at www.zefox.net wrote on
Wed May 12 21:10:02 UTC 2021 :
> Attempts to compile x11/x11-wm/lxqt on a Pi4 running -current
> get stuck with:
> ===> Building for json-glib-1.6.2_1
> [ 1% 1/53] cc -Ijson-glib/libjson-glib-1.0.so.0.600.2.p -Ijson-glib
> -I../json-glib -I. -I.. -I/u
Yuri yuri at FreeBSD.org wrote on
Tue May 11 16:54:05 UTC 2021 :
> I checked packages for www/authelia, www/adguardhome, science/siesta and
> they are 2+ weeks outdated for thus architecture.
Using
http://ampere2.nyi.freebsd.org/build.html?mastername=main-arm64-default&build=pe67ae562eb4c_s64
I've been using USE_TMPFS=yes (so "wrkdir data") on
various systems, both ZFS (recently) and UFS
(generally, even now). Only one system builds rust
(in order for something else to be built), at least
so far.
An example of the wrkdirs tmpfs use for rust is
(UFS context):
# df -m | grep tmpfs
Files
Tatsuki Makino tatsuki_makino at hotmail.com wrote on
Mon May 10 21:08:06 UTC 2021 :
> In poudriere.conf, there is a setting for BUILDNAME_FORMAT.
> It will be set to the default value of %Y-%m-%d_%Hh%Mm%Ss in
> /usr/local/share/poudriere/common.sh
>
> BUILDNAME_FORMAT is used as ${BUILDNAME:=$(
Ronald Klop ronald-lists at klop.ws wrote on
Sun May 9 10:22:38 UTC 2021 :
> On the pkg builders the list of builds is ordered on git hash.
>
> http://beefy18.nyi.freebsd.org/jail.html?mastername=main-amd64-default
>
> (NB: ipv6 only)
>
> This ordering is totally random to me. With svn the list
On 2021-May-3, at 08:23, bob prohaska wrote:
> On Mon, May 03, 2021 at 01:00:03AM -0700, Mark Millard via freebsd-ports
> wrote:
> [detailed code tour omitted]
>
>>
>> My guess would be xoscope used a signed 32-bit type
>> that got a value with sign extension
On 2021-May-2, at 23:37, bob prohaska wrote:
> After a successful compile of audio/xoscope on a Pi4 running current a
> stream of messages appeared on the console and in the security log
> while xoscope was running:
>
>
> +WARNING pid 26370 (xoscope): ioctl sign-extension ioctl c0045006
On 2021-Apr-28, at 22:26, Kurt Jaeger wrote:
>
>>> https://bsdimp.blogspot.com/2020/09/freebsd-subversion-to-git-migration.html
>>
>> The https://github.com/bsdimp/freebsd-git-docs/ material
>> for git-why.md is still available via:
>>
>> https://github.com/bsdimp/freebsd-git-docs/commits/48
Kurt Jaeger pi at freebsd.org wrote on
Wed Apr 28 19:30:32 UTC 2021 :
> > > > The 'why' was explained here:
> > > >
> > > > https://github.com/bsdimp/freebsd-git-docs/
>
> Ah, here's the link to the 'why' post:
>
> https://bsdimp.blogspot.com/2020/09/freebsd-subversion-to-git-migration.html
The
George Mitchell george+freebsd at m5p.com wrote on
Mon Apr 19 14:51:54 UTC 2021 :
> For me, https://cgit.freebsd.org/ports/tree/
> is more helpful, though I still haven't figured out where to find the
> *date* of any commit ...
Two ways starting from a tree view:
A) On the same line as the fil
On 2021-Apr-8, at 10:46, Mark Millard wrote:
> Building devel/llvm10 via poudriere-devel on a Cortex-A57
> system (OverDrive 1000), I ended up with just:
>
> # /usr/local/llvm10/bin/llc -version
> LLVM (http://llvm.org/):
> LLVM version 10.0.1
> Optimized build.
> Default target: aarch64-p
ned in your use that should be cleaned up.
> On 09/04/2021 1:23 pm, Mark Millard via freebsd-ports wrote:
>> Simon Wright simon.wright at gmx.net wrote on
>> Fri Apr 9 02:48:47 UTC 2021 :
>>
>>> I'm still not clear though whether checking out this commit brin
Simon Wright simon.wright at gmx.net wrote on
Fri Apr 9 02:48:47 UTC 2021 :
> I'm still not clear though whether checking out this commit brings in
> all the commits from git clone to this one or only this commit. My
> reading seems to say that this is *only* this one commit which is not my
> need
Building devel/llvm10 via poudriere-devel on a Cortex-A57
system (OverDrive 1000), I ended up with just:
# /usr/local/llvm10/bin/llc -version
LLVM (http://llvm.org/):
LLVM version 10.0.1
Optimized build.
Default target: aarch64-portbld-freebsd14.0
Host CPU: (unknown)
Registered Targets:
[The original send attempt for this failed somehow.]
Eric Turgeon ericbsd at freebsd.org wrote on
Mon Apr 5 20:33:22 UTC 2021 :
> Today when trying to sync the GhostBSD ports tree with the FreeBSD ports
> tree, I found out the main branch history is not compatible with the old
> GitHub master.
>
___
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"
https://cgit.freebsd.org/ shows:
QUOTE
NameDescription IdleLinks
development
doc FreeBSD documentation tree 16 hourssummarylogtree
ports FreeBSD ports tree 57 min. summarylogtree
src FreeBSD source tree 3 days summarylogtree
END QUOTE
https://wiki.fre
Carmel carmel_ny at outlook.com wrote on
Sun Apr 4 18:05:17 UTC 2021 :
> On Sun, 4 Apr 2021 19:49:04 +0200 (CEST), Helge Oldach stated:
> >Jeffrey Bouquet via freebsd-ports wrote on Sun, 04 Apr 2021 18:46:15
> >+0200 (CEST):
> >> running 12.2 STABLE, I would like a complete DEFAULTS and PORTS
> >
Felix Palmen felix at palmen-it.de wrote on
Sat Apr 3 20:35:46 UTC 2021 :
> * Mark Millard via freebsd-ports [20210403
> 10:02]:
> > Felix Palmen felix at palmen-it.de wrote on
> > > There was an announcement to deprecate it, but it's still built with
> >
Felix Palmen felix at palmen-it.de wrote on
Fri Apr 2 22:49:58 UTC 2021 :
> * Guido Falsi via freebsd-ports [20210403
> 00:35]:
> > On 02/04/21 23:16, The Doctor via freebsd-ports wrote:
> > > but I use pkg/portsnap .
> > >
> > > How does that affect us?
> >
> > AFAIK you can't use it anymore.
x27;s/freebsd\/freebsd-//g' /usr/local/etc/gitup.conf
>>
>> then do `gitup ports`
>>
>> Kind Regards,
>> Moin
>>
>>> On 3 Apr, 2021, at 07:20, The Doctor via freebsd-ports
>>> wrote:
>>>
>>> On Fri, Apr 02, 2021 at 05:
On 2021-Apr-2, at 18:20, The Doctor wrote:
> On Fri, Apr 02, 2021 at 05:54:48PM -0700, Mark Millard via freebsd-ports
> wrote:
>>
>>
>> On 2021-Apr-2, at 17:41, Mark Millard wrote:
>>
>>> The Doctor doctor at doctor.nl2k.ab.ca wrote on
>>>
On 2021-Apr-2, at 17:41, Mark Millard wrote:
> The Doctor doctor at doctor.nl2k.ab.ca wrote on
> Sat Apr 3 00:27:42 UTC 2021 :
>
> Results:
>
>> gitup -v 1 ports
>> # Host: github.com
>> # Port: 443
>> # Repository: /freebsd/freebsd-ports.git
>> # Target: /usr/ports
>> gitup: get_commit_deta
The Doctor doctor at doctor.nl2k.ab.ca wrote on
Sat Apr 3 00:27:42 UTC 2021 :
Results:
> gitup -v 1 ports
> # Host: github.com
> # Port: 443
> # Repository: /freebsd/freebsd-ports.git
> # Target: /usr/ports
> gitup: get_commit_details: refs/heads/master doesn't exist in
> /freebsd/freebsd-ports.
George Mitchell george+freebsd at m5p.com wrote on
Thu Apr 1 22:19:32 UTC 2021 :
> On 4/1/21 6:04 PM, Tatsuki Makino wrote:
> > Dewayne Geraghty wrote on 2021/04/01 17:47:
> >> [...]
> >> Would appreciate if anyone can provide insight as to the 4 git commands
> >> that I need to function, in a man
Chris Rees crees at bayofrum.net wrote on
Thu Mar 4 09:48:12 UTC 2021 :
> . . .
> I'm afraid that this, which I found in pdflib-lite's readme.txt [1]
> differs on that opinion.
>
>
>
> - PDFlib Lite
>Open-source edition for basic PDF generation, free for personal use.
>PDFlib Lite
On 2021-Feb-23, at 19:26, Tatsuki Makino wrote:
> Hello.
>
> Jonathan Chen wrote on 2021/02/24 11:25:
>>
>> You're running 12.1, and not -STABLE. The EOL for 12.1 was Nov-2019.
>>
>> You need to get a later version or run -STABLE (ie: build from source
>> off the stable/12 branch).
>
> No,
Chris portmaster at bsdforge.com wrote on
Tue Feb 23 23:31:09 UTC 2021 :
> On 2021-02-23 14:58, @lbutlr wrote:
> > On 23 Feb 2021, at 13:26, Chris wrote:
> >> OK On a virgin 12 stable install.
> >
> > The current release is 12.2-RELEASE. 12.0-RELEASE was EOLed last February.
> > I
> > am
> > n
On 2021-Feb-15, at 20:18, Mark Millard wrote:
> Steve Kargl sgk at troutmask.apl.washington.edu wrote on
> Tue Feb 16 02:14:06 UTC 2021 :
>
>> On Mon, Feb 15, 2021 at 05:10:54PM -0800, Mark Millard via freebsd-ports
>> wrote:
>>> Steve Kargl sgk at troutmask.apl.w
Steve Kargl sgk at troutmask.apl.washington.edu wrote on
Tue Feb 16 02:14:06 UTC 2021 :
> On Mon, Feb 15, 2021 at 05:10:54PM -0800, Mark Millard via freebsd-ports
> wrote:
> > Steve Kargl sgk at troutmask.apl.washington.edu wrote on
> > Mon Feb 15 20:39:19 UTC 2021 :
> >
Steve Kargl sgk at troutmask.apl.washington.edu wrote on
Mon Feb 15 20:39:19 UTC 2021 :
> On Mon, Feb 15, 2021 at 12:01:47PM -0800, Kevin Oberman wrote:
> > On Mon, Feb 15, 2021 at 11:10 AM Steve Kargl <
> > sgk at troutmask.apl.washington.edu> wrote:
> >
> > > I have a system installed from late
Steve Kargl sgk at troutmask.apl.washington.edu wrote on
Mon Feb 15 19:10:36 UTC 2021 :
> I have a system installed from late January FreeBSD-current
> sources and at that point an up-to-date ports tree. All
> installed ports where builtin after I installed FreeBSD. So,
> I am running FreeBSD-14.
> On arm64 (Pi3) under
> FreeBSD pelorus.zefox.org 13.0-ALPHA3 FreeBSD 13.0-ALPHA3 #2
> stable/13-c256281-gc415d0df47f: Fri Feb 5 08:09:12 PST 2021
> bob at pelorus.zefox.org
> :/usr/obj/usr/freebsd-src/arm64.aarch64/sys/GENERIC-MMCCAM arm64
> it looks like dialog4ports is out of whack. It
https://www.freshports.org/devel/autoconf reports that
perl is a dependency:
Build dependencies:
• gm4 : devel/m4
• help2man : misc/help2man
• gmake : devel/gmake
• makeinfo : print/texinfo
• perl5>=5.28.r1<5.29 : lang/perl5.28
Runtime dependencies:
bob prohaska fbsd at www.zefox.net wrote on
Sat Feb 6 16:50:16 UTC 2021 :
> Looks like a path problem, so
>
> root at pelorus
> :/usr/ports/devel/autoconf # $PATH
> /sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/root/bin:
> Command not found.
>
> Paths look reasonable, but what's
On 2021-Feb-4, at 16:47, Tatsuki Makino wrote:
> Mark Millard wrote on 2021/02/05 09:39:
>>
>>
>> On 2021-Feb-4, at 15:54, Tatsuki Makino
>> wrote:
>>
>>> Is there indexinfo in deps in +MANIFEST extracted from your
>>> /usr/local/poudriere/data/packages/FBSDpowerpc64-default/.building/Al
On 2021-Feb-4, at 15:54, Tatsuki Makino wrote:
> make -C /usr/ports/devel/gettext-tools -V _STAGE_SEQ
>
> is usually
>
> ... 150:run-depends ... 750:post-install-script ...
>
> So, RUN_DEPENDS is sufficient for that.
Okay. Good to know, thanks.
> I suspect that RUN_DEPENDS is not recorded
On 2021-Feb-4, at 15:33, Mark Millard wrote:
> On 2021-Feb-4, at 15:11, Tatsuki Makino wrote:
>
>> In rare cases, a package with missing contents may be created.
>> If there is a problem after checking with
>>
>> tar -t -f
>> /usr/local/poudriere/data/packages/jail-portstree/All/indexinfo-0.3
On 2021-Feb-4, at 15:11, Tatsuki Makino wrote:
> In rare cases, a package with missing contents may be created.
> If there is a problem after checking with
>
> tar -t -f
> /usr/local/poudriere/data/packages/jail-portstree/All/indexinfo-0.3.1.txz
>
> , etc., you can force it to be rebuilt by
m/work/.bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/root/bin
. . .
--MAKE_ENV--
. . .
PATH=/wrkdirs/usr/ports/x11/libXpm/work/.bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/root/bin
. . .
> Mark Millard via freebsd-ports wrote on 2021/02/05 07:14:
>
Looks like print/indexinfo is not being installed before
installing gettext-tools tries to use indexinfo in various
contexts.
===
===> rhash-1.4.0 depends on executable: msgfmt - not found
===> Installing existing package /packages/All/gettext
Xavier Humbert xavier at groumpf.org wrote on
Sat Jan 30 22:02:51 UTC 2021 :
> I was running 13-CURRENT, and as of 01/22 I switched to 13-STABLE
>
> Now, when I run any ports/pkg command - I use only ports-, I got
>
> > pkg-static: Warning: Major OS version upgrade detected. Running "pkg
> > b
On 2020-Dec-14, at 13:34, Mark Millard wrote:
> This was on aarch64 doing a build targeting armv7 via poudriere --but might
> apply to other platforms that by default do not have LLVM's OpenMP runtime:
>
>WITHOUT_OPENMP
> Set to not build LLVM's OpenMP runtime.
>
>
This was on aarch64 doing a build targeting armv7 via poudriere --but might
apply to other platforms that by default do not have LLVM's OpenMP runtime:
WITHOUT_OPENMP
Set to not build LLVM's OpenMP runtime.
This is a default setting on arm/armv6, arm/armv7, mips/mip
On 2020-Dec-5, at 07:02, Steve Kargl
wrote:
> On Sat, Dec 05, 2020 at 01:18:34AM -0800, Mark Millard wrote:
>> Steve Kargl sgk at troutmask.apl.washington.edu wrote on:
>>>
>>> Well, I guess that pretty much kills LLVM_DEFAULT for any
>>> modern hardware (even a 8 year old laptop) that uses
Steve Kargl sgk at troutmask.apl.washington.edu wrote on:
Fri Dec 4 22:59:46 UTC 2020
> On Fri, Dec 04, 2020 at 11:41:41PM +0100, Jan Beich wrote:
> > Steve Kargl writes:
> >
> > > It takes a long time to compile on my laptop. I have
> > >
> > > DEFAULT_VERSIONS+=llvm=90
> >
> > Why do you nee
On 2020-Aug-10, at 23:44, Mark Millard wrote:
> I noticed the sysutils/edk2 addition. So I've tried to figure
> out how to use it to reproduce the pftf RPi4 V1.18 release
> (as an example), by, say, adjusting the distinfo file to pick
> up the matching source.
>
> Looking at https://github.com/p
On 2020-Aug-11, at 00:46, Mark Murray wrote:
>> On 11 Aug 2020, at 07:44, Mark Millard via freebsd-arm
>> wrote:
>>
>> Unfortunately, I'm not aware of anything for macchiatobin
>> that is analogous to https://github.com/pftf/RPi3 and
>> https://github.com/pftf/RPi4 off which to derive what
>>
I noticed the sysutils/edk2 addition. So I've tried to figure
out how to use it to reproduce the pftf RPi4 V1.18 release
(as an example), by, say, adjusting the distinfo file to pick
up the matching source.
Looking at https://github.com/pftf/RPi4/releases/
there is a 4dd0f24 listed for the most re
On 2020-Jul-30, at 23:11, Tatsuki Makino wrote:
>
> Hmmm, I was using 2 builders by -J 2:4. But I don't remember if there
> were other jobs available when nss was building :)
> How is your poudriere set up for NO_ZFS? I'm using it with NO_ZFS=yes.
I do not have any media with ZFS in use in an
On 2020-Jul-29, at 23:34, Tatsuki Makino wrote:
> Hello.
>
> The same thing happened to me.
> If you want the build to succeed, I think enabling DISABLE_MAKE_JOBS
> will solve the problem.
Running bulk again had no troubles, no use of MAKE_JOBS_UNSAFE
involved.
However, I use poudriere with
While building ports for a cortexA53 (aarch64) on a cortexA57
system via poudriere-devel use I got:
gmake[5]: Leaving directory
'/wrkdirs/usr/ports/security/nss/work/nss-3.55/nss/lib/ckfw/builtins'
gmake[4]: *** [../../coreconf/rules.mk:387:
../../../dist/public/nss/nssckmdt.h] Abort trap (core
On 2020-Jul-23, at 09:25, Mark Millard wrote:
>
> On 2020-Jul-22, at 21:02, Mark Millard wrote:
>
>> On 2020-Jul-22, at 17:16, Mark Millard wrote:
>>
>>> On 2020-Jul-22, at 14:11, Jan Beich wrote:
>>>
Mark Millard via freebsd-ppc writes:
> ../src/util/u_atomic.c:38:1: e
On 2020-Jul-22, at 21:02, Mark Millard wrote:
> On 2020-Jul-22, at 17:16, Mark Millard wrote:
>
>> On 2020-Jul-22, at 14:11, Jan Beich wrote:
>>
>>> Mark Millard via freebsd-ppc writes:
>>>
../src/util/u_atomic.c:38:1: error: cannot redeclare builtin function
'__sync_add_and_f
On 2020-Jul-22, at 17:16, Mark Millard wrote:
> On 2020-Jul-22, at 14:11, Jan Beich wrote:
>
>> Mark Millard via freebsd-ppc writes:
>>
>>> ../src/util/u_atomic.c:38:1: error: cannot redeclare builtin function
>>> '__sync_add_and_fetch_8'
>>> __sync_add_and_fetch_8(uint64_t *ptr, uint64_t va
On 2020-Jul-22, at 14:11, Jan Beich wrote:
> Mark Millard via freebsd-ppc writes:
>
>> ../src/util/u_atomic.c:38:1: error: cannot redeclare builtin function
>> '__sync_add_and_fetch_8'
>> __sync_add_and_fetch_8(uint64_t *ptr, uint64_t val)
>> ^
>> ../src/util/u_atomic.c:38:1: note: '__sync_
On 2020-Jul-22, at 01:03, Mark Millard wrote:
> On 2020-Jul-22, at 00:23, KIRIYAMA Kazuhiko wrote:
>
>> Hi, Mark
>>
>> On Tue, 21 Jul 2020 17:51:41 +0900,
>> Mark Millard via freebsd-ports wrote:
>>>
>>> KIRIYAMA Kazuhiko kiri at true
On 2020-Jul-22, at 00:23, KIRIYAMA Kazuhiko wrote:
> Hi, Mark
>
> On Tue, 21 Jul 2020 17:51:41 +0900,
> Mark Millard via freebsd-ports wrote:
>>
>> KIRIYAMA Kazuhiko kiri at truefc.org wrote on
>> Tue Jul 21 02:33:25 UTC 2020 :
>>
>>> checking
The error report material was:
cc -Isrc/util/ed6d25d@@mesa_util@sta -Isrc/util -I../src/util -Iinclude
-I../include -Isrc -I../src -Isrc/mapi -I../src/mapi -Isrc/mesa -I../src/mesa
-I../src/gallium/include -Isrc/gallium/auxiliary -
I../src/gallium/auxiliary -Xclang -fcolor-diagnostics -pipe
-D_
On 2020-Jul-21, at 01:45, Piotr Kubaj wrote:
> Please try after r542724.
For 32-bit powerpc: devel/libffi built. Some dependent ports have built. (More
are building.)
It will be a while before I try powerpc64: There are 130+ 32-bit ports still to
build. It takes
a while.
> On 20-07-20 16:33
KIRIYAMA Kazuhiko kiri at truefc.org wrote on
Tue Jul 21 02:33:25 UTC 2020 :
> checking for iconv declaration...
> extern size_t iconv (iconv_t cd, char * *inbuf, size_t *inbytesleft,
> char * *outbuf, size_t *outbytesleft);
> *** BFD does not support target native-unknown-freebsd13.0.
On 2020-Jul-20, at 16:13, Piotr Kubaj wrote:
>
> Thanks for your report. I'm currently testing whether powerpc(64) on
> 12.1 and head can build with this patch
> https://github.com/libffi/libffi/commit/01a75ed76ea7e57f1b7a5c183e2b1e890e6aa0fd.patch
FYI: I did the powerpc64 bulk build first an
This resulted in: Failed: 1 Skipped: 181
# poudriere jail -l
JAILNAME VERSION ARCH METHOD TIMESTAMP PATH
FBSDpowerpc 13.0-CURRENT powerpc null 2019-12-31 01:21:28
/usr/obj/DESTDIRs/clang-powerpc-installworld-poud
FBSDpowerpc64 13.0-CURRENT powerpc.
In my poudriere-devel based port upgrade's bulk run I got:
--- .obj/qdrawhelper_neon_asm.o ---
cc: error: unable to execute command: Executable "as" doesn't exist!
cc: error: assembler command failed with exit code 1 (use -v to see invocation)
*** [.obj/qdrawhelper_neon_asm.o] Error code 1
make[1
Thomas Mueller mueller6722 at twc.com wrote on
Fri Jun 19 01:31:47 UTC 2020 :
> > > I do package builds on one machine on my (small) network, using
> > > portmaster [...]
> [...]
> > > And how do I bandage up the foot I shot myself in?
>
> > I understand it might be unpopular, but the preferred w
On 2020-Jun-16, at 22:21, bob prohaska wrote:
> On Tue, Jun 16, 2020 at 09:59:24PM -0700, Mark Millard wrote:
>>
>>
>> On 2020-Jun-16, at 21:34, bob prohaska wrote:
>>
>>> Just noticed there are now two u-boot ports for the RPi3, one
>>> called u-boot-rpi3-32 and (the presumably original) u-b
On 2020-Jun-16, at 21:34, bob prohaska wrote:
> Just noticed there are now two u-boot ports for the RPi3, one
> called u-boot-rpi3-32 and (the presumably original) u-boot-rpi3.
>
> The descriptions are equally bland, what's the difference?
> The goal is to boot a recent snapshot of -current f
On 2020-May-31, at 19:22, bob prohaska wrote:
> Made another attempt to compile www/chromium on a Pi3B, this time using
> a mechanical hard disk for all storage (and boot). It stopped with
>
> ../../third_party/zlib/cpu_features.c:32:10: fatal error: 'asm/hwcap.h' file
> not found
> #include
On 2020-May-20, at 11:16, bob prohaska wrote:
> On Wed, May 20, 2020 at 07:09:11PM +0200, Mika??l Urankar wrote:
>> Le mer. 20 mai 2020 ?? 18:46, bob prohaska a ??crit :
>>>
>>> Is there supposed to be a /dev/io by default in FreeBSD on a Pi3?
>>> Attempts to start X under 12.1-STABLE r36127
On 2020-May-20, at 19:25, bob prohaska wrote:
>
> Which list is the appropriate forum, -ports, -arm or something else?
> If there is a better problem description I'll use it. ISTR xorg
> compiling and running without a hitch on -current previously, ~
> a year ago.
Does not look like I can
20-May-15, at 11:59, Mark Millard wrote:
>>>
>>> On 2020-May-15, at 11:05, bob prohaska wrote:
>>>
>>>> On Fri, May 15, 2020 at 01:49:21PM -0300, Danilo G. Baio wrote:
>>>>> On Fri, May 15, 2020 at 08:19:22AM -0700, bob prohaska wrote:
>&g
o G. Baio wrote:
>>> On Fri, May 15, 2020 at 08:19:22AM -0700, bob prohaska wrote:
>>>> On Fri, May 15, 2020 at 12:33:10AM -0700, Mark Millard via freebsd-ports
>>>> wrote:
>>>>>
>>>>> Some building and isntalling had to occur prior to t
On 2020-May-15, at 11:05, bob prohaska wrote:
> On Fri, May 15, 2020 at 01:49:21PM -0300, Danilo G. Baio wrote:
>> On Fri, May 15, 2020 at 08:19:22AM -0700, bob prohaska wrote:
>>> On Fri, May 15, 2020 at 12:33:10AM -0700, Mark Millard via freebsd-ports
>>> wrote:
&
On 2020-May-15, at 08:19, bob prohaska wrote:
> On Fri, May 15, 2020 at 12:33:10AM -0700, Mark Millard via freebsd-ports
> wrote:
>>
>> Some building and isntalling had to occur prior to the
>> textproc/py-sphinx18 build attempt, possibly from
>> prior session
On 2020-May-15, at 00:33, Mark Millard wrote:
> bob prohaska fbsd at www.zefox.net wrote on
> Fri May 15 04:30:07 UTC 2020 :
>
>> An attempt to compile x11/xorg on a new installation of 12.1 on a Pi3B
>> resulted in a
>> conflict:
>>
>> ===> Installing for py37-sphinx18-1.8.5_1,1
>> ===>
bob prohaska fbsd at www.zefox.net wrote on
Fri May 15 04:30:07 UTC 2020 :
> An attempt to compile x11/xorg on a new installation of 12.1 on a Pi3B
> resulted in a
> conflict:
>
> ===> Installing for py37-sphinx18-1.8.5_1,1
> ===> Checking if py37-sphinx18 is already installed
> ===> Registe
On 2020-May-11, at 11:34, Patrick M. Hausen wrote:
> I’m confused by this thread. isn’t the point of Poudriere
> bulk builds to
When I listed:
# poudriere jail -l
JAILNAME VERSION ARCH METHOD TIMESTAMP PATH
FBSDFSSDjail 13.0-CURRENT amd64 nu
Leander Schaefer info at NetOcean.de wrote on
Tue May 5 20:38:49 UTC 2020 :
> I have been dealing with Poudriere for quite a while and one of the most
> issues I have is, that I have ports which won't compile along with
> another. Reason is mostly something like:
>
> pkg-static: ImageMagick7-7.
1 - 100 of 333 matches
Mail list logo