I have Fedora 7 with gcc-4.1.2-12 and was trying to compile LFS.
Something went wrong and i opened compat/memcmp.c to see what.
Can you just look at the code i think it is trivial.
Thanks Mladen
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This is a duplicate of bug #1631017, which is reported as fixed in both HEAD and 8.4. The files on HEAD and core-8-4-branch differ: is there a reason for that?
Assigning to dkf as he reported this fixed.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
| The real bug is that compat/memcmp.c is being used in the first place -
| if the build system is trying to use this file at all, it indicates that
| the configure script has failed to detect a working C compiler.
Other reports indicate that this happens when trying to cross-compile.
One proposed solution is to use AC_TRY_LINK instead of AC_TRY_RUN.
(sorry, reference not handy, I just vaguely remember reading this somewhere).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
memcmp.c patch
Logged In: YES
user_id=148712
Originator: NO
Could you please explain what "unable to compile" means? What platform are you on?
Logged In: NO
I have Fedora 7 with gcc-4.1.2-12 and was trying to compile LFS.
Something went wrong and i opened compat/memcmp.c to see what.
Can you just look at the code i think it is trivial.
Thanks Mladen
Logged In: YES
user_id=148712
Originator: NO
This is a duplicate of bug #1631017, which is reported as fixed in both HEAD and 8.4. The files on HEAD and core-8-4-branch differ: is there a reason for that?
Assigning to dkf as he reported this fixed.
Logged In: YES
user_id=68433
Originator: NO
From comments in #1631017:
| The real bug is that compat/memcmp.c is being used in the first place -
| if the build system is trying to use this file at all, it indicates that
| the configure script has failed to detect a working C compiler.
Other reports indicate that this happens when trying to cross-compile.
One proposed solution is to use AC_TRY_LINK instead of AC_TRY_RUN.
(sorry, reference not handy, I just vaguely remember reading this somewhere).
Logged In: YES
user_id=79902
Originator: NO
Fixed the obvious fault in compat/memcmp.c; I won't try to think about the bugs relating to why that file exists or is used.