Re: Large builds with poudriere

2021-05-20 Thread Mark Millard via freebsd-ports
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: >>> > . . . >>> >> >>

Re: Large builds with poudriere

2021-05-20 Thread Mark Millard via freebsd-ports
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

Re: Large builds with poudriere

2021-05-20 Thread Mark Millard via freebsd-ports
LVM_TARGET_RISCV WITHOUT_LLVM_TARGET_X86 vs. WITH_LLVM_TARGET_X86 Some of the mixes would simulate the various devel/llvm* ports BE_NATIVE's intent for various platforms. (BE_NATIVE does not work in all contexts, last I tried it anyway.) === Mark Millard marklmi at y

Re: Large builds with poudriere

2021-05-20 Thread Mark Millard via freebsd-ports
rds, aarch64 was missing. I had to pick BE_STANDARD or BE_FREEBSD to get something that would target aarch64 on aarch64. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___ freebsd-ports@freebsd.org mailing list https://lists

Re: Large builds with poudriere

2021-05-20 Thread Mark Millard via freebsd-ports
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 m

Re: Large builds with poudriere

2021-05-20 Thread Mark Millard via freebsd-ports
> ALLOW_MAKE_JOBS_PACKAGES will let a single package build using more cores. Even when MAKE_JOBS is otherwise disabled: # List of packages that will always be allowed to use MAKE_JOBS # regardless of ALLOW_MAKE_JOBS. This is useful for allowing ports # which holdup the rest of the que

On aarch64: "sysutils/hpacucli dependency on misc/compat4x has wrong PKGNAME"

2021-05-19 Thread Mark Millard via freebsd-ports
: b309895b3544ffba9e8df8786062ec6013c752ff merge-base: CommitDate: 2021-05-17 06:32:36 + b309895b3544 (HEAD -> main, freebsd/main, freebsd/HEAD) x11-themes/kde-icons-black-and-white: add LICENSE, take MAINTAINER n545993 (--first-parent --count for merge-base) === Mark Millard marklmi at yahoo.com ( dsl-only.

Re: Python 37/38 conflict, was Re: Trubles compiling lxqt on RPi4

2021-05-19 Thread Mark Millard via freebsd-ports
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: >>>

Re: Python 37/38 conflict, was Re: Trubles compiling lxqt on RPi4

2021-05-19 Thread Mark Millard via freebsd-ports
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] >> >&

Re: Python 37/38 conflict, was Re: Trubles compiling lxqt on RPi4

2021-05-19 Thread Mark Millard via freebsd-ports
ependencies) and that that pkg has arleady been redirected to use the poudriere-built packages: # pkg delete -a # pkg install `cat file-listing-packages` Technically, I do not know if your environment is so messed up that pkg delete -a would fail. I'll note that if pkg instead still points to the

Re: Python 37/38 conflict, was Re: Trubles compiling lxqt on RPi4

2021-05-17 Thread Mark Millard via freebsd-ports
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 e

Re: Python 37/38 conflict, was Re: Trubles compiling lxqt on RPi4

2021-05-17 Thread Mark Millard via freebsd-ports
are how well it would end up fitting their goals, context, preferences, and so on vs. other alternatives overall. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___ freebsd-ports@freebsd.org mailing list https://lists

Re: Python 37/38 conflict, was Re: Trubles compiling lxqt on RPi4

