On 09/06/11 00:14, Olivier Smedts wrote: > 2011/9/6 Olivier Smedts<olivier_at_gid0.org>: >> 2011/9/6 Volodymyr Kostyrko<c.kworr_at_gmail.com>: >>> 05.09.2011 10:43, Olivier Smedts wrote: >>> >>>>> ===> libexec/atrun (all) >>>>> clang -O2 -pipe -march=native -DATJOB_DIR=\"/var/at/jobs/\" >>>>> -DLFILE=\"/var/at/jobs/.lockfile\" -DLOADAVG_MX=1.5 >>>>> -DATSPOOL_DIR=\"/var/at/spool\" -DVERSION=\"2.9\" -DDAEMON_UID=1 >>>>> -DDAEMON_GID=1 -DDEFAULT_BATCH_QUEUE=\'E\' -DDEFAULT_AT_QUEUE=\'c\' >>>>> -DPERM_PATH=\"/var/at/\" -I/usr/src/libexec/atrun/../../usr.bin/at >>>>> -I/usr/src/libexec/atrun -DLOGIN_CAP -DPAM -std=gnu99 -fstack-protector >>>>> -Wsystem-headers -Wall -Wno-format-y2k -Wno-uninitialized >>>>> -Wno-pointer-sign >>>>> -c /usr/src/libexec/atrun/atrun.c >>>> Try removing "-march=native" from your CFLAGS. >>>> >>>> I have the exact same problem since months on my Core i7 CPU when >>>> using "-march=native" or "-march=corei7". No problems for me with >>>> "-march=core2" though. >>> It so nice you have noted that. I'll be much happier if you also spare some >>> time reading my previous emails. >> Or you could search this mailing list for the exact same problem >> reported some time ago. > Sorry for double-post. My point was : this does not seem to be a > buildworld problem, but rather a clang problem with coreiX's latest > instructions. Should be reported upstream IMO. > On my Dell Latitude E6510 notebook, equipted with one of the former Core-i5 "Lynnfield" CPUs, I got into a even worse situation. I can build the whole system with -march=native (buildworld), install it and at least run it. But then in multiuser mode, hitting the tab key, always ends up in a forced logout (it is with every shell, but only in multiuser mode, noct when starting the box in single user mode). Well, so far. Thought it was a fair chance, tried to revert what I've done and start compiling the OS again with either -march=core2 ore simply omit this. No chance! Shortly after start building world, I receive a weird error that cc1 failed compiling something, I need to make a report. When switching back to the legacy gcc 4.2, the same error occurs. The system isn't usable anymore. The OS is instable, hitting TAB key always ends up "logged out". I guess the only way to revert this is to install the box from scratch. I tried installing a base system from an installation DVD, it works so far. OliverReceived on Tue Sep 06 2011 - 05:13:18 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:17 UTC