Vladimir A. Pavlov wrote:
> On Wednesday 01 November 2006 08:20, Luca wrote:
>
>> I checked and double-checked all the env and settings variables and
>> everything's right, in fact all other packages when cross-compiling gave
>> no errors, this one is the only that broke in this way (however it then
>> checks for cross-compiling only to build some native tools before
>> building the package).
>>
>
> Sorry for my barging into your talking but it seems I can suggest
> something helpful.
>
> 1. First, some philosophy. Luca, if you _know_ the settings are correct
> then you also know what the error is. But you do _not_ know what the
> error is, so you don't know whether you settings are correct.
>
> The best way to prove they are so or to find the error in them is
> sending the output of the "set" command (is you use bash) showing
> all the environment variables and their values, to this list.
>
> 2. Try to reproduce the error. You saw it appeared when configure tried
> to execute "cc conftest.c". Create the file in the directory where
> it was created when ./configuring, like that one described by you
> above (that one from config.log), try to compile it with that
> command and send here the command output.
>
> 3. Are you sure you use "--build=${CLFS_HOST} --host=${CLFS_TARGET}"
> configure flags?
>
>
Hi Vladimir,
Really, I checked manually all the settings, and then checked the
.bashrc file and it's like the book says, finally unset all the
variables and set them by hand before compiling and it broke the same way.
My target works as expected when cross-compiling all other packages, so
I don't understand why texinfo broke... it's the only package that broke...
I tried a lot of times various ways of building, even setting manually
values caught by configure, and texinfo broke on...
My silly trick about commenting all the part regarding cross-compiling
is obviously not a solution but the behaviors of the resulting binaries,
after various tests, is normal, no signs of misbehaviors...
>From configure of texinfo before the check of cross-compiling:
# We need to run some of our own binaries, most notably makedoc, but as
# long as we have this process, we also use our own makeinfo and
# install-info.
#
# This means that if we are cross compiling, we have to configure the
# package twice: once with the native compiler (this is done in a
# subdirectory $native_tools), and once with the cross compiler.
# The former is invoked automatically here, with --host=$build.
# $native_tools is also added to SUBDIRS in the main Makefile.am,
# so that make compiles the native tools first.
#
However the problem is a wrongly triplet check, don't know why it checks
for something different...
Luca
_______________________________________________
Clfs-support mailing list
[email protected]
http://lists.cross-lfs.org/cgi-bin/mailman/listinfo/clfs-support