2021-05-16 Thread Mark Millard via freebsd-ports
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=\$\{R

Re: Python 37/38 conflict, was Re: Trubles compiling lxqt on RPi4

2021-05-16 Thread Mark Millard via freebsd-ports
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

Re: Python 37/38 conflict, was Re: Trubles compiling lxqt on RPi4

2021-05-15 Thread Mark Millard via freebsd-ports
QUOTE There is also: QUOTE -n Do not be recursive -r Remove port options instead of configuring them -s Show port options instead of configuring them END QUOTE See: man poudriere-options === Mark Millard marklmi at yahoo.com ( dsl-only.net went

Re: Python 37/38 conflict, was Re: Trubles compiling lxqt on RPi4

2021-05-15 Thread Mark Millard via freebsd-ports
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? >

Re: Python 37/38 conflict, was Re: Trubles compiling lxqt on RPi4

2021-05-14 Thread Mark Millard via freebsd-ports
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 > > l

Re: Trubles compiling lxqt on RPi4

2021-05-13 Thread Mark Millard via freebsd-ports
: It will not be me that tests such commands for handling such contexts. May be Bob P. will test your sequence. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___ 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: Trubles compiling lxqt on RPi4

2021-05-13 Thread Mark Millard via freebsd-ports
hon37 # REINSTALL="$(pkg info -o "*py37*" | awk '{printf "%s ", $2}')" # pkg delete -f "*py37*" # portmaster $REINSTALL # REBUILD=$(pkg query -g "%n:%dn" '*' | grep py3 | grep -v py38 | cut -d : -f 1 | sort -u) # portmaster $REBUILD #

Re: Troubles compiling lxqt on RPi4 [out of date Mk/Uses/meson.mk in use]

2021-05-13 Thread Mark Millard via freebsd-ports
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

Re: Troubles compiling lxqt on RPi4

2021-05-13 Thread Mark Millard via freebsd-ports
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

Re: Trubles compiling lxqt on RPi4

2021-05-12 Thread Mark Millard via freebsd-ports
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

Re: Trubles compiling lxqt on RPi4

2021-05-12 Thread Mark Millard via freebsd-ports
s, beyond the basicis of the python3 change.) This may get into things like poudriere based builds vs. some other ways of building that are more sensitive to context oddities. But you were not explicit about that aspect of things. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away i

Re: FreeBSD:13:aarch64 packages are outdated

2021-05-11 Thread Mark Millard via freebsd-ports
p://ampere2.nyi.freebsd.org/jail.html?mastername=main-arm64-default === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-por

ports-mgmt/poudriere-devel, lang/rust (for example), and USE_TMPFS that includes wrkdir (or yes)

2021-05-10 Thread Mark Millard via freebsd-ports
MPFS shows over 130 GiBytes in the tmpfs earn the end of the builder's activity. (This is a amd64 context with 128 GiBytes of RAM and 192 GiBytes of swapping/paging space.) === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) _

Re: pkg builders order of jobs

2021-05-10 Thread Mark Millard via freebsd-ports
same text now used in the name. The use of the date/time encoding as a prefix avoids dealing with picking between the port and system "rev-list --first-parent --count" figure or having to list both in some order --and avoids the computational effort to find those counts. === Mark Millard marklmi a

Re: pkg builders order of jobs

2021-05-09 Thread Mark Millard via freebsd-ports
t builds has become much more painful/impractical. (It has never helped that architecture is in a deeper layer but is also partial: only some architectures might build for the commit in question. One has had to inspect to find examples of the architecture of interest.) === Mark Millard marklmi at yah

Re: Xoscope nuisance console messages on Pi4 running -current

2021-05-03 Thread Mark Millard via freebsd-ports
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

Re: Xoscope nuisance console messages on Pi4 running -current

2021-05-03 Thread Mark Millard via freebsd-ports
nsion to 64 bits before the value started being treated as unsigned. If it had used an unsigned type instead, the padding would have been a zero fill instead (presuming that I've guessed right). === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)

Re: When will git be supported for ports?

2021-04-29 Thread Mark Millard via freebsd-ports
s shown. The hashes/links that I supplied were there to copy in the web browser during this sequence, so that I what I did to supply them. > > It's the old saying: Give a man a fish, so he will not be hungry > for a day, teach him to fish and he will be fed for a livetime 8-} I hope that

Re: When will git be supported for ports?

2021-04-28 Thread Mark Millard via freebsd-ports
Dec-03. So it was updated a little from the 2020-Sep blog variant. The changes may not be important. I've not gone through them. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___ freebsd-ports@freebsd.org mailing

Re: SVNWEB not updated for ports

2021-04-19 Thread Mark Millard via freebsd-ports
of lines and it will show the author, committer, dates, and the one-line summary for the commit identified. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___ freebsd-ports@freebsd.org mailing l

Re: devel/llvm10 (and 11) on aarch64: only BE_AMDGPU registered targets despite OPTIONS_FILE_SET+=BE_NATIVE also being set

2021-04-09 Thread Mark Millard via freebsd-ports
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. >

Re: Specific svn/git package update use case

2021-04-09 Thread Mark Millard via freebsd-ports
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 brings in >>> all th

Re: Specific svn/git package update use case

2021-04-08 Thread Mark Millard via freebsd-ports
on a branch does not require doing them one by one to get the net effect. You may want to inspect after checkouts (or similar activity) that "git status" does not display any surprises that need to be cleaned up in the local file system via some variant(s) of git restore or/and git clean

devel/llvm10 (and 11) on aarch64: only BE_AMDGPU registered targets despite OPTIONS_FILE_SET+=BE_NATIVE also being set

2021-04-08 Thread Mark Millard via freebsd-ports
-base: CommitDate: 2021-03-12 20:29:42 + 7381bbee29df (freebsd/main, freebsd/HEAD, pure-src, main) cam: Run all XPT_ASYNC ccbs in a dedicated thread n245444 (--first-parent --count for merge-base) === Mark Millard marklmi at yahoo.com ( dsl-only.net went

Re: Any plan to fix ports git main history compatibility with old GitHub master?

2021-04-05 Thread Mark Millard via freebsd-ports
, etc.)" that was added to the schedule on 2021-04-05 09:12:09 UTC. That might be what you are waiting for. Still not listed as started, last I looked. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___ freebsd-ports@fr

Re: Any plan to fix ports git main history compatibility with old GitHub master?

2021-04-05 Thread Mark Millard via freebsd-ports
___ 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"

Read-only https://cgit.freebsd.org/ports/ accessible now; push access not reported as available yet

2021-04-05 Thread Mark Millard via freebsd-ports
ch have happened yet. "2021Q2 quarterly branch created" is listed last. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/li

Re: gitip usage.

2021-04-04 Thread Mark Millard via freebsd-ports
. Unlike for src, the ports schedule makes no mention of the likes of "Starting pushing to external mirrors (github, gitlab, etc.)". The following *presumes* such will be done but the status of such in unclear. Once github is updated(?) to be tracking the new ports git repository, you may have so

Re: No update for a day on ports?

2021-04-03 Thread Mark Millard via freebsd-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 > >

Re: No update for a day on ports?

2021-04-03 Thread Mark Millard via freebsd-ports
p://${SERVERNAME}/s/${SNAPSHOTHASH}.tgz files exist. But there is not much point to having /usr/sbin/portsnap in the file systems once useful versions of such files are no longer available to fetch. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) _

Re: No update for a day on ports?

2021-04-03 Thread Mark Millard via freebsd-ports
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:54:48PM -0700, Mark

Re: No update for a day on ports?

2021-04-02 Thread Mark Millard via freebsd-ports
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 >>>

Re: No update for a day on ports?

2021-04-02 Thread Mark Millard via freebsd-ports
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-por

Re: No update for a day on ports?

2021-04-02 Thread Mark Millard via freebsd-ports
.git was effectively renamed to /freebsd/freebsd-ports-legacy/ and a new /freebsd/freebsd-ports/ was created that used "main" instead of "master". === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___

Re: No update for a day on ports?

2021-04-01 Thread Mark Millard via freebsd-ports
-- George Be careful: Git-svn-cheatsheet.pdf is about how to use git with a svn server, not with a git server: "Cheatsheet for Git as an SVN Client" The "as an SVN Client" is what says that the server involved is an SVN server. === Mark Millard marklmi at yahoo.com ( dsl-on

Re: www/joomla3 is no longer in the FreeBSD pkg repo

2021-03-04 Thread Mark Millard via freebsd-ports
s that: "This license is governed by the laws of Germany, excluding choice of law rules." I make no claim about any validity of depending on any of the content of the PDFlib-Lite-license.pdf referenced. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___

Re: When did pkg(8) drop support for 12-STABLE?

2021-02-23 Thread Mark Millard via freebsd-ports
nd releng/13.*/ and relelase/13.*/ and main (14) and later: snv can no longer be used to get source. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/m

Re: When did pkg(8) drop support for 12-STABLE?

2021-02-23 Thread Mark Millard via freebsd-ports
last February. > > I > > am > > not sure what build you mean by "12-STABLE" > It was from a 12-STABLE usb stick (probably 12.1). Is there no way forward, > save > building up to 12.2? You might want to report the output of: # uname -apKU if you can sti

Re: bogus warning from pkg

2021-02-15 Thread Mark Millard via freebsd-ports
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

Re: bogus warning from pkg

2021-02-15 Thread Mark Millard via freebsd-ports
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 : > >

Re: bogus warning from pkg

2021-02-15 Thread Mark Millard via freebsd-ports
terial to be distributed to various servers. But I do not know how to track down those times.) Did you happen to to do step 6 before the first FreeBSD:14 ports showed up? If yes, then you were still working against FreeBSD:13 ports from pkg install; if no, then you should have gotten FreeBSD:14 ports. >

Re: bogus warning from pkg

2021-02-15 Thread Mark Millard via freebsd-ports
he FreeBSD servers. But, either way, if I understand right, the warning implies the above (presuming you have not forced a definition of ABI). I'm not sure if a definition of ABI can lead to such notices when it mismatches with the architecture/annotations for pkg. === Mark Millard mark

Re: Bind9 security upgrade

2021-02-07 Thread Mark Millard via freebsd-ports
.so.9 (0x403a5000) libc.so.7 => /lib/libc.so.7 (0x40408000) An incorrectly built dialog4ports will show /usr.lib/libdialog.so.8 instead. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___ freebsd-ports@freebsd.org

Re: Bind9 security upgrade

2021-02-06 Thread Mark Millard via freebsd-ports
ombines some of the features of C, sed, awk and shell. See the manual page for more hype. There are also many books published by O'Reilly & Assoc. See pod/perlbook.pod for more information. WWW: https://www.perl.org/ === Mark Millard marklmi at yahoo.com ( dsl-only.net went away i

Re: Bind9 security upgrade

2021-02-06 Thread Mark Millard via freebsd-ports
in:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/root/bin Thus the error that it reported. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___ freebsd-ports@freebsd.org mailing list https://lists.freeb

Re: "pkg-static: POST-INSTALL script failed" during poudriere based builds: gettext-tools install can attempt use of indexinfo before print/indexinfo is installed for the build

2021-02-04 Thread Mark Millard via freebsd-ports
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/poud

Re: "pkg-static: POST-INSTALL script failed" during poudriere based builds: gettext-tools install can attempt use of indexinfo before print/indexinfo is installed for the build

2021-02-04 Thread Mark Millard via freebsd-ports
nWWW: https://github.com/bapt/indexinfo","categories":["ports-mgmt","print"],"annotations":{"FreeBSD_version":"143"},"files":{"/usr/local/bin/indexinfo":"1$0231cd46617eb332e640aec15dee7f273a675e8f9669154d821613232de51c20","/usr/local/share/licens

Re: "pkg-static: POST-INSTALL script failed" during poudriere based builds: gettext-tools install can attempt use of indexinfo before print/indexinfo is installed for the build

2021-02-04 Thread Mark Millard via freebsd-ports
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/p

Re: "pkg-static: POST-INSTALL script failed" during poudriere based builds: gettext-tools install can attempt use of indexinfo before print/indexinfo is installed for the build

2021-02-04 Thread Mark Millard via freebsd-ports
issing as far as I can tell. If so, it needs to be added. > Mark Millard wrote on 2021/02/05 07:58: >> >> >> On 2021-Feb-4, at 14:44, Tatsuki Makino >> wrote: >> >>> Hello. >>> >>> It's the one that happens when environment variable PA

Re: "pkg-static: POST-INSTALL script failed" during poudriere based builds: gettext-tools install can attempt use of indexinfo before print/indexinfo is installed for the build

2021-02-04 Thread Mark Millard via freebsd-ports
k/.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: >>

"pkg-static: POST-INSTALL script failed" during poudriere based builds: gettext-tools install can attempt use of indexinfo before print/indexinfo is installed for the build

2021-02-04 Thread Mark Millard via freebsd-ports
ying to update an old PowerMac powerpc64 context to FreeBSD:14 based ABI builds for ports.) === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinf

Re: Warning: Major OS version upgrade detected

2021-01-30 Thread Mark Millard via freebsd-ports
would seem unlikely you could have picked up a pkg that was built for/from stable/13 or main as 14-CURRENT on Jan-22nd or soon after. This leaves me curious about what to avoid at such transitions. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) __

