Re: emulators/qemu-user-static linker error on 13-CURRENT r358890
On 12 Mar 2020, at 15:35, Warner Losh wrote: > > On Thu, Mar 12, 2020 at 8:24 AM Glen Barber wrote: >> 13-CURRENT aarch64 GENERIC builds failed this week due to the dependent >> port emulators/qemu-user-static failing to build, which is used by the >> targets that create the cloud provider images (EC2, GCE, etc.). >> >> The error output from the port build is: >> >> ===> Configuring for qemu-user-static-2.11.50.g20191211_3 >> >> ERROR: We need to link the QEMU user mode binaries at a >> specific text address. Unfortunately your linker >> doesn't support either the -Ttext-segment option or >> printing the default linker script with --verbose. >> If you don't want the user mode binaries, pass the >> --disable-user option to configure. >> >> The machine was upgraded yesterday from r356986 to r358890, and there >> does not seem to be any relevant change to the port. >> >> Any ideas? > > Force it to use ld.bfd? This may be lld fallout. Indeed it is due to lld 10.0.0. For the emulators/qemu-sbruno port, which is the master for the qemu-user-static port, I have submitted a fix in https://bugs.freebsd.org/244772. Fixes for other qemu ports: https://bugs.freebsd.org/244768 (qemu-cheri) https://bugs.freebsd.org/244769 (qemu-devel) https://bugs.freebsd.org/244770 (qemu) https://bugs.freebsd.org/244771 (qemu-powernv) https://bugs.freebsd.org/244773 (qemu30) https://bugs.freebsd.org/244774 (qemu31) https://bugs.freebsd.org/244775 (qemu40) And while typing this, I see there is yet *another* qemu port, namely qemu-user-static-devel. -Dimitry P.S.: WTF do we have so many qemu ports? :) signature.asc Description: Message signed with OpenPGP
Re: New Xorg - different key-codes
On Thu, Mar 12, 2020 at 04:53:32PM +0100, Michael Gmelin wrote: > > > On Thu, 12 Mar 2020 10:36:42 -0500 > Bob Willcox wrote: > > > On Thu, Mar 12, 2020 at 07:24:42AM -0500, Bob Willcox wrote: > > > On Wed, Mar 11, 2020 at 11:46:49PM +0100, Michael Gmelin wrote: > > > > > > > > > > > > SNIP SNAP > > > > >> It might fix the ???Down key opens application launcher??? > > > > >> problem by applying the correct keymap (you have to select the > > > > >> correct one, ???de??? probably won???t cut it for you). At > > > > >> least it did with xfce, where it was important to run it > > > > >> before the wm starts - you could also try running it > > > > >> afterwards to see if it makes a difference. > > > > > > > > > > I don't know about that problem. What I'm experiencing is the > > > > > Alt-up,down,left,right keys don't work as they used to in my > > > > > ctwm window manager. They used to move the current window to > > > > > the closest boundry in the direction indicated by the key that > > > > > is also pressed (while holding the Alt key down). Also, > > > > > Alt-shift-up,down,left,right would expand the window in the > > > > > direction indicated by the key. These actions seem to do > > > > > nothing now. > > > > > > > > I don???t know much about ctwm, but why don???t you give it a > > > > shot? > > > > > > I plan to sometime today when I get into the office. But since it's > > > my work system and I am dependent on it to do my job, I've just > > > been a little hesitant. > > > > Ok, I added this to my ~/.xinitrc file: > > > > setxkbmap -model pc105 -layout us > > > > and my ctwm window adjustment hot keys are working again. :) > > > > I do wonder why it was deemed ok to change the default behavior for > > the key mappings? Couldn't the default mappings have remained the > > same with change to evdev? This change certainly violated the > > "principle of least surprise" for me. > > > > > > I think the change was unavoidable, but it could've been communicated > better. Then again, time and resources are limited and I'm quite > grateful the graphics team finally made that necessary push forward. > > I'm curious how people set their keyboard layout in the past though, > is it possible that the defaults just worked for US users? I always had > to set it explicitly (setxkbmap or in Xorg.conf), so I was never really > affected by this change. > > -m > > p.s. What does "setxkbmap -query" show if you start X without setting > the keymap in .xinitrc? I'll have to try that when I get home tonight on one of my other systems as I really can't afford to take the time to restart X on this system now...got to get some work done. :) Bob > > -- > Michael Gmelin -- Bob Willcox| It's possible that the whole purpose of your life is to b...@immure.com | serve as a warning to others. Austin, TX | ___ 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: New Xorg - different key-codes
On Thu, 12 Mar 2020 10:36:42 -0500 Bob Willcox wrote: > On Thu, Mar 12, 2020 at 07:24:42AM -0500, Bob Willcox wrote: > > On Wed, Mar 11, 2020 at 11:46:49PM +0100, Michael Gmelin wrote: > > > > > > > > > SNIP SNAP > > > >> It might fix the ???Down key opens application launcher??? > > > >> problem by applying the correct keymap (you have to select the > > > >> correct one, ???de??? probably won???t cut it for you). At > > > >> least it did with xfce, where it was important to run it > > > >> before the wm starts - you could also try running it > > > >> afterwards to see if it makes a difference. > > > > > > > > I don't know about that problem. What I'm experiencing is the > > > > Alt-up,down,left,right keys don't work as they used to in my > > > > ctwm window manager. They used to move the current window to > > > > the closest boundry in the direction indicated by the key that > > > > is also pressed (while holding the Alt key down). Also, > > > > Alt-shift-up,down,left,right would expand the window in the > > > > direction indicated by the key. These actions seem to do > > > > nothing now. > > > > > > I don???t know much about ctwm, but why don???t you give it a > > > shot? > > > > I plan to sometime today when I get into the office. But since it's > > my work system and I am dependent on it to do my job, I've just > > been a little hesitant. > > Ok, I added this to my ~/.xinitrc file: > > setxkbmap -model pc105 -layout us > > and my ctwm window adjustment hot keys are working again. :) > > I do wonder why it was deemed ok to change the default behavior for > the key mappings? Couldn't the default mappings have remained the > same with change to evdev? This change certainly violated the > "principle of least surprise" for me. > > I think the change was unavoidable, but it could've been communicated better. Then again, time and resources are limited and I'm quite grateful the graphics team finally made that necessary push forward. I'm curious how people set their keyboard layout in the past though, is it possible that the defaults just worked for US users? I always had to set it explicitly (setxkbmap or in Xorg.conf), so I was never really affected by this change. -m p.s. What does "setxkbmap -query" show if you start X without setting the keymap in .xinitrc? -- Michael Gmelin ___ 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: New Xorg - different key-codes
On Thu, Mar 12, 2020 at 07:24:42AM -0500, Bob Willcox wrote: > On Wed, Mar 11, 2020 at 11:46:49PM +0100, Michael Gmelin wrote: > > > > > > > On 11. Mar 2020, at 23:25, Bob Willcox wrote: > > > > > > ???On Wed, Mar 11, 2020 at 11:04:18PM +0100, Michael Gmelin wrote: > > >> > > >> > > On 11. Mar 2020, at 22:58, Bob Willcox wrote: > > >>> > > >>> ???On Wed, Mar 11, 2020 at 02:48:56PM +0100, Michael Gmelin wrote: > > ??? > > >> On 11. Mar 2020, at 10:29, Mark Martinec > > >> wrote: > > > ??? > > >> > > >>> I just updated my laptop from source, and somewhere along the way > > >>> the key-codes Xorg sees changed. > > >> Indeed. This doesn't just affect -CURRENT: it happened to me on > > >> -STABLE last week, so I'm copying that list too. > > > > > > And a "Down" key now opens and closes a KDE "Application Launcher", > > > alternatively with its original function (which makes editing a > > > frustration). > > > > > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244354 > > > > > > > > > > This *might* help you: > > > > https://lists.freebsd.org/pipermail/freebsd-x11/2020-February/025046.html > > > > (Short version: run setxkbmap in ~/.xinitrc, e.g., > > setxkbmap -model pc105 -layout de) > > >>> > > >>> Will running that command return my key mappings back to what they use > > >>> to be? > > >>> > > >> > > >> It might fix the ???Down key opens application launcher??? problem by > > >> applying the correct keymap (you have to select the correct one, > > >> ???de??? probably won???t cut it for you). At least it did with xfce, > > >> where it was important to run it before the wm starts - you could also > > >> try running it afterwards to see if it makes a difference. > > > > > > I don't know about that problem. What I'm experiencing is the > > > Alt-up,down,left,right keys > > > don't work as they used to in my ctwm window manager. They used to move > > > the current window > > > to the closest boundry in the direction indicated by the key that is also > > > pressed (while > > > holding the Alt key down). Also, Alt-shift-up,down,left,right would > > > expand the window in > > > the direction indicated by the key. These actions seem to do nothing now. > > > > > > > I don???t know much about ctwm, but why don???t you give it a shot? > > I plan to sometime today when I get into the office. But since it's my work > system and I > am dependent on it to do my job, I've just been a little hesitant. Ok, I added this to my ~/.xinitrc file: setxkbmap -model pc105 -layout us and my ctwm window adjustment hot keys are working again. :) I do wonder why it was deemed ok to change the default behavior for the key mappings? Couldn't the default mappings have remained the same with change to evdev? This change certainly violated the "principle of least surprise" for me. > > Bob > > -- > Bob Willcox| It's possible that the whole purpose of your life is to > b...@immure.com | serve as a warning to others. > Austin, TX | -- Bob Willcox| It's possible that the whole purpose of your life is to b...@immure.com | serve as a warning to others. Austin, TX | ___ 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: emulators/qemu-user-static linker error on 13-CURRENT r358890
On Thu, Mar 12, 2020 at 8:24 AM Glen Barber wrote: > 13-CURRENT aarch64 GENERIC builds failed this week due to the dependent > port emulators/qemu-user-static failing to build, which is used by the > targets that create the cloud provider images (EC2, GCE, etc.). > > The error output from the port build is: > > ===> Configuring for qemu-user-static-2.11.50.g20191211_3 > > ERROR: We need to link the QEMU user mode binaries at a >specific text address. Unfortunately your linker >doesn't support either the -Ttext-segment option or >printing the default linker script with --verbose. >If you don't want the user mode binaries, pass the >--disable-user option to configure. > > The machine was upgraded yesterday from r356986 to r358890, and there > does not seem to be any relevant change to the port. > > Any ideas? > Force it to use ld.bfd? This may be lld fallout. Warner ___ 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"
emulators/qemu-user-static linker error on 13-CURRENT r358890
13-CURRENT aarch64 GENERIC builds failed this week due to the dependent port emulators/qemu-user-static failing to build, which is used by the targets that create the cloud provider images (EC2, GCE, etc.). The error output from the port build is: ===> Configuring for qemu-user-static-2.11.50.g20191211_3 ERROR: We need to link the QEMU user mode binaries at a specific text address. Unfortunately your linker doesn't support either the -Ttext-segment option or printing the default linker script with --verbose. If you don't want the user mode binaries, pass the --disable-user option to configure. The machine was upgraded yesterday from r356986 to r358890, and there does not seem to be any relevant change to the port. Any ideas? Glen signature.asc Description: PGP signature
Re: New Xorg - different key-codes
On Wed, Mar 11, 2020 at 11:46:49PM +0100, Michael Gmelin wrote: > > > > On 11. Mar 2020, at 23:25, Bob Willcox wrote: > > > > ???On Wed, Mar 11, 2020 at 11:04:18PM +0100, Michael Gmelin wrote: > >> > >> > On 11. Mar 2020, at 22:58, Bob Willcox wrote: > >>> > >>> ???On Wed, Mar 11, 2020 at 02:48:56PM +0100, Michael Gmelin wrote: > ??? > >> On 11. Mar 2020, at 10:29, Mark Martinec > >> wrote: > > ??? > >> > >>> I just updated my laptop from source, and somewhere along the way > >>> the key-codes Xorg sees changed. > >> Indeed. This doesn't just affect -CURRENT: it happened to me on > >> -STABLE last week, so I'm copying that list too. > > > > And a "Down" key now opens and closes a KDE "Application Launcher", > > alternatively with its original function (which makes editing a > > frustration). > > > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244354 > > > > > > This *might* help you: > > https://lists.freebsd.org/pipermail/freebsd-x11/2020-February/025046.html > > (Short version: run setxkbmap in ~/.xinitrc, e.g., > setxkbmap -model pc105 -layout de) > >>> > >>> Will running that command return my key mappings back to what they use to > >>> be? > >>> > >> > >> It might fix the ???Down key opens application launcher??? problem by > >> applying the correct keymap (you have to select the correct one, ???de??? > >> probably won???t cut it for you). At least it did with xfce, where it was > >> important to run it before the wm starts - you could also try running it > >> afterwards to see if it makes a difference. > > > > I don't know about that problem. What I'm experiencing is the > > Alt-up,down,left,right keys > > don't work as they used to in my ctwm window manager. They used to move the > > current window > > to the closest boundry in the direction indicated by the key that is also > > pressed (while > > holding the Alt key down). Also, Alt-shift-up,down,left,right would expand > > the window in > > the direction indicated by the key. These actions seem to do nothing now. > > > > I don???t know much about ctwm, but why don???t you give it a shot? I plan to sometime today when I get into the office. But since it's my work system and I am dependent on it to do my job, I've just been a little hesitant. Bob -- Bob Willcox| It's possible that the whole purpose of your life is to b...@immure.com | serve as a warning to others. Austin, TX | ___ 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: llvm 10 libomp build error
On 12 Mar 2020, at 11:38, Kristof Provost wrote: > > On 12 Mar 2020, at 16:58, Ronald Klop wrote: ... >> cc: error: no such file or directory: >> '/data/src/freebsd-current/contrib/llvm-pr >> oject/openmp/runtime/src/thirdparty/ittnotify/ittnotify_static.c' >> cc: error: no input files >> *** [ittnotify_static.pico] Error code 1 ... > Try removing /usr/obj/* (or whatever your object directory is) and rebuilding. > That worked for me. This has now been worked around in r358907. -Dimitry signature.asc Description: Message signed with OpenPGP
Re: llvm 10 libomp build error
On 12 Mar 2020, at 16:58, Ronald Klop wrote: Hi, Clean build after svn update gives: cc: error: no such file or directory: '/data/src/freebsd-current/contrib/llvm-pr oject/openmp/runtime/src/thirdparty/ittnotify/ittnotify_static.c' cc: error: no input files *** [ittnotify_static.pico] Error code 1 make[5]: stopped in /data/src/freebsd-current/lib/libomp The file ittnotify_static.c does indeed not exist. A .cpp version does exist. [builder@sjakie ~]$ more /etc/src.conf KERNCONF?=GENERIC-NODEBUG # Don't build these WITHOUT_LLVM_TARGET_ALL=true WITHOUT_LPR=true WITHOUT_PROFILE=true WITHOUT_SENDMAIL=true WITHOUT_TESTS=true What is the advice? Currently rebuilding with -j 1, but that will hours for building the new clang again. Try removing /usr/obj/* (or whatever your object directory is) and rebuilding. That worked for me. Best, Kristof ___ 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: llvm 10 libomp build error
On Thu, Mar 12, 2020 at 09:13:38AM +, Filippo Moretti wrote: > Same problem yesterdayFilippo > > On Thursday, March 12, 2020, 08:59:17 AM GMT+1, Ronald Klop > wrote: > > Hi, > > Clean build after svn update gives: > > cc: error: no such file or directory: > '/data/src/freebsd-current/contrib/llvm-pr > oject/openmp/runtime/src/thirdparty/ittnotify/ittnotify_static.c' > cc: error: no input files > *** [ittnotify_static.pico] Error code 1 > I had no issues, updating from r358830 to r358872. Peace, david -- David H. Wolfskill da...@catwhisker.org "Trump has signaled that even in matters of life and death, he is either incapable or unwilling to lead." -- Samantha Vinograd See http://www.catwhisker.org/~david/publickey.gpg for my public key. signature.asc Description: PGP signature
Re: New Xorg - different key-codes
On Thu, 12 Mar 2020 10:31:40 +0100 Alexander Leidinger wrote: > Hi, > > This command sets the keyboard layout. You are supposed to set the > keyboard layout which matches the physical layout of the hardware. > This hadn't changed, it's a fundamental part of X11 since I know it > (X11 6.5) and even before... > [snip] Exactly. I just personally prefer to use setxkbmap, as all my setups are single user (one unprivileged user per machine that runs X, no shared machines) and customization happens in $HOME that way. Makes it a bit easier to setup a new machine (no digging in Xorg configs) and reading ~/.xinitrc basically tells me all about my current config. Plus, setxkbmap makes it easy to experiment, as it's applies changes while X is running, even if one makes the those changes permanently in an xorg config file later. And the resulting command is just one line (in my case as short as "setxkbmap -model pc105 -layout de"), makes it easier to support people. Another useful application of the command is for debugging: "setxkbmap -query" will tell you what's currently configured (regardless how that configuration was done), e.g., On a machine running xorg 1.18: # setxkbmap -query rules: base model: pc105 layout: de On a machine running xorg 1.20: rules: evdev model: pc105 layout: de In both cases the same setxkbmap command was used in ~/.xinitrc to set model and layout. Rules were taken from Xorg's default config, which changed to evdev in 1.20. Cheers, Michael -- Michael Gmelin ___ 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: New Xorg - different key-codes
Hi,
This command sets the keyboard layout. You are supposed to set the keyboard
layout which matches the physical layout of the hardware. This hadn't
changed, it's a fundamental part of X11 since I know it (X11 6.5) and even
before...
For those which had an explicit setting in xorg.conf (like me) but switched
now to nothing or the "match" snippets for mouse or kbd: you can specify
this already in the config. Here is what I use:
---snip---
Donnerstag, 12. März 2020, 10:21:40
{1} [video:/]
(201) root@ttypts/1 # cat /usr/local/etc/X11/xorg.conf.d/kbd.conf Section
"InputClass"
Identifier "Keyboard0"
MatchIsKeyboard "on"
MatchDevicePath "/dev/input/event*"
Driver "libinput"
Option "XkbModel" "pc105"
Option "XkbLayout" "de"
Option "XkbRules" "evdev"
EndSection
Donnerstag, 12. März 2020, 10:22:05
{0} [video:/]
(202) root@ttypts/1 # cat /usr/local/etc/X11/xorg.conf.d/mouse.conf
Section "InputClass"
Identifier "Mouse0"
MatchIsPointer "on"
MatchDevicePath "/dev/input/event*"
Driver "libinput"
# Option "Protocol" "auto"
# Option "Device" "/dev/sysmouse"
Option "ZAxisMapping" "4 5 6 7"
EndSection
---snip---
Note, I use this in sysctl.conf:
---snip---
# enable hardware devices in evdev
kern.evdev.rcpt_mask=12
---snip---
When I did that, I just validated that I was able to login to KDE (the
particular X11 is feeding a home-cinema setup and is not used often, I just
decided to update it as long as I remembered there was a change to xorg
with a config impact). I didn't check any up/down/umlauts, I just plain
assumed it works (and I still assume it does). The above is just meant to
provide some info how to make it work globally instead of having a setting
in each local startup per user.
Bye,
Alexander.
--
Send from a mobile device, please forgive brevity and misspellings.
Am 11. März 2020 23:07:55 schrieb Bob Willcox :
On Wed, Mar 11, 2020 at 02:48:56PM +0100, Michael Gmelin wrote:
???
>> On 11. Mar 2020, at 10:29, Mark Martinec
>> wrote:
> ???
>>
>>> I just updated my laptop from source, and somewhere along the way
>>> the key-codes Xorg sees changed.
>> Indeed. This doesn't just affect -CURRENT: it happened to me on
>> -STABLE last week, so I'm copying that list too.
>
> And a "Down" key now opens and closes a KDE "Application Launcher",
> alternatively with its original function (which makes editing a
> frustration).
>
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244354
>
>
This *might* help you:
https://lists.freebsd.org/pipermail/freebsd-x11/2020-February/025046.html
(Short version: run setxkbmap in ~/.xinitrc, e.g.,
setxkbmap -model pc105 -layout de)
Will running that command return my key mappings back to what they use to be?
--
Bob Willcox| It's possible that the whole purpose of your life is to
b...@immure.com | serve as a warning to others.
Austin, TX |
___
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"
___
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: llvm 10 libomp build error
Same problem yesterdayFilippo On Thursday, March 12, 2020, 08:59:17 AM GMT+1, Ronald Klop wrote: Hi, Clean build after svn update gives: cc: error: no such file or directory: '/data/src/freebsd-current/contrib/llvm-pr oject/openmp/runtime/src/thirdparty/ittnotify/ittnotify_static.c' cc: error: no input files *** [ittnotify_static.pico] Error code 1 make[5]: stopped in /data/src/freebsd-current/lib/libomp The file ittnotify_static.c does indeed not exist. A .cpp version does exist. [builder@sjakie ~]$ more /etc/src.conf KERNCONF?=GENERIC-NODEBUG # Don't build these WITHOUT_LLVM_TARGET_ALL=true WITHOUT_LPR=true WITHOUT_PROFILE=true WITHOUT_SENDMAIL=true WITHOUT_TESTS=true What is the advice? Currently rebuilding with -j 1, but that will hours for building the new clang again. Ronald. ___ 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" ___ 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"
llvm 10 libomp build error
Hi, Clean build after svn update gives: cc: error: no such file or directory: '/data/src/freebsd-current/contrib/llvm-pr oject/openmp/runtime/src/thirdparty/ittnotify/ittnotify_static.c' cc: error: no input files *** [ittnotify_static.pico] Error code 1 make[5]: stopped in /data/src/freebsd-current/lib/libomp The file ittnotify_static.c does indeed not exist. A .cpp version does exist. [builder@sjakie ~]$ more /etc/src.conf KERNCONF?=GENERIC-NODEBUG # Don't build these WITHOUT_LLVM_TARGET_ALL=true WITHOUT_LPR=true WITHOUT_PROFILE=true WITHOUT_SENDMAIL=true WITHOUT_TESTS=true What is the advice? Currently rebuilding with -j 1, but that will hours for building the new clang again. Ronald. ___ 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"
