[Clfs-support] Problem compiling e2fsprogs
Andrew Bradford
bradfa at gmail.com
Sun Jan 9 08:12:57 PST 2011
On Fri, Jan 7, 2011 at 11:37 PM, Nazmul Alam <fadedreamz at gmail.com> wrote:
> Andrew ,
>
> Thank you. I will try them out.
>
> There were at least two file which uses utime.h, one is debugfs another is
> misc.c (probably).
>
I'm not sure which misc.c you are referring to, I've not had any problems
with e2fsprogs compiling complaining about a misc.c. Maybe my configure
switches prevent building of misc.c? I don't know.
> I found something interesting, kind of a hint, while searching for solution
> to a error (gcc). It suggested that somewhere in build process the LD flag
> is set to its default setting. I was wondering, if anything like this is
> happening in e2fsprogs compilation.
>
I don't think the LD flag is getting reset to its default setting. Using
the switches in the book, "--with-linker=${LD}" should pull the LD variable
from the clfs user's environment which should be set to
"arm-unknown-linux-uclibc-ld".
For newer versions of e2fsprogs (like e2fsprogs-1.41.14), the
"--with-linker" and "--with-cc" switches don't work any more, you'll get an
error at the start of the configure script like:
configure: WARNING: unrecognized options: --with-linker
or
configure: WARNING: unrecognized options: --with-cc
But it doesn't matter, as configure can still find the correct linker even
without a hint and the "CC=${CC}" takes care of defining which compiler we
want to use.
Regards,
Andrew
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.clfs.org/pipermail/clfs-support-clfs.org/attachments/20110109/c06a0376/attachment-0001.htm>
More information about the Clfs-support
mailing list