Re: new gensetdefs breaks booting
Bruce Evans wrote: The new gensetdefs gives unbootable kernels on i386's. They hang before printing anything. I verified that the output of gensetdefs.pl is identical to that of gensetdefs(1). Does the kernel boot if gensetdefs(1) is used? -- Marcel Moolenaar mail: [EMAIL PROTECTED] / [EMAIL PROTECTED] tel: (408) 447-4222 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new gensetdefs breaks booting
Bruce Evans wrote: The new gensetdefs gives unbootable kernels on i386's. They hang before printing anything. I verified that the output of gensetdefs.pl is identical to that of gensetdefs(1). Does the kernel boot if gensetdefs(1) is used? Its not identical here, gensetdefs.pl uses .quad for the size of the linker set (?), which should be .long for x86. Also, I'm not sure if the calculation for pointer size is correct, all the numbers seemed 3 times too big in setdefs.h. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new gensetdefs breaks booting
Jake Burkholder wrote: Bruce Evans wrote: The new gensetdefs gives unbootable kernels on i386's. They hang before printing anything. I verified that the output of gensetdefs.pl is identical to that of gensetdefs(1). Does the kernel boot if gensetdefs(1) is used? Its not identical here, gensetdefs.pl uses .quad for the size of the linker set (?), which should be .long for x86. Also, I'm not sure if the calculation for pointer size is correct, all the numbers seemed 3 times too big in setdefs.h. Ok, thanks. The commit has been reverted for all platforms except ia64. I think I messed up my testing, but may easily have committed the wrong gensetdefs.pl. I'll check it out... -- Marcel Moolenaar mail: [EMAIL PROTECTED] / [EMAIL PROTECTED] tel: (408) 447-4222 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
