ChanServ changed the topic of #armlinux to: ARM kernel talk [Upstream kernel, find your vendor forums for questions about their kernels] | https://libera.irclog.whitequark.org/armlinux
apritzel has quit [Ping timeout: 260 seconds]
elastic_dog has quit [Ping timeout: 245 seconds]
elastic_dog has joined #armlinux
matthias_bgg has quit [Ping timeout: 252 seconds]
matthias_bgg has joined #armlinux
jn has quit [Ping timeout: 268 seconds]
jclsn has quit [Ping timeout: 256 seconds]
jclsn has joined #armlinux
hays has quit [Remote host closed the connection]
heat has joined #armlinux
hays has joined #armlinux
hays has quit [Client Quit]
hays has joined #armlinux
heat has quit [Ping timeout: 256 seconds]
amitk has joined #armlinux
cbeznea has joined #armlinux
luispm has joined #armlinux
sakman_ has joined #armlinux
sakman has quit [Ping timeout: 240 seconds]
dhruvag2000 has joined #armlinux
dhruvag2000 has quit [Changing host]
dhruvag2000 has joined #armlinux
mvaittin has joined #armlinux
sakman_ is now known as sakman
monstr has joined #armlinux
gclement has joined #armlinux
frieder has joined #armlinux
apritzel has joined #armlinux
frieder has quit [Ping timeout: 268 seconds]
apritzel has quit [Ping timeout: 252 seconds]
frieder has joined #armlinux
prabhakarlad has quit [Quit: Client closed]
headless has joined #armlinux
mripard has joined #armlinux
dliviu has joined #armlinux
mag_ has joined #armlinux
mag has quit [Ping timeout: 255 seconds]
heat has joined #armlinux
prabhakar has quit [Ping timeout: 256 seconds]
bjoto has quit [Quit: WeeChat 4.0.5]
iivanov has joined #armlinux
sszy has joined #armlinux
headless has quit [Quit: Konversation terminated!]
apritzel has joined #armlinux
alpernebbi has quit [Ping timeout: 255 seconds]
rgallaispou has joined #armlinux
alpernebbi has joined #armlinux
prabhakar has joined #armlinux
prabhakarlad has joined #armlinux
sudeepholla_ has quit [Read error: Connection reset by peer]
sudeepholla_ has joined #armlinux
bjoto has joined #armlinux
jn_ has joined #armlinux
jn_ has joined #armlinux
krzk has quit [Ping timeout: 260 seconds]
sally has joined #armlinux
nsaenz has joined #armlinux
psydroid has joined #armlinux
nsaenz has quit [Remote host closed the connection]
matthias_bgg has quit [Ping timeout: 246 seconds]
krzk has joined #armlinux
iivanov has quit [Ping timeout: 268 seconds]
rvalue has quit [Read error: Connection reset by peer]
rvalue has joined #armlinux
alpernebbi has quit [Quit: No Ping reply in 180 seconds.]
alpernebbi has joined #armlinux
robmur01 has quit [Ping timeout: 245 seconds]
iivanov has joined #armlinux
mripard has quit [Remote host closed the connection]
hanetzer1 has joined #armlinux
hanetzer has quit [Killed (NickServ (GHOST command used by hanetzer1))]
hanetzer1 is now known as hanetzer
robmur01 has joined #armlinux
prabhakarlad has quit [Ping timeout: 250 seconds]
prabhakar has quit [Ping timeout: 268 seconds]
mripard has joined #armlinux
headless has joined #armlinux
rgallaispou has quit [K-Lined]
gclement has quit [Ping timeout: 252 seconds]
heat has quit [Read error: Connection reset by peer]
heat has joined #armlinux
krzk has quit [Quit: leaving]
krzk has joined #armlinux
amitk_ has joined #armlinux
sakman has quit [Ping timeout: 264 seconds]
monstr has quit [Remote host closed the connection]
<ardb>
nathanchance: so this is simply a matter of building the compat vdso for armv7
<nathanchance>
ardb: Somewhat, ARCH=arm is affected as well, in an even worse manner
<ardb>
how so?
<nathanchance>
‘—target=arm-linux-gnueabi -march=armv7-a’ will result in ‘-triple armv5e-unknown-linux-gnueabi'
<ardb>
ok so that is just plain broken for anything built with that compiler, right?
<nathanchance>
Right
<ardb>
for the arm64 case, i would argue that the missing target is something that we should fix anyway
<nathanchance>
They are basically hardcoding arm-linux-gnueabi to mean their “armel” which is an armv5 baseline and arm-linux-gnueabihf to mean “armed” which is armv7
<nathanchance>
We have a target for the arm64 case
<ardb>
so why does it complain about needing v6? is that also a debian llvm bug?
<nathanchance>
No, it’s the consequence of that change