Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

zipl: copy new section introduced by GCC 9 #60

Closed
wants to merge 1 commit into from

Conversation

sharkcz
Copy link
Contributor

@sharkcz sharkcz commented Mar 9, 2019

GCC 9 is using a new section called .rodata.cst8 for some literals and it must be included
when copying the bootloaders to the bin images.

GCC 9 is using a new section called .rodata.cst8 for some literals and it must be included
when copying the bootloaders to the bin images.

Signed-off-by: Dan Horák <dan@danny.cz>
@hoeppnerj hoeppnerj closed this in cdb23f8 Mar 21, 2019
sharkcz referenced this pull request Apr 30, 2019
The stage 3 loader size has to be a multiple of the filesystem
blocksize so that the signature maps with the later in memory
stage 3 loader. The lowest common blocksize is 4k so the image
is padded to a 4k boundary.

Signed-off-by: Stefan Haberland <sth@linux.ibm.com>
Acked-by: Peter Oberparleiter <oberpar@linux.ibm.com>
Signed-off-by: Jan Höppner <hoeppner@linux.ibm.com>
sharkcz added a commit to sharkcz/s390-tools that referenced this pull request May 2, 2019
The objcopy command for stage3.bin needs to take the new rodata section into account.
See also PR ibm-s390-linux#60.

Signed-off-by: Dan Horák <dan@danny.cz>
hoeppnerj pushed a commit that referenced this pull request May 21, 2019
The objcopy command for stage3.bin needs to take the new rodata section
into account.
See also PR #60.

Closes: #61
Signed-off-by: Dan Horák <dan@danny.cz>
Acked-by: Stefan Haberland <sth@linux.ibm.com>
Signed-off-by: Jan Höppner <hoeppner@linux.ibm.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant