A quick update
Quoted 4 lines
The -N places the $DATA$ section after
the $CODE$ section in low memory. The +n option that was being used in theMakefilehas the $DATA$ section in the0x40000000quadrant. This is wrong for the kernel.
The opposite of -N is -n, not +n. The +n option tells the linker to search archive libraries iteratively, which I believe is needed for the Linux kernel.
The -N option tells the linker to build a "non-shareable" executable, so it puts text and data together in one segment. The -n option is the default, where shareable text is placed in the first quadrant and data is placed in the second quadrant.
Cary Coutant
Hewlett-Packard Co.
Application Delivery Lab
Quoted 9 lines
Quoted 5 lines
The -N places the $DATA$ section after
the $CODE$ section in low memory. The +n option that was being used in theMakefilehas the $DATA$ section in the0x40000000quadrant. This is wrong for the kernel.The opposite of -N is -n, not +n. The +n option tells the linker to search archive libraries iteratively, which I believe is needed for the Linux kernel.
Thanks for the information on the +n option. My old system doesn't document +n. However, with the simple configuration that is being tested, it doesn't seem necessary to link the kernel with +n. Possibly, +n will be required when more modules are configured in the kernel.
Quoted 4 lines
The -N option tells the linker to build a "non-shareable" executable, so it puts text and data together in one segment. The -n option is the default, where shareable text is placed in the first quadrant and data is placed in the second quadrant.
Based on the code in the IPL that is being used, it looks like -N is the correct choice. The IPL doesn't try to load kernel data into the second quadrant as far as I can tell.
Signature · 2 lines
J. David Anglin [email protected] National Research Council of Canada (613) 990-0752 (FAX: 952-6605)