fatal error: 'cpuid.h' file not found
Trying "make -j8 buildworld" with a very recent tree (revision 366156). This fails with /usr/src/sys/contrib/openzfs/lib/libspl/include/sys/simd.h:34:10: fatal error: 'cpuid.h' file not found #include Could this be related to the flags I am using (in particular not building CLANG)? $ cat /etc/make.conf MALLOC_PRODUCTION=yes WITH_CCACHE_BUILD=yes CCACHE_DIR=/usr/obj/ccache $ cat /etc/src.conf WITHOUT_CLANG=yes $ cat /etc/src-env.conf WITH_META_MODE=yes I do kldload filemon before buildworld. Trying minimize incremental build time and don't really care to build clang every time. [I'd appreciate any advice on how to further cut down the build time] If it matters, I am using the cgit-beta tree. Thanks! ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: error pulling from the Beta git repo
Patrick McMunn wrote in : |I'm using the beta git repo at , and I have been compiling source in that |directory. Today, when I ran "git pull", it errored out instead of updating |fully. I don't know if the error was a result of me building in the |directory, but it seems like a reasonable possibility. It was never an |issue with SVN, but should I build the source in a separate directory to |avoid problems with git? I don't know if git keeps a log that I can check |for the full output. If it does, I'd check if I knew the location. As it |is, I only have the partial output still present in my terminal window. $ git clean -fxd [--dry-run] $ [git reset --hard HEAD] $ [git fetch -vv] $ [git gc [--aggressive --prune=all]] $ git checkout -B local-branch-name origin/branch-name [Or git update-ref local-branch-name refs/remotes/origin/branch-name] Alternatively just use a bare repository as a database and several different checked-out working directories somewhere else. Btw. the Linux distro i use has a git driver for its ports system, it goes like that: cd "$REPOSITORY" 2> "/dev/null" if [ $? -lt 1 ]; then git checkout -q "$BRANCH" git fetch -q git diff --pretty=format: --name-status "$BRANCH" origin/"$BRANCH" | sed "s/M\t/ Edit /g; s/A\t/ Checkout /g; s/D\t/ Delete /g" | sort git clean -q -f git reset -q --hard origin/"$BRANCH" gc= else git clone -q -b "$BRANCH" "$URL" "$REPOSITORY" ls -1 $REPOSITORY | sed "s/^/ Checkout /" gc=--aggressive fi git gc --quiet $gc --prune=all That gc stuff is a local addition of mine, i hate stale stuff. Good night. --steffen | |Der Kragenbaer,The moon bear, |der holt sich munter he cheerfully and one by one |einen nach dem anderen runter wa.ks himself off |(By Robert Gernhardt) ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
error pulling from the Beta git repo
I'm using the beta git repo at , and I have been compiling source in that directory. Today, when I ran "git pull", it errored out instead of updating fully. I don't know if the error was a result of me building in the directory, but it seems like a reasonable possibility. It was never an issue with SVN, but should I build the source in a separate directory to avoid problems with git? I don't know if git keeps a log that I can check for the full output. If it does, I'd check if I knew the location. As it is, I only have the partial output still present in my terminal window. Following is the last portion of the output if it helps to identify the error and its cause: Auto-merging crypto/openssl/crypto/x509v3/v3_purp.c CONFLICT (content): Merge conflict in crypto/openssl/crypto/x509v3/v3_purp.c CONFLICT (rename/delete): crypto/x509/x_pubkey.c deleted in 2541f3df33872528e8bd003b97a78668119f812d and renamed to crypto/openssl/crypto/x509/x_pubkey.c in HEAD. Version HEAD of crypto/openssl/crypto/x509/x_pubkey.c left in tree. Auto-merging crypto/openssl/crypto/x509/x509_vfy.c CONFLICT (content): Merge conflict in crypto/openssl/crypto/x509/x509_vfy.c CONFLICT (rename/delete): crypto/x509/x509_local.h deleted in 2541f3df33872528e8bd003b97a78668119f812d and renamed to crypto/openssl/crypto/x509/x509_local.h in HEAD. Version HEAD of crypto/openssl/crypto/x509/x509_local.h left in tree. CONFLICT (rename/delete): crypto/whrlpool/wp_block.c deleted in 2541f3df33872528e8bd003b97a78668119f812d and renamed to crypto/openssl/crypto/whrlpool/wp_block.c in HEAD. Version HEAD of crypto/openssl/crypto/whrlpool/wp_block.c left in tree. Auto-merging crypto/openssl/crypto/ui/ui_openssl.c CONFLICT (content): Merge conflict in crypto/openssl/crypto/ui/ui_openssl.c CONFLICT (rename/delete): crypto/ts/ts_rsp_sign.c deleted in 2541f3df33872528e8bd003b97a78668119f812d and renamed to crypto/openssl/crypto/ts/ts_rsp_sign.c in HEAD. Version HEAD of crypto/openssl/crypto/ts/ts_rsp_sign.c left in tree. CONFLICT (rename/delete): crypto/store/store_lib.c deleted in 2541f3df33872528e8bd003b97a78668119f812d and renamed to crypto/openssl/crypto/store/store_lib.c in HEAD. Version HEAD of crypto/openssl/crypto/store/store_lib.c left in tree. CONFLICT (rename/delete): crypto/store/loader_file.c deleted in 2541f3df33872528e8bd003b97a78668119f812d and renamed to crypto/openssl/crypto/store/loader_file.c in HEAD. Version HEAD of crypto/openssl/crypto/store/loader_file.c left in tree. CONFLICT (rename/delete): crypto/rsa/rsa_ameth.c deleted in 2541f3df33872528e8bd003b97a78668119f812d and renamed to crypto/openssl/crypto/rsa/rsa_ameth.c in HEAD. Version HEAD of crypto/openssl/crypto/rsa/rsa_ameth.c left in tree. CONFLICT (rename/delete): crypto/rand/rand_local.h deleted in 2541f3df33872528e8bd003b97a78668119f812d and renamed to crypto/openssl/crypto/rand/rand_local.h in HEAD. Version HEAD of crypto/openssl/crypto/rand/rand_local.h left in tree. CONFLICT (rename/delete): crypto/rand/drbg_lib.c deleted in 2541f3df33872528e8bd003b97a78668119f812d and renamed to crypto/openssl/crypto/rand/drbg_lib.c in HEAD. Version HEAD of crypto/openssl/crypto/rand/drbg_lib.c left in tree. CONFLICT (rename/delete): crypto/rand/drbg_ctr.c deleted in 2541f3df33872528e8bd003b97a78668119f812d and renamed to crypto/openssl/crypto/rand/drbg_ctr.c in HEAD. Version HEAD of crypto/openssl/crypto/rand/drbg_ctr.c left in tree. CONFLICT (add/add): Merge conflict in crypto/openssl/crypto/pem/pvkfmt.c Auto-merging crypto/openssl/crypto/pem/pvkfmt.c Auto-merging crypto/openssl/crypto/pem/pem_pkey.c CONFLICT (content): Merge conflict in crypto/openssl/crypto/pem/pem_pkey.c Auto-merging crypto/openssl/crypto/pem/pem_lib.c CONFLICT (content): Merge conflict in crypto/openssl/crypto/pem/pem_lib.c Auto-merging crypto/openssl/crypto/o_time.c CONFLICT (content): Merge conflict in crypto/openssl/crypto/o_time.c CONFLICT (rename/delete): crypto/modes/xts128.c deleted in 2541f3df33872528e8bd003b97a78668119f812d and renamed to crypto/openssl/crypto/modes/xts128.c in HEAD. Version HEAD of crypto/openssl/crypto/modes/xts128.c left in tree. CONFLICT (rename/delete): crypto/modes/ofb128.c deleted in 2541f3df33872528e8bd003b97a78668119f812d and renamed to crypto/openssl/crypto/modes/ofb128.c in HEAD. Version HEAD of crypto/openssl/crypto/modes/ofb128.c left in tree. CONFLICT (rename/delete): crypto/modes/modes_local.h deleted in 2541f3df33872528e8bd003b97a78668119f812d and renamed to crypto/openssl/crypto/modes/modes_local.h in HEAD. Version HEAD of crypto/openssl/crypto/modes/modes_local.h left in tree. CONFLICT (rename/delete): crypto/modes/gcm128.c deleted in 2541f3df33872528e8bd003b97a78668119f812d and renamed to crypto/openssl/crypto/modes/gcm128.c in HEAD. Version HEAD of crypto/openssl/crypto/modes/gcm128.c left in tree. CONFLICT (rename/delete): crypto/modes/ctr128.c deleted in 2541f3df33872528e8bd003b97a78668119f812d and renamed to crypto/openssl/crypto/modes/ctr128.c in HEAD. Version HEAD of
BROKEN DESKTOP
FreeBSD Free_BSD_13 13.0-CURRENT FreeBSD 13.0-CURRENT #0 r366158: Fri Sep 25 12:23:15 EDT 2020 root@Free_BSD_13:/usr/obj/usr/src/amd64.amd64/sys/MYKERNEL.bak amd64 1300117 After a recent upgrade of base system, kernel and all ports my desktop is broken. >From log: Sep 25 14:25:17 Free_BSD_13 mate-session[78320]: WARNING: Could not connect to ConsoleKit: Could not get owner of name 'org.freedesktop.ConsoleKit': no such name Sep 25 14:25:17 Free_BSD_13 syslogd: last message repeated 1 times Sep 25 14:25:17 Free_BSD_13 mate-session[78320]: WARNING: Unable to find provider '' of required component 'dock' Sep 25 14:25:18 Free_BSD_13 gnome-keyring-daemon[85947]: The PKCS#11 component was already initialized Sep 25 14:25:18 Free_BSD_13 gnome-keyring-daemon[85947]: The Secret Service was already initialized Sep 25 14:25:18 Free_BSD_13 gnome-keyring-daemon[85947]: The SSH agent was already initialized Sep 25 14:25:18 Free_BSD_13 console-kit-daemon[4901]: CRITICAL: polkit_authority_check_authorization: assertion 'POLKIT_IS_AUTHORITY (authority)' failed Now nothing is working, does anyone have an idea how to fix this? ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: How to find out the revision for HEAD after build-snapshots-from-git?
On Fri, 25 Sep 2020 21:13:28 +0300 xto...@hotmail.com wrote: > Sergey V. Dyatko wrote: > > Hi, > > > > Possible I missed the answer to my question, sorry. But > > Today I installed FreeBSD from > > FreeBSD-13.0-CURRENT-amd64-20200924-3c514403bef-disc1 > > and now I want to rebuild kernel and so on BUT I don't know which SVN > > revision should I checkout. > > uname -a output: > > > > FreeBSD my.host.name 13.0-CURRENT FreeBSD 13.0-CURRENT #0 > > 3c514403bef-c253353(main): Thu Sep 24 06:45:17 UTC 2020 > > r...@releng1.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 > > > > r253353 looks too old, I suppose... > > There certainly should be easier way, but as a quick "fix", try > searching for commit hash: > > https://cgit-beta.freebsd.org/src/log/?qt=range=3c514403bef Looks amazing! but i'm not an Alien, I'm just a human... It is r366075, right ? Thanks! -- wbr, Sergey ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: How to find out the revision for HEAD after build-snapshots-from-git?
Sergey V. Dyatko wrote: Hi, Possible I missed the answer to my question, sorry. But Today I installed FreeBSD from FreeBSD-13.0-CURRENT-amd64-20200924-3c514403bef-disc1 and now I want to rebuild kernel and so on BUT I don't know which SVN revision should I checkout. uname -a output: FreeBSD my.host.name 13.0-CURRENT FreeBSD 13.0-CURRENT #0 3c514403bef-c253353(main): Thu Sep 24 06:45:17 UTC 2020 r...@releng1.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 r253353 looks too old, I suppose... There certainly should be easier way, but as a quick "fix", try searching for commit hash: https://cgit-beta.freebsd.org/src/log/?qt=range=3c514403bef ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
How to find out the revision for HEAD after build-snapshots-from-git?
Hi, Possible I missed the answer to my question, sorry. But Today I installed FreeBSD from FreeBSD-13.0-CURRENT-amd64-20200924-3c514403bef-disc1 and now I want to rebuild kernel and so on BUT I don't know which SVN revision should I checkout. uname -a output: FreeBSD my.host.name 13.0-CURRENT FreeBSD 13.0-CURRENT #0 3c514403bef-c253353(main): Thu Sep 24 06:45:17 UTC 2020 r...@releng1.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 r253353 looks too old, I suppose... -- wbr, Sergey ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: iflib/bridge kernel panic
Sergey V. Dyatko wrote: On Mon, 21 Sep 2020 09:57:40 +0200 "Kristof Provost" wrote: On 21 Sep 2020, at 2:52, Shawn Webb wrote: From latest HEAD on a Dell Precision 7550 laptop: https://gist.github.com/lattera/a0803f31f58bcf8ead51ac1ebbc447e2 The last working boot environment was 14 Aug 2020. If I get some time to bisect commits, I'll try to figure out the culprit. Try https://reviews.freebsd.org/D26418 Best regards, Kristof I'm not sure, but doesn't this panic have the same root as mine? Sorry, but I haven't text console and can post only screenshot[s] from IP-KVM https://gyazo.com/fee41c5267e9fc543d43901e498b7c94 rc.conf have something like: clonned_interfaces="lagg0 vlan101" ifconfig_lagg0="laggproto lacp laggport em0 laggport em1 x.x.x.x/mask" ifconfig_vlan101="vlan 101 vlandev lagg0 192.168.1.29/24" without VLAN part all works fine. Installed from FreeBSD-13.0-CURRENT-amd64-20200924-3c514403bef-disc1.iso Yes, same panic. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: iflib/bridge kernel panic
On Mon, 21 Sep 2020 09:57:40 +0200 "Kristof Provost" wrote: > On 21 Sep 2020, at 2:52, Shawn Webb wrote: > >> From latest HEAD on a Dell Precision 7550 laptop: > > > > https://gist.github.com/lattera/a0803f31f58bcf8ead51ac1ebbc447e2 > > > > The last working boot environment was 14 Aug 2020. If I get some time to > > bisect commits, I'll try to figure out the culprit. > > > Try https://reviews.freebsd.org/D26418 > > Best regards, > Kristof I'm not sure, but doesn't this panic have the same root as mine? Sorry, but I haven't text console and can post only screenshot[s] from IP-KVM https://gyazo.com/fee41c5267e9fc543d43901e498b7c94 rc.conf have something like: clonned_interfaces="lagg0 vlan101" ifconfig_lagg0="laggproto lacp laggport em0 laggport em1 x.x.x.x/mask" ifconfig_vlan101="vlan 101 vlandev lagg0 192.168.1.29/24" without VLAN part all works fine. Installed from FreeBSD-13.0-CURRENT-amd64-20200924-3c514403bef-disc1.iso -- wbr, Sergey ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
