search for: attampt

Erik de Castro Lopo wrote: > JonY wrote: > > > Please do a link time test instead, I am not getting this error and > > would like to keep stack protector on. > > I'll write an m4 macro. I have attampted to write a macro that reliably detects the availability of stack smash protection. I currently have two configurations where my detection says that SSP is available but the compile fails: - MinGW cross compile from Linux to Windows. - Native FreeBSD compile. Not sure what to do from here. I...

Hi, I am using the rpart package to build a classification tree. I did manage to build a tree with data on a previous project. However, when attampting to build a tree on a project I am working on, I seem to be getting the error shown below: > nhg3.rp <- rpart(profitresp ~., nhg3, method="class") > plot(nhg3.rp, branch=0.4, uniform=T); text(nhg3.rp, digits=3) Error in yval[, 1] : incorrect number of dimensions The distri...

...(uid=1001, gid=1001) (pid 1119) [2004/12/28 10:44:57, 1] smbd/service.c:close_cnum(836) sharedpc (192.168.2.133) closed connection to service Engi -- The closed came from logging off this machine -- Also, as of this morning, it stopped sending the username from windows automatically. When i attampt to login to my home directory, it prompts for a username and password. It did not do that before. $> testparm [global] workgroup = AZIMAOFFICE server string = adamwest log file = /var/log/log.%m max log size = 50 preferred master = Yes dom...

On 3/9/2013 06:20, Erik de Castro Lopo wrote: > bat guano wrote: > >> >> Hi >> I have a problem now cross-compiling FLAC from latest git. >> With Ubuntu 12.04 and g++-mingw-w64-i686 (4.6.3-1ubuntu5+5ubuntu1). >> >> I think that the problem might have been introduced on 5 Mar 2013 >> with commit 05609d5 (configure.ac : Add hardening compile options.)

...acd0: setting PIO4 on ROSB4 chip Apr 29 01:07:50 udns kernel: ata0: reinit done .. Apr 29 01:07:50 udns kernel: ad0: TIMEOUT - READ_DMA retrying (0 retries left) LBA=18520542 The board has a Serverworks/AMI BIOS (current flash). I'm running an 80 wire ribbon on a UDMA166 capable drive (first attampt on a 40Gig, second on a 13Gig). I can't imagine what would cause this. The kernel is GENERIC - as I won't be able to build world/kernel until I can resolve this. Is the kernel being too aggressive - eg; attempting to use the drive's capability when the BIOS only provides UDMA33? Anyway...