Re: Changement de runlevel
Le Sunday 5 February 2006 14:39, Cyril Brulebois a écrit : Laurent [EMAIL PROTECTED] (05/02/2006): Bonjour, Bonjour, Je cherche un moyen de savoir a quel runlevel était le système avantle dernier boot. Le but est de savoir si c'est un reboot ou si c'est un boot après un arrêt de la machine. dans /var/log/syslog*, on trouve ce genre de choses : (date) localhost shutdown[13562]: shutting down for system reboot (date) localhost init: Switching to runlevel: 6 Je pense que, pour ce genre de questions, les listes de diffusion « utilisateurs » suffisent, par exemple debian-user-french. Cordialement, La commande runlevel fournit ce type d'info. Cordialement, Yann -- http://www.non-violence.org/ | Site collaboratif sur la non-violence http://www.forget-me.net/ | Alternatives sur le Net http://fr.wikipedia.org/ | Encyclopédie libre -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Cross compileur pour AMD64
Bonjour, J'ai posté la réponse sur d-u-fr, et je n'ai pas eu de réponse. Et cela concerne le développement. J'espère n'être pas trop HS. J'essaie de construire un cross compileur pour AMD64 (Opteron 242) avec gcc-3.3.3 et gcc-3.4.0. Je suis sur Debian unstable : $ gcc -v Reading specs from /usr/lib/gcc-lib/i486-linux/3.3.3/specs Configured with: ../src/configure -v --enable-languages=c,c++,java,f77,pascal,objc,ada,treelang --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-gxx-include-dir=/usr/include/c++/3.3 --enable-shared --with-system-zlib --enable-nls --without-included-gettext --enable-__cxa_atexit --enable-clocale=gnu --enable-debug --enable-java-gc=boehm --enable-java-awt=xlib --enable-objc-gc i486-linux Thread model: posix gcc version 3.3.3 (Debian 20040401) $ uname -a Linux hal 2.4.23-amd64 #1 Sat Nov 29 12:52:06 EST 2003 x86_64 GNU/Linux J'ai compilé avec succès binutils pour AMD64 avec ./configure --target=x86_64-unknown-linux --prefix=/opt/x86-64 Pour gcc, j'utilise PATH=/opt/x86-64/bin:$PATH CFLAGS=-O2 -Dinhibit_libc ./configure --target=x86_64-unknown-linux --prefix=/opt/x86-64 \ --enable-languages=c \ --disable-shared --disable-multilib --enable-threads=single J'obtiens pour gcc-3.3.3 et gcc-3.40 respectivement : /home/yann/src/gcc/gcc-3.3.3/gcc/xgcc -B/home/yann/src/gcc/gcc-3.3.3/gcc/ -B/opt/x86-64/x86_64-unknown-linux/bin/ -B/opt/x86-64/x86_64-unknown-linux/lib/ -isystem /opt/x86-64/x86_64-unknown-linux/include -O2 -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -isystem ./include -fPIC -g -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -I. -I. -I. -I./. -I./config -I./../include -fexceptions -c ./unwind-dw2.c -o libgcc/./unwind-dw2.o unwind-dw2.c: In function `uw_frame_state_for': unwind-dw2.c:942: error: structure has no member named `rsp' unwind-dw2.c:942: error: structure has no member named `rax' unwind-dw2.c:942: error: structure has no member named `rdx' unwind-dw2.c:942: error: structure has no member named `rcx' unwind-dw2.c:942: error: structure has no member named `rbx' unwind-dw2.c:942: error: structure has no member named `rsi' unwind-dw2.c:942: error: structure has no member named `rdi' unwind-dw2.c:942: error: structure has no member named `rbp' unwind-dw2.c:942: error: structure has no member named `r8' unwind-dw2.c:942: error: structure has no member named `r9' unwind-dw2.c:942: error: structure has no member named `r10' unwind-dw2.c:942: error: structure has no member named `r11' unwind-dw2.c:942: error: structure has no member named `r12' unwind-dw2.c:942: error: structure has no member named `r13' unwind-dw2.c:942: error: structure has no member named `r14' unwind-dw2.c:942: error: structure has no member named `r15' unwind-dw2.c:942: error: structure has no member named `rip' make[2]: *** [libgcc/./unwind-dw2.o] Error 1 make[2]: Leaving directory `/usr/local/src/gcc/gcc-3.3.3/gcc' make[1]: *** [stmp-multilib] Error 2 make[1]: Leaving directory `/usr/local/src/gcc/gcc-3.3.3/gcc' make: *** [all-gcc] Error 2 /home/yann/src/gcc/gcc-3.4.0/gcc/xgcc -B/home/yann/src/gcc/gcc-3.4.0/gcc/ -B/opt/x86-64/x86_64-unknown-linux/bin/ -B/opt/x86-64/x86_64-unknown-linux/lib/ -isystem /opt/x86-64/x86_64-unknown-linux/include -isystem /opt/x86-64/x86_64-unknown-linux/sys-include -O2 -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -isystem ./include -fPIC -g -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -I. -I. -I. -I./. -I./../include -fexceptions -c ./unwind-dw2.c -o libgcc/./unwind-dw2.o ./unwind-dw2.c: In function `uw_frame_state_for': ./unwind-dw2.c:1022: error: structure has no member named `rsp' ./unwind-dw2.c:1022: error: structure has no member named `rax' ./unwind-dw2.c:1022: error: structure has no member named `rdx' ./unwind-dw2.c:1022: error: structure has no member named `rcx' ./unwind-dw2.c:1022: error: structure has no member named `rbx' ./unwind-dw2.c:1022: error: structure has no member named `rsi' ./unwind-dw2.c:1022: error: structure has no member named `rdi' ./unwind-dw2.c:1022: error: structure has no member named `rbp' ./unwind-dw2.c:1022: error: structure has no member named `r8' ./unwind-dw2.c:1022: error: structure has no member named `r9' ./unwind-dw2.c:1022: error: structure has no member named `r10' ./unwind-dw2.c:1022: error: structure has no member named `r11' ./unwind-dw2.c:1022: error: structure has no member named `r12' ./unwind-dw2.c:1022: error: structure has no member named `r13' ./unwind-dw2.c:1022: error: structure has no member named `r14' ./unwind-dw2.c:1022: error: structure has no member named `r15' ./unwind-dw2.c:1022: error: structure has no member named `rip' make[2]: *** [libgcc/./unwind-dw2.o] Error 1 make[2]: Leaving directory `/usr/local/src/gcc/gcc-3.4.0/gcc' make[1]: *** [stmp-multilib] Error 2 make[1]: Leaving directory `/usr/local/src/gcc/gcc-3.4.0/gcc' make: *** [all-gcc] Error 2 Qu'est-ce que
Questions sur les Rapports de Bugs
Bonjour, J'ai plusieurs questions concernant le rapport de bugs avec BTS : 1. Comment clore un bug que j'ai soumis maintenant que ça fonctionne correctement après une MAJ ? 2. En fait, le problème (Konqueror + Java) n'a pas complètement disparu. Ça ne fonctionnait pas du tout, maintenant, ça fonctionne partiellement. Faut-il clore le bug et en soumettre un nouveau, ou modifier le rapport de bug existant ? 3. Pas de rapport sur le bug 38734 que j'ai soumis : http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=38734 An error occurred. Dammit. Error was: Couldn't get bug status: No such file or directory. Pourtant, j'ai reçu un rapport par mail. Une explication ? 4. Pour un bug que j'ai soumis, le mainteneur m'a répondu retitle 131886 RFP: klendar - A calendar tool for KDE. Que faut-il faire pour renommer ce bug ? Si je ne suis pas sur la bonne liste, merci de me dire (gentiment ;o)) où je dois m'adresser. Merci, Yann -- Chef de projet Linux / Linux project manager Juillerat-Grin SA http://www.codalis.ch