Re: math/suitesparse from ports head -r557893 fails for armv7 by default: "/usr/local/bin/ld: cannot find -lomp"

2020-12-14 Thread Mark Millard via freebsd-ports
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

math/suitesparse from ports head -r557893 fails for armv7 by default: "/usr/local/bin/ld: cannot find -lomp"

2020-12-14 Thread Mark Millard via freebsd-ports
obj/cortexA72_clang/arm64.aarch64/usr/src/arm64.aarch64/sys/GENERIC-NODBG arm64 aarch64 1300131 1300131 === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.

Re: DEFAULT_VERSIONS+=llvm=90 ignored?

2020-12-05 Thread Mark Millard via freebsd-ports
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

Re: DEFAULT_VERSIONS+=llvm=90 ignored?

2020-12-05 Thread Mark Millard via freebsd-ports
n for things using the LLVM API. Having all ports using the same LLVM API release is probably not an option (upstream issues). In other words: software that chooses to be in part based on the LLVM API tends to lead to needing various vintages of LLVM to be installed. === Mark Millard marklmi at yahoo.

Re: How to build sysutils/edk2@rpi4 (for example) that matches https://github.com/pftf/RPi4/releases/tag/v1.18 (for example)

2020-08-15 Thread Mark Millard via freebsd-ports
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

