Moin-moin!
After upgrade to recent -current (153) I've got a ld error for 32bit an
aarch64 machine:(
ELF binary type "9" not known.
eval: /libexec/ld-elf32.so.1: Exec format error
Snapshot from 2023-10-13 was fine, no errors
15.0-CURRENT #0 main-6f38d2e7b0: Thu Nov 16 03:29:03 MSK 2023 is
gcc-depended
stuff on my box.
Tested gcc11-devel, gcc12-devel, gcc13-devel
On 14.04.2023 00:42, Dima Panov wrote:
Moin-moin!
Somethings changed in main branch between Mar, 28 and Apr, 8 which causes
permanent build error for lang/gcc1[012] on aarch64 (exactly VMWare container
on M1Pro mac
Moin-moin!
On 14.04.2023 01:13, Dimitry Andric wrote:
On 13 Apr 2023, at 23:42, Dima Panov wrote:
Somethings changed in main branch between Mar, 28 and Apr, 8 which causes
permanent build error for lang/gcc1[012] on aarch64 (exactly VMWare container
on M1Pro mac)
during RTL pass: sched1
Moin-moin!
Somethings changed in main branch between Mar, 28 and Apr, 8 which causes
permanent build error for lang/gcc1[012] on aarch64 (exactly VMWare container
on M1Pro mac)
during RTL pass: sched1
gimple-match.cc: In function 'bool gimple_nop_atomic_bit_test_and_p(tree,
tree_node**, tree_
Moin!
On 23.05.2022 19:03, Dimitry Andric wrote:
On 23 May 2022, at 17:53, Tomoaki AOKI wrote:
After some discussion with Mark Millard on Bug 263976 and some tests,
I've changed the subject of it to "editors/libreoffice: Fails to build
if LLVM_DEFAULT=90 (default) and LTO=on (non-default)".
W
Moin!
As maintainer of libreoffice I have my 2¢ to say.
It builds fine on a recent -current with clang14,
https://build.dimapanov.com/poudriere//data/140amd64-dimaports/2022-05-21_19h50m37s/logs/libreoffice-7.3.3.2_1.log
However, all my own builds run without LTO enabled, it might matters
On 2
Moin!
I saw a such issue on amd64, both 13.0-RELEASE and -CURRENT.
Both hosts have zfsd enabled, and after devd die by signal 15 all other daemons
such as sshd, crond, syslogd (almost all runned daemons) stopeed by signal 15
too. At least, as it shows by system logs.
Will try to play with zfsd
Moin!
Stefan, please add check for __FreeBSD_version and fill PR or commit it
directly with ports-secteam approval.
--
Dima. (desktop, kde, x11, office, ports-secteam)@FreeBSD team
(flu...@freebsd.org, https://t.me/dima_panov)
> On Tuesday, Jan 26, 2021 at 8:37 PM, Stefan Esser (mailto:s...@fr
24.08.2012 19:12, Dimitry Andric пишет:
On 2012-08-24 05:55, Dima Panov wrote:
Does anybody get same error at buildworld with recent -current?
...
In file included from /usr/src/lib/libc/../../include/rpc/rpc.h:76:
/usr/src/lib/libc/../../include/rpc/rpcb_clnt.h:69:8: error: unknown
type name
0 r238449M: Sat Jul 14 23:34:39
VLAT 2012
CLANG_IS_CC
Full buildlog at http://fluffy.homeunix.net/~fluffy/files/screenlog.0
--
Dima Panov (flu...@freebsd.org)
(KDE, Office)@FreeBSD team
Facebook: http://www.facebook.com/fluffy.khv
IRC: fluffy@EFNet, fluffykhv@FreeNode
twitter: fluffy_khv | skype:
:
>> $FreeBSD: src/sys/dev/ath/if_ath.c,v 1.302 2011/03/02 17:19:54 adrian Exp $
>
> Ok, so between r219318 (today) and r218779 (2011-02-18).
>
> Would you please first test r218779 and verify that performance is (back to)
> fine?
--
Dima Pa
n -- h
ath_prom_read [-i ifname] -d
[root@Beastie] ~# ath_prom_read -d ar9285
ath_prom_read: ath0: Invalid argument
[root@Beastie] ~#
FreeBSD 9.0-900030-CURRENT #0 r217695M: Sat Jan 22 13:57:57 VLAT 2011
--
Dima Panov (flu...@freebsd.org)
KDE@FreeBSD t
hello!
22.01.2011, 22:19, "Adrian Chadd" :
> So it's all completely stable for you too right now?
>
Yes, almost 7 hours with new kernel and no errors.
Stable as all previous revisions.
Wait a 802.11n support to utilize it with my home and office hotspots :)
> adrian
atheros wifi card.
> I'd like to make sure I fix all regressions before I start bringing
> over more code from ath9k in preparation for enabling the basic
> 802.11n support for testing.
--
Dima Panov (flu...@freebsd.org)
KDE@FreeBSD team
Facebook: http://www.facebook.com/?id=1000
On Friday 18 June 2010 18:46:49 Jan Henrik Sylvester wrote:
> On 01/-10/-28163 20:59, Doug Barton wrote:
> > 3. kdepim4 My understanding is that the version currently under
> > development has support for libassuan 2.0.0, and will be released in
> > August. The kde@ folks have indicated that if the
On Thursday 06 May 2010 04:13:57 Roman Divacky wrote:
> fwiw, it looks like it may make sense to have 2nd round of runtime testing
> :)
>
> these things were fixed in clangbsd that were reported as problems:
>
> 1) static binaries (eg. make) crash
>
> 2) kernel sound module miscompilation
>
> 3
On Thursday 29 April 2010 02:40:24 Dima Panov wrote:
> On Wednesday 28 April 2010 23:16:38 Ollivier Robert wrote:
> > According to Dima Panov:
> > > while building lang/ruby18:
> > Which options to you use?
> >
> > _OPTIONS_READ=ruby+oniguruma-1.8.
On Wednesday 28 April 2010 23:16:38 Ollivier Robert wrote:
> According to Dima Panov:
> > while building lang/ruby18:
> Which options to you use?
>
> _OPTIONS_READ=ruby+oniguruma-1.8.7.248_1,1
> WITHOUT_ONIGURUMA=true
> WITH_RDOC=true
> WITHOUT_DEBUG=true
>
> I
On Saturday 17 April 2010 03:08:18 Roman Divacky wrote:
> Hi,
>
> ClangBSD is a branch of FreeBSD that aims at integrating clang
> (clang.llvm.org) into FreeBSD, replacing GCC as a system compiler.
>
> Recently, we've achieved the state when clang can compile all of FreeBSD
> world on i386/amd64
19 matches
Mail list logo
