search for: 255th

This is probably a problem with having too many sections. There are a few places where mach-o has a limit on the number of sections. For instance the n_sect field of the nlist record is one byte. So any symbol in a section past the 255th section wraps around and shows up with the wrong n_sect number. -Nick On Apr 29, 2010, at 6:19 AM, Jack Howarth wrote: > I am wondering how the following issue was handled for > libLTO? We have a working patch to implement the FSF gcc > LTO on darwin which now passes all of the liblto...

...Thu, Apr 29, 2010 at 10:06:00PM -0700, Nick Kledzik wrote: > This is probably a problem with having too many sections. There are a few places where mach-o has a limit on the number of sections. For instance the n_sect field of the nlist record is one byte. So any symbol in a section past the 255th section wraps around and shows up with the wrong n_sect number. > > -Nick > > > On Apr 29, 2010, at 6:19 AM, Jack Howarth wrote: > > I am wondering how the following issue was handled for > > libLTO? We have a working patch to implement the FSF gcc > > LTO on d...

I am wondering how the following issue was handled for libLTO? We have a working patch to implement the FSF gcc LTO on darwin which now passes all of the liblto testsuite but are seeing linker issues with larger programs like aermod... as -arch x86_64 -force_cpusubtype_ALL -o aermod.o aermod.s /usr/bin/ld -dynamic -arch x86_64 -macosx_version_min 10.6.3 -weak_reference_mismatches

I am still having this weird problem with nodes hanging while I'm running OCFS. I'm using OCFS 1.0.9-12 and RHAS 2.1 I've been working on tracking it down and here's what I've got so far: 1. I create a file from node 0. This succeeds; I can /bin/cat the file, append, edit, or whatever. 2. From node 1, I do an operation that accesses the DirNode (e.g. /bin/ls) 3. Node 0

I am still having this weird problem with nodes hanging while I'm running OCFS. I'm using OCFS 1.0.9-12 and RHAS 2.1 I've been working on tracking it down and here's what I've got so far: 1. I create a file from node 0. This succeeds; I can /bin/cat the file, append, edit, or whatever. 2. From node 1, I do an operation that accesses the DirNode (e.g. /bin/ls) 3. Node 0

...se fdisk (or similar) so to "create a new empty DOS partition table". I'll try to clarify. One thing is the CHS *geometry*, e.g. Nx255x63. But since the first LBA is 0 (zero), the first C is 0 (zero) and the first H is 0 (zero), then, for instance, "cylinder 254" is the 255th cylinder and so on. I am assuming that the CHS values that you posted are not the "amount" (Nx255x63), but the "position" (or "name", if you want). So for a geometry of Nx255x63, 1st sector: CHS: 0 / 0 / 1 = LBA 0 2nd: CHS: 0 / 0 / 2 = LBA 1 61th: CHS: 0 / 0 / 61...

...sionally. o arima() with 'fixed' supplied and p=0 for the non-seasonal part could give spurious warnings about 'some AR parameters were fixed'. o summary.matrix() could give an infinite recursion on some classed objects (e.g. those of class "Surv"). o The 255th character in an 8-bit character set was not handled correctly as a letter on some platforms where C char is signed: for example it was printed as \377 and not allowed in variable names. (Spotted by Alexey Shipunov in Russian encodings.) o Conversion from POSIXct to POSIXlt is done more ac...

...sionally. o arima() with 'fixed' supplied and p=0 for the non-seasonal part could give spurious warnings about 'some AR parameters were fixed'. o summary.matrix() could give an infinite recursion on some classed objects (e.g. those of class "Surv"). o The 255th character in an 8-bit character set was not handled correctly as a letter on some platforms where C char is signed: for example it was printed as \377 and not allowed in variable names. (Spotted by Alexey Shipunov in Russian encodings.) o Conversion from POSIXct to POSIXlt is done more ac...

As I said before, booting is bigger than one bootloader. I am replying to what I think was asked. I might have misunderstood the questions. Whichever the case, this email is less about Syslinux itself. If this is considered too far off-topic in the Syslinux Mailing List, please receive my apologies. > > I still have the factory-set contents of my three USB sticks. A small