Re: How to build sysutils/edk2@rpi4 (for example) that matches https://github.com/pftf/RPi4/releases/tag/v1.18 (for example)

2020-08-11 Thread Mark Millard via freebsd-ports
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.co

How to build sysutils/edk2@rpi4 (for example) that matches https://github.com/pftf/RPi4/releases/tag/v1.18 (for example)

2020-08-11 Thread Mark Millard via freebsd-ports
ased on using a personal uefi/acpi build that I was given access to. I've no clue how to reproduce it from what source. I've no clue what would be good to build for @macchiatobin use. (It need not match what is good for the RPi3 and RPi4 as far as I can tell, although such might work currently(?).)

Re: security/nss build failure under poudriere, "symlink creation race", head -r363590 FreeBSD and head -r543636 ports

2020-07-31 Thread Mark Millard via freebsd-ports
made a difference would be problematical: failure is rare without MAKE_JOBS_UNSAFE in my context. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mail

Re: security/nss build failure under poudriere, "symlink creation race", head -r363590 FreeBSD and head -r543636 ports

2020-07-30 Thread Mark Millard via freebsd-ports
gt; Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to > the maintainer. > *** Error code 1 > > Stop. > make: stopped in /usr/ports/security/nss > > > I don't know why it's trying to run the command twice against nssckfw.h. > ===

