Re: ld (a.k.a. ld.lld) for amd64 -r325369 -> aarch64 cross buildworld is messed up: ld just says "Invalid argument" [vs. binutils ld: R_AARCH64_ABS64 used with TLS symbol]

[Forcing use of /usr/local/aarch64-freebsd/bin/ld and other aarch64-binutils-2.28,1 material for the aarch64 links: that fails too, but with messages that are more informative (but might be independent): "R_AARCH64_ABS64 used with TLS symbol".] > On 2017-Nov-3, at 9:24 PM, Mark Millard wrote: >

release(7) targets busted

> *** FATAL ERROR: Cannot 'cd' to /root/git/freebsd/release/.. and install > files to > the temproot environment > > If you run into an issue like that with the make release targets, here's a fix: http://people

ld (a.k.a. ld.lld) for amd64 -r325369 -> aarch64 cross buildworld is messed up: ld just says "Invalid argument" (input files for libc.so.7.full)

Context: # uname -apKU FreeBSD FreeBSDx64OPC 12.0-CURRENT FreeBSD 12.0-CURRENT r325369M amd64 amd64 1200052 1200052 Problem: While I show the buildworld error report later, even simple ld commands that list a input file to the amd64 -> aarch64 cross build's ld (a.k.a. ld.lld) file get messag

Re: Head build unsafe for /etc today

On 11/2/2017 8:58 PM, Warner Losh wrote: > FreeBSD has grown too big to test every possible thing before you commit. The build itself is massive. I usually forget about release/ and the new 'make packages', external toolchain, "old style" kernel builds, etc. Steve's concerns have validity. I d

Re: pcsc-lite hangs up after unplugging an USB card reader

Hello, Le 01/11/2017 à 12:05, Jairo Montes González a écrit : Jairo Montes schrieb am 01.11.2017 11:04 _ The output from "procstat -ak" is attached to this email. As you might see, I'm trying to debug it, but this is my first

sys/boot machine symlink dirs causing rebuild [was Re: Example of Bryan Drewery's "Something is very wrong" ...]

On 11/3/2017 12:42 PM, Mark Millard wrote: > On 2017-Nov-3, at 11:31 AM, Bryan Drewery wrote: > >> On 11/3/17 1:52 AM, Mark Millard wrote: >>> I did get another problem after buildworld, buildkernel, installkernel >>> without future source code dates: the installworld got a "cc not found" >>> for

Re: Example of Bryan Drewery's "Something is very wrong" (from his disabling head/Makefile)?: obj-cross-tools path referenced but file is under obj-bootstrap-tools

On 2017-Nov-3, at 11:31 AM, Bryan Drewery wrote: > On 11/3/17 1:52 AM, Mark Millard wrote: >> I did get another problem after buildworld, buildkernel, installkernel >> without future source code dates: the installworld got a "cc not found" >> for the amd64 native build based on -r325351 --that al

Re: Example of Bryan Drewery's "Something is very wrong" (from his disabling head/Makefile)?: obj-cross-tools path referenced but file is under obj-bootstrap-tools

On 11/3/17 1:52 AM, Mark Millard wrote: > I did get another problem after buildworld, buildkernel, installkernel > without future source code dates: the installworld got a "cc not found" > for the amd64 native build based on -r325351 --that also appears to be > set up to report: > > ERROR-tried-to

Re: Emacs and LLD

On Fri, Nov 3, 2017, at 16:59, Hans Petter Selasky wrote: > On 11/03/17 16:29, Tobias Kortkamp wrote: > > Hi, > > > > I cannot build editors/emacs-nox11 (or any other Emacs port) on FreeBSD > > 12 anymore for several months now. The build aborts with: > > > > ./temacs --batch --load loadup boots

Re: Emacs and LLD

On 11/03/17 16:29, Tobias Kortkamp wrote: Hi, I cannot build editors/emacs-nox11 (or any other Emacs port) on FreeBSD 12 anymore for several months now. The build aborts with: ./temacs --batch --load loadup bootstrap Fatal error 'Can't allocate initial thread' at line 337 in file /usr/src/lib/

Emacs and LLD

Hi, I cannot build editors/emacs-nox11 (or any other Emacs port) on FreeBSD 12 anymore for several months now. The build aborts with: ./temacs --batch --load loadup bootstrap Fatal error 'Can't allocate initial thread' at line 337 in file /usr/src/lib/libthr/thread/thr_init.c (errno = 12) gmake[

Re: Example of Bryan Drewery's "Something is very wrong" (from his disabling head/Makefile)?: obj-cross-tools path referenced but file is under obj-bootstrap-tools

I did get another problem after buildworld, buildkernel, installkernel without future source code dates: the installworld got a "cc not found" for the amd64 native build based on -r325351 --that also appears to be set up to report: ERROR-tried-to-rebuild-during-make-install if cc had been found: