HEADS UP - HAMMER on-media format changed 12-May-2008
For those people testing HAMMER, the HAMMER on-media format has changed so you will have to newfs any HAMMER filesystems. I know I have said this before, but there's a very good chance that no more on-media changes will be made after this point. The official freeze of the on-media format will not occur until the 2.0 release, however. The testing of the reblocking and pruning code continues. There are still a handful of bugs related to parallel operations while reblocking and pruning which I expect to be worked out this week. -Matt
Re: problem with ELF
On Mon, May 12, 2008 at 07:37:32PM +0200, dark0s Optik wrote: > I've installed opera, but when I lanch it, console outputs Load linux emulation. Joerg
problem with ELF
I've installed opera, but when I lanch it, console outputs #opera ELF binary type "0" not known Abort # What is the problem? -- only the paranoid will survive
Re: problem with xorg
> (EE) : Cannot find wich device to use Maybe you gave the wrong pointer device. If you use moused in console, you can use /dev/sysmouse. Otherwise directly /dev/ums0 -- Robert Luciani Chalmers University of Technology, SWE Department of Computer Science and Engineering http://www.rluciani.com/[EMAIL PROTECTED]
Re: problem with xorg
I've installed the following packages: modular-xorg-drivers modular-xorg-libs modular-xorg-fonts modular-xorg-server modular-xorg-apps and xf86-input-void xf86-input-mouse xf86-input-keyboard but consola outputs: (EE) : Cannot find wich device to use (EE) xf86OpenSerial: No Device Specified (EE) : Cannot open input device (EE) PreInit failed cannot open input device "" No core pointer What is the problem? Thanks, savio 2008/5/10 Andre LeClaire <[EMAIL PROTECTED]>: > dark0s Optik wrote: > > > I didn't find a modular-xorg-package in > > > http://chlamydia.fs.ei.tum.de/pub/DragonFly/packages/DragonFly-1.12/stable/All/ > > > > > > You'll find it here: > > http://www.theshell.com/pub/DragonFly/packages/DragonFly-1.12/stable/All/ > -- only the paranoid will survive
Re: Linking with gcc runtime
[cc & reply-to kernel] Thomas E. Spanjaard wrote: > Hasso Tepper wrote: >> There are some software pieces out there which want to link with gcc >> runtime stuff (emacs and pcc are examples). But we have the >> interesting files in /usr/lib/gcc/. >> >> What I really don't want to do is to maintain patches which will break >> with every compiler upgrade: >> >> #if defined(__GNUC__) && __GNUC__ == 3 && __GNUC_MINOR__ == 4 >> #define GCC_LIB -L/usr/lib/gcc34 >> ... >> #elif defined(__GNUC__) && __GNUC__ == 4 && __GNUC_MINOR__ == 1 >> #define GCC_LIB -L/usr/lib/gcc41 >> ... >> >> Anyone has good ideas how to do it in better way? > > Introduce a varsym which uses CCVER (/usr/lib/gcc/ -> /usr/lib/$(CCVER))? We don't have varsyms enabled by default. I think we should investigate whether having crt files for every single compiler is the right thing to do. maybe not, maybe yes. I know that I introduced them, but I didn't anticipate that there would be other consumers than the compiler itself. Anyways, what is emacs doing with these files? I know that pcc just hijacks these crt files because it doesn't provide its own. I think it could also be parsed from a cc -v (or so) output. cheers simon signature.asc Description: OpenPGP digital signature
Re: Linking with gcc runtime
Hasso Tepper wrote: There are some software pieces out there which want to link with gcc runtime stuff (emacs and pcc are examples). But we have the interesting files in /usr/lib/gcc/. What I really don't want to do is to maintain patches which will break with every compiler upgrade: #if defined(__GNUC__) && __GNUC__ == 3 && __GNUC_MINOR__ == 4 #define GCC_LIB -L/usr/lib/gcc34 ... #elif defined(__GNUC__) && __GNUC__ == 4 && __GNUC_MINOR__ == 1 #define GCC_LIB -L/usr/lib/gcc41 ... Anyone has good ideas how to do it in better way? Introduce a varsym which uses CCVER (/usr/lib/gcc/ -> /usr/lib/$(CCVER))? -- Thomas E. Spanjaard [EMAIL PROTECTED] [EMAIL PROTECTED] signature.asc Description: OpenPGP digital signature
Linking with gcc runtime
There are some software pieces out there which want to link with gcc runtime stuff (emacs and pcc are examples). But we have the interesting files in /usr/lib/gcc/. What I really don't want to do is to maintain patches which will break with every compiler upgrade: #if defined(__GNUC__) && __GNUC__ == 3 && __GNUC_MINOR__ == 4 #define GCC_LIB -L/usr/lib/gcc34 ... #elif defined(__GNUC__) && __GNUC__ == 4 && __GNUC_MINOR__ == 1 #define GCC_LIB -L/usr/lib/gcc41 ... Anyone has good ideas how to do it in better way? -- Hasso Tepper