security/nss build failure under poudriere, "symlink creation race", head -r363590 FreeBSD and head -r543636 ports

2020-07-29 Thread Mark Millard via freebsd-ports
ink %s", toname); } . . . The "goto retry" is odd given the "fail" use and: void fail(char *format, ...) { . . . abort(); exit(1); } The poudriere bulk is still going, building other things. So it will be some time before I find out if this rep

Re: 32-bit powerpc graphics/mesa-dri build failure (poudriere based): "error: cannot redeclare builtin function" (e.g., __sync_add_and_fetch_8)

2020-07-23 Thread Mark Millard via freebsd-ports
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-p

Re: 32-bit powerpc graphics/mesa-dri build failure (poudriere based): "error: cannot redeclare builtin function" (e.g., __sync_add_and_fetch_8)

2020-07-23 Thread Mark Millard via freebsd-ports
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.

Re: 32-bit powerpc graphics/mesa-dri build failure (poudriere based): "error: cannot redeclare builtin function" (e.g., __sync_add_and_fetch_8)

2020-07-22 Thread Mark Millard via freebsd-ports
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' >>> _

Re: 32-bit powerpc graphics/mesa-dri build failure (poudriere based): "error: cannot redeclare builtin function" (e.g., __sync_add_and_fetch_8)

