-
Notifications
You must be signed in to change notification settings - Fork 144
support i386 #456
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
support i386 #456
Conversation
Signed-off-by: Luca Dariz <luca.dariz@gmail.com>
60d8360 to
18ef109
Compare
| lkl_get_free_irq lkl_put_irq lkl_is_running lkl_bug lkl_printf | ||
|
|
||
| ifeq ($(OUTPUT_FORMAT),elf32-i386) | ||
| LKL_ENTRY_POINTS += \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The symbols added here are not "LKL_ENTRY_POINTS", right? I have no idea what to call the variable used in the objcopy-invocation should be called like insteadm though, So maybe we have one variable that we fill conditionally (if i386) add these thunk-symbols and then unconditionally add LKL_ENTRY_POINTS. As I said, though I have a hard time coming up with a name.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok, i'll update the patch in the next days
|
It should be mentioned that, I suppose, different compiler versions are looking for different symbol names: sometimes it is |
Thank you, I didn't think about that. Any idea how to detect the compiler? From a quick grep I didn't find examples in linux, maybe something like |
8bd2734 to
c520f30
Compare
|
I tried with 32-bit clang and no modifications are necessary, everything compiles and test pass as well. Unfortunately I can't test other compilers like intel icc. |
thehajime
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think keep using LKL_ENTRY_POINTS would be nicer.
c520f30 to
18ef109
Compare
|
removed the commit with the LKL_ENTRY_POINTS modification |
|
thanks @luckyluke. the update is fine. another thought is if we can have CI (circleci) for i386 build/tests. it would be great if you added an i386 build instance for circleci if possible ? current our CI is running here: |
|
Hi @thehajime, thank you for the feedback. |
Signed-off-by: Luca Dariz <luca.dariz@gmail.com>
Signed-off-by: Luca Dariz <luca.dariz@gmail.com>
Signed-off-by: Luca Dariz <luca.dariz@gmail.com>
|
Hi @thehajime I added a circleci config on a container I created based on ubuntu i386. This required some more fix for the tests, I guess due to different versions of gcc and btrfs-tools from my debian machine. |
Thanks ! LGTM.
for the btrfs-tools, it is also useful with newer mkfs.btrfs; my fedora uses |
|
@luckyluke for the follow up fix, could you please make a pull request to https://github.com/lkl/lkl-docker/commits/master ? if we could make the image, we may be able to pull the docker image from docker hub (lkldocker/). |
Basic support for i386, should fix #341
This change is