2020-07-22 Thread Mark Millard via freebsd-ports
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) >> ^ >&g

Re: Why lang/gcc9 depends native-binutils ?

2020-07-22 Thread Mark Millard via freebsd-ports
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

Re: Why lang/gcc9 depends native-binutils ?

2020-07-22 Thread Mark Millard via freebsd-ports
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

32-bit powerpc graphics/mesa-dri build failure (poudriere based): "error: cannot redeclare builtin function" (e.g., __sync_add_and_fetch_8)

2020-07-21 Thread Mark Millard via freebsd-ports
un, 12 Jul 2020) === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "fr

Re: devel/libffi build broken for head -r363123 32-bit powerpc contexts (poudriere bulk): error: __int128 is not supported on this target

2020-07-21 Thread Mark Millard via freebsd-ports
-20 16:33:27, Mark Millard wrote: >> >> >> 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/

Re: Why lang/gcc9 depends native-binutils ?

2020-07-21 Thread Mark Millard via freebsd-ports
not what was reported as involved. I've ignored CROSS_TOOLCHAIN infrastructure as it was not mentioned as being in use. I do not see how devel/binutils/Makefile would generate "native-unknown-freebsd13.0" text on its own. Sorry I've not been able to identify anything for the error. I'

Re: devel/libffi build broken for head -r363123 32-bit powerpc contexts (poudriere bulk): error: __int128 is not supported on this target

2020-07-20 Thread Mark Millard via freebsd-ports
to a pointer in some contexts, unlike what __float128 or __int128 would have done. > On 20-07-20 15:27:01, Mark Millard wrote: >> This resulted in: Failed: 1 Skipped: 181 >> >> # poudriere jail -l >> JAILNAME VERSION ARCH METHOD TIMESTAMP

devel/libffi build broken for head -r363123 32-bit powerpc contexts (poudriere bulk): error: __int128 is not supported on this target

2020-07-20 Thread Mark Millard via freebsd-ports
"--enable-new-dtags" "-m" "elf32ppc_fbsd" "-o" "a.out" "/usr/lib/crt1.o" "/usr/lib/crti.o" "/usr/lib/crtbegin.o" "-L/usr/lib" "/dev/null" "-lc++" "-lm" "-lgcc" "--a

armv7: x11-toolkits/qt5-gui still blocked by 'unable to execute command: Executable "as" doesn't exist!' for .obj/qdrawhelper_neon_asm.o and .obj/pixman-arm-neon-asm.o

2020-07-15 Thread Mark Millard via freebsd-ports
${MAKE_ARGS} ${INSTALL_TARGET} .endfor -.include +.include + +.if ${ARCH} == "armv6" || ${ARCH} == "armv7" +BUILD_DEPENDS+= ${LOCALBASE}/bin/as:devel/binutils +.endif + +.include === Mark Millard marklmi at yahoo.com (

Re: Jumbled dependencies

2020-06-18 Thread Mark Millard via freebsd-ports
/var/db/ports/*_*/options files. > I once got a royal mess of circular/jumbled dependencies with dialog4ports; > cleaning was a major nuisance, nothing simple like editing /etc/mk.conf or > /etc/make.conf . > > I never used pkgsrc with any OS other than NetBSD but

Re: Which u-boot for rpi3? u-boot-rpi3-32 or the old one?

2020-06-17 Thread Mark Millard via freebsd-ports
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

Re: Which u-boot for rpi3? u-boot-rpi3-32 or the old one?

2020-06-16 Thread Mark Millard via freebsd-ports
r use with aarch64 FreeBSD B) sysutils/u-boot-rpi3-32 is for use with armv7 FreeBSD === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/list

Re: 'asm/hwcap.h' file not found building chromium on Pi3

2020-05-31 Thread Mark Millard via freebsd-ports
so it seems the problem would be considered to be in the port instead. I've no clue what a proper alternative would be for third_party/zlib/cpu_features.c to use in a FreeBSD context. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) __

Re: Missing /dev/io on rpi3 running 12-stable

2020-05-23 Thread Mark Millard via freebsd-ports
I versions" information. So your failing context is either devd based or still has the environment configured for HAL or is otherwise messed up such that udev is not in use. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)

Re: Missing /dev/io on rpi3 running 12-stable

2020-05-20 Thread Mark Millard via freebsd-ports
I have. I'm not so sure any of it will happen to help. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscr

Re: Conflict on very first port (xorg) on rpi3

2020-05-15 Thread Mark Millard via freebsd-ports
On 2020-May-15, at 13:03, bob prohaska wrote: > On Fri, May 15, 2020 at 12:33:02PM -0700, Mark Millard wrote: >> [Gack: devel/cmake needs devel/py-sphinx by default >> and devel/llvm80 needs both devel/cmake and >> devel/py-pshinx18 by default.] >> >> On 20

Re: Conflict on very first port (xorg) on rpi3

2020-05-15 Thread Mark Millard via freebsd-ports
[Gack: devel/cmake needs devel/py-sphinx by default and devel/llvm80 needs both devel/cmake and devel/py-pshinx18 by default.] On 2020-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, Danil

Re: Conflict on very first port (xorg) on rpi3

2020-05-15 Thread Mark Millard via freebsd-ports
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 >>> wrot

Re: Conflict on very first port (xorg) on rpi3

2020-05-15 Thread Mark Millard via freebsd-ports
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

Re: Conflict on very first port (xorg) on rpi3

2020-05-15 Thread Mark Millard via freebsd-ports
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: >> >> ===&g

Re: Conflict on very first port (xorg) on rpi3

2020-05-15 Thread Mark Millard via freebsd-ports
proc/py-sphinx* difference in requirements. The conflict is real and limits what combinations of ports you may have installed at the same time. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___ freebsd-ports@freebsd.org

Re: Poudriere - Compile ALL Ports

2020-05-11 Thread Mark Millard via freebsd-ports
a "null" METHOD where I'm supplying my own materials. Again it allows for testing development materials that are not checked into svn. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___ freebsd-ports@free

Re: Poudriere - Compile ALL Ports

2020-05-11 Thread Mark Millard via freebsd-ports
e same problems with having pre-existing material in an equivalent of my /usr/obj/DESTDIRs/clang-amd64-installworld-poud/usr/local/ area. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___ freebsd-ports@freebsd.

  1   2   3   4   5   6   >