crosstool-ng 1.15.2: cloog problems

crosstool-ng 1.15.2: cloog problems

[Thomas De Schampheleire]

[-- Attachment #1: Type: text/plain, Size: 5897 bytes --]

[Please keep me in CC]

Hi,

I'm experiencing trouble with cloog in crosstool-ng 1.15.2, and I
didn't have problems before with 1.13.4. I'm using the same
configuration.

Note: the machine on which I have these problems is running CentOS
5.8, which does not contain the most recent packages of anything. But
note also that the same machine was used before (1.13.4) without
problems.

The first problem was this:

[EXTRA]    Building CLooG/ppl
[ALL  ]    make[3]: Entering directory
`/repo/central/jenkins/workspace/buildroot-eglibc-toolchain/output/build/build-toolchain/.build/powerpc-unknown-linux-gnu/build/build-cloog-ppl-host-x86_64-build_unknown-linux-gnu'
[ALL  ]    cd /repo/central/jenkins/workspace/buildroot-eglibc-toolchain/output/build/build-toolchain/.build/src/cloog-ppl-0.15.9
&& /bin/sh /repo/central/jenkins/workspace/buildroot-eglibc-toolchain/output/build/build-toolchain/.build/src/cloog-ppl-0.15.9/autoconf/missing
--run aclocal-1.9 -I m4

[ALL  ]    aclocal: couldn't open directory `m4': No such file or directory
[ERROR]    make[3]: ***
[/repo/central/jenkins/workspace/buildroot-eglibc-toolchain/output/build/build-toolchain/.build/src/cloog-ppl-0.15.9/aclocal.m4]
Error 1
[ALL  ]    make[3]: Leaving directory
`/repo/central/jenkins/workspace/buildroot-eglibc-toolchain/output/build/build-toolchain/.build/powerpc-unknown-linux-gnu/build/build-cloog-ppl-host-x86_64-build_unknown-linux-gnu'

The m4 directory is indeed not present in cloog-ppl so it shouldn't be
referenced anyway.
I could fix this problem by changing the cloog Makefile.in and
Makefile.am so that the m4 directory is not included (remove
ACLOCAL_AMFLAGS setting).

Then, the second problem arises:

[ALL  ]    if /bin/sh ./libtool --tag=CC --mode=compile
x86_64-build_unknown-linux-gnu-gcc -DHAVE_CONFIG_H -I.
-I/repo/central/jenkins/workspace/buildroot-eglibc-toolchain/output/build/build-toolchain/.build/src/cloog-ppl-0.15.9
-I./include/cloog -I./include
-I/repo/central/jenkins/workspace/buildroot-eglibc-toolchain/output/build/build-toolchain/.build/src/cloog-ppl-0.15.9/include
 -I/repo/central/jenkins/workspace/buildroot-eglibc-toolchain/output/build/build-toolchain/.build/powerpc-unknown-linux-gnu/buildtools/include
-I/repo/central/jenkins/workspace/buildroot-eglibc-toolchain/output/build/build-toolchain/.build/powerpc-unknown-linux-gnu/buildtools/include
 -Wall -fomit-frame-pointer -pipe  -MT options.lo -MD -MP -MF
".deps/options.Tpo" -c -o options.lo `test -f 'source/options.c' ||
echo '/repo/central/jenkins/workspace/buildroot-eglibc-toolchain/output/build/build-toolchain/.build/src/cloog-ppl-0.15.9/'`source/options.c;
      then mv -f ".deps/options.Tpo" ".deps/options.Plo"; else rm -f
".deps/options.Tpo"; exit 1; fi
[ALL  ]    ./libtool: line 466: CDPATH: command not found
[ALL  ]    ./libtool: line 466: CDPATH: command not found
[ALL  ]    ./libtool: line 466: CDPATH: command not found
[ALL  ]    ./libtool: line 466: CDPATH: command not found
[ALL  ]    ./libtool: line 1144: func_opt_split: command not found
[ALL  ]    ./libtool: line 1144: func_opt_split: command not found
[ALL  ]    ./libtool: line 1144: func_opt_split: command not found
[ALL  ]    ./libtool: line 1144: func_opt_split: command not found
[ALL  ]    libtool: Version mismatch error.  This is libtool 2.2.6
Debian-2.2.6a-1ubuntu1, but the
[ALL  ]    libtool: definition of this LT_INIT comes from an older release.
[ALL  ]    libtool: You should recreate aclocal.m4 with macros from
libtool 2.2.6 Debian-2.2.6a-1ubuntu1
[ALL  ]    libtool: and run autoconf again.
[ALL  ]    libtool: Version mismatch error.  This is libtool 2.2.6
Debian-2.2.6a-1ubuntu1, but the
[ALL  ]    libtool: definition of this LT_INIT comes from an older release.
[ALL  ]    libtool: You should recreate aclocal.m4 with macros from
libtool 2.2.6 Debian-2.2.6a-1ubuntu1
[ALL  ]    libtool: and run autoconf again.
[ALL  ]    libtool: Version mismatch error.  This is libtool 2.2.6
Debian-2.2.6a-1ubuntu1, but the
[ALL  ]    libtool: definition of this LT_INIT comes from an older release.
[ALL  ]    libtool: You should recreate aclocal.m4 with macros from
libtool 2.2.6 Debian-2.2.6a-1ubuntu1
[ALL  ]    libtool: and run autoconf again.
[ALL  ]    libtool: Version mismatch error.  This is libtool 2.2.6
Debian-2.2.6a-1ubuntu1, but the
[ALL  ]    libtool: definition of this LT_INIT comes from an older release.
[ALL  ]    libtool: You should recreate aclocal.m4 with macros from
libtool 2.2.6 Debian-2.2.6a-1ubuntu1
[ALL  ]    libtool: and run autoconf again.
[ERROR]    make[3]: *** [block.lo] Error 1
[ALL  ]    make[3]: *** Waiting for unfinished jobs....
[ERROR]    make[3]: *** [loop.lo] Error 1
[ERROR]    make[3]: *** [names.lo] Error 1
[ERROR]    make[3]: *** [options.lo] Error 1
[ALL  ]    make[3]: Leaving directory
`/repo/central/jenkins/workspace/buildroot-eglibc-toolchain/output/build/build-toolchain/.build/powerpc-unknown-linux-gnu/build/build-cloog-ppl-host-x86_64-build_unknown-linux-gnu'

The CDPATH problem stems from the following line in <cloog>/libtool:
$lt_unset CDPATH

Normally $lt_unset is set to 'unset'. This is done through the
configure script. However, when I look at the configure script, it no
longer matches with the version from the tarball. It seems to have
been regenerated, and in the new version, lt_unset no longer exists.
Hence, it resolves to the empty string, and CDPATH is interpreted as a
command.

Has this problem been seen before? Has anything changed in the cloog
area in crosstool-ng.

In the working case, I was using buildroot-2012.02 and crosstool-ng
1.13.4. In the bad case, this is buildroot-2012.05 and
crosstool-ng-1.15.2.
In both cases, automake is at 1.11.1, autoconf at 2.65, libtool at
2.2.10, cloog at 0.15.9.

I send the screen log in attachment (consoleText.gz).
I also send the build.log from the second run (CDPATH problem) (build.log.gz).

Thanks,
Thomas

[-- Attachment #2: consoleText.gz --]
[-- Type: application/x-gzip, Size: 860374 bytes --]

[-- Attachment #3: build.log.gz --]
[-- Type: application/x-gzip, Size: 827222 bytes --]

[-- Attachment #4: Type: text/plain, Size: 71 bytes --]

--
For unsubscribe information see http://sourceware.org/lists.html#faq

Re: crosstool-ng 1.15.2: cloog problems

[Thomas De Schampheleire]

Hi,

On Fri, Jun 8, 2012 at 2:16 PM, Thomas De Schampheleire
<patrickdepinguin@gmail.com> wrote:
> [Please keep me in CC]
>
> Hi,
>
> I'm experiencing trouble with cloog in crosstool-ng 1.15.2, and I
> didn't have problems before with 1.13.4. I'm using the same
> configuration.
>
> Note: the machine on which I have these problems is running CentOS
> 5.8, which does not contain the most recent packages of anything. But
> note also that the same machine was used before (1.13.4) without
> problems.
>
> The first problem was this:
>
> [EXTRA]    Building CLooG/ppl
> [ALL  ]    make[3]: Entering directory
> `/repo/central/jenkins/workspace/buildroot-eglibc-toolchain/output/build/build-toolchain/.build/powerpc-unknown-linux-gnu/build/build-cloog-ppl-host-x86_64-build_unknown-linux-gnu'
> [ALL  ]    cd /repo/central/jenkins/workspace/buildroot-eglibc-toolchain/output/build/build-toolchain/.build/src/cloog-ppl-0.15.9
> && /bin/sh /repo/central/jenkins/workspace/buildroot-eglibc-toolchain/output/build/build-toolchain/.build/src/cloog-ppl-0.15.9/autoconf/missing
> --run aclocal-1.9 -I m4
>
> [ALL  ]    aclocal: couldn't open directory `m4': No such file or directory
> [ERROR]    make[3]: ***
> [/repo/central/jenkins/workspace/buildroot-eglibc-toolchain/output/build/build-toolchain/.build/src/cloog-ppl-0.15.9/aclocal.m4]
> Error 1
> [ALL  ]    make[3]: Leaving directory
> `/repo/central/jenkins/workspace/buildroot-eglibc-toolchain/output/build/build-toolchain/.build/powerpc-unknown-linux-gnu/build/build-cloog-ppl-host-x86_64-build_unknown-linux-gnu'
>
> The m4 directory is indeed not present in cloog-ppl so it shouldn't be
> referenced anyway.
> I could fix this problem by changing the cloog Makefile.in and
> Makefile.am so that the m4 directory is not included (remove
> ACLOCAL_AMFLAGS setting).

So I tracked down the first problem (assuming the second is a
consequence of the first).

In previous crosstool-ng versions (1.14), the cloog sources were not
patched. In the current version, configure and configure.in are
changed. This triggers the cloog Makefile to call the folllowing line:
autoconf/missing --run aclocal-1.9 -I m4

When aclocal-1.9 is not present on the system, all is fine. The script
returns with a simple warning saying that aclocal-1.9 isn't installed
and that you only need it if you changed configure.in. This comes from
the following lines in autoconf/missing:

# If it does not exist, or fails to run (possibly an outdated version),
# try to emulate it.
case "$1" in
  aclocal*)
    echo 1>&2 "\
WARNING: \`$1' is $msg.  You should only need it if
         you modified \`acinclude.m4' or \`${configure_ac}'.  You might want
         to install the \`Automake' and \`Perl' packages.  Grab them from
         any GNU archive site."
    touch aclocal.m4
    ;;


When aclocal-1.9 is present, it actually runs it, with parameter -I
m4' as instructed by the cloog package. However, the m4 directory
doesn't exist and aclocal chokes on it. According to me this is a
problem in the cloog package that should be fixed.

But, I'm troubled by the fact that I haven't found reports about this
anywhere. Do none of you have aclocal-1.9 installed?

What is the best solution here?

One thing that works is make sure that aclocal.m4 is more recent than
the patched configure files (by touching it) so that the missing
script isn't called. This works in the current case because the
patching of configure doesn't have impact on the aclocal.m4 file. It
may not be a generic fix in case configure is patched with more
impact, but it works (I tried).

What do you think? Any input is welcome...

Thanks,
 Thomas

--
For unsubscribe information see http://sourceware.org/lists.html#faq

Re: crosstool-ng 1.15.2: cloog problems

[Thomas De Schampheleire]

On Wed, Jun 13, 2012 at 10:02 AM, Thomas De Schampheleire
<patrickdepinguin@gmail.com> wrote:
> Hi,
>
> On Fri, Jun 8, 2012 at 2:16 PM, Thomas De Schampheleire
> <patrickdepinguin@gmail.com> wrote:
>> [Please keep me in CC]
>>
>> Hi,
>>
>> I'm experiencing trouble with cloog in crosstool-ng 1.15.2, and I
>> didn't have problems before with 1.13.4. I'm using the same
>> configuration.
>>
>> Note: the machine on which I have these problems is running CentOS
>> 5.8, which does not contain the most recent packages of anything. But
>> note also that the same machine was used before (1.13.4) without
>> problems.
>>
>> The first problem was this:
>>
>> [EXTRA]    Building CLooG/ppl
>> [ALL  ]    make[3]: Entering directory
>> `/repo/central/jenkins/workspace/buildroot-eglibc-toolchain/output/build/build-toolchain/.build/powerpc-unknown-linux-gnu/build/build-cloog-ppl-host-x86_64-build_unknown-linux-gnu'
>> [ALL  ]    cd /repo/central/jenkins/workspace/buildroot-eglibc-toolchain/output/build/build-toolchain/.build/src/cloog-ppl-0.15.9
>> && /bin/sh /repo/central/jenkins/workspace/buildroot-eglibc-toolchain/output/build/build-toolchain/.build/src/cloog-ppl-0.15.9/autoconf/missing
>> --run aclocal-1.9 -I m4
>>
>> [ALL  ]    aclocal: couldn't open directory `m4': No such file or directory
>> [ERROR]    make[3]: ***
>> [/repo/central/jenkins/workspace/buildroot-eglibc-toolchain/output/build/build-toolchain/.build/src/cloog-ppl-0.15.9/aclocal.m4]
>> Error 1
>> [ALL  ]    make[3]: Leaving directory
>> `/repo/central/jenkins/workspace/buildroot-eglibc-toolchain/output/build/build-toolchain/.build/powerpc-unknown-linux-gnu/build/build-cloog-ppl-host-x86_64-build_unknown-linux-gnu'
>>
>> The m4 directory is indeed not present in cloog-ppl so it shouldn't be
>> referenced anyway.
>> I could fix this problem by changing the cloog Makefile.in and
>> Makefile.am so that the m4 directory is not included (remove
>> ACLOCAL_AMFLAGS setting).
>
> So I tracked down the first problem (assuming the second is a
> consequence of the first).
>
> In previous crosstool-ng versions (1.14), the cloog sources were not
> patched. In the current version, configure and configure.in are
> changed. This triggers the cloog Makefile to call the folllowing line:
> autoconf/missing --run aclocal-1.9 -I m4
>
> When aclocal-1.9 is not present on the system, all is fine. The script
> returns with a simple warning saying that aclocal-1.9 isn't installed
> and that you only need it if you changed configure.in. This comes from
> the following lines in autoconf/missing:
>
> # If it does not exist, or fails to run (possibly an outdated version),
> # try to emulate it.
> case "$1" in
>  aclocal*)
>    echo 1>&2 "\
> WARNING: \`$1' is $msg.  You should only need it if
>         you modified \`acinclude.m4' or \`${configure_ac}'.  You might want
>         to install the \`Automake' and \`Perl' packages.  Grab them from
>         any GNU archive site."
>    touch aclocal.m4
>    ;;
>
>
> When aclocal-1.9 is present, it actually runs it, with parameter -I
> m4' as instructed by the cloog package. However, the m4 directory
> doesn't exist and aclocal chokes on it. According to me this is a
> problem in the cloog package that should be fixed.
>
> But, I'm troubled by the fact that I haven't found reports about this
> anywhere. Do none of you have aclocal-1.9 installed?
>
> What is the best solution here?
>
> One thing that works is make sure that aclocal.m4 is more recent than
> the patched configure files (by touching it) so that the missing
> script isn't called. This works in the current case because the
> patching of configure doesn't have impact on the aclocal.m4 file. It
> may not be a generic fix in case configure is patched with more
> impact, but it works (I tried).
>
> What do you think? Any input is welcome...
>

Yann, any input?

--
For unsubscribe information see http://sourceware.org/lists.html#faq

Re: crosstool-ng 1.15.2: cloog problems

[Per Arnold Blaasmo]

On 25. juni 2012 15:21, Thomas De Schampheleire wrote:
> On Wed, Jun 13, 2012 at 10:02 AM, Thomas De Schampheleire
> <patrickdepinguin@gmail.com> wrote:
>> Hi,
>>
>> On Fri, Jun 8, 2012 at 2:16 PM, Thomas De Schampheleire
>> <patrickdepinguin@gmail.com> wrote:
>>> [Please keep me in CC]
>>>
>>> Hi,
>>>
>>> I'm experiencing trouble with cloog in crosstool-ng 1.15.2, and I
>>> didn't have problems before with 1.13.4. I'm using the same
>>> configuration.
>>>
>>> Note: the machine on which I have these problems is running CentOS
>>> 5.8, which does not contain the most recent packages of anything. But
>>> note also that the same machine was used before (1.13.4) without
>>> problems.
>>>
>>> The first problem was this:
>>>
>>> [EXTRA]    Building CLooG/ppl
>>> [ALL  ]    make[3]: Entering directory
>>> `/repo/central/jenkins/workspace/buildroot-eglibc-toolchain/output/build/build-toolchain/.build/powerpc-unknown-linux-gnu/build/build-cloog-ppl-host-x86_64-build_unknown-linux-gnu'
>>> [ALL  ]    cd /repo/central/jenkins/workspace/buildroot-eglibc-toolchain/output/build/build-toolchain/.build/src/cloog-ppl-0.15.9
>>> && /bin/sh /repo/central/jenkins/workspace/buildroot-eglibc-toolchain/output/build/build-toolchain/.build/src/cloog-ppl-0.15.9/autoconf/missing
>>> --run aclocal-1.9 -I m4
>>>
>>> [ALL  ]    aclocal: couldn't open directory `m4': No such file or directory
>>> [ERROR]    make[3]: ***
>>> [/repo/central/jenkins/workspace/buildroot-eglibc-toolchain/output/build/build-toolchain/.build/src/cloog-ppl-0.15.9/aclocal.m4]
>>> Error 1
>>> [ALL  ]    make[3]: Leaving directory
>>> `/repo/central/jenkins/workspace/buildroot-eglibc-toolchain/output/build/build-toolchain/.build/powerpc-unknown-linux-gnu/build/build-cloog-ppl-host-x86_64-build_unknown-linux-gnu'
>>>
>>> The m4 directory is indeed not present in cloog-ppl so it shouldn't be
>>> referenced anyway.
>>> I could fix this problem by changing the cloog Makefile.in and
>>> Makefile.am so that the m4 directory is not included (remove
>>> ACLOCAL_AMFLAGS setting).
>>
>> So I tracked down the first problem (assuming the second is a
>> consequence of the first).
>>
>> In previous crosstool-ng versions (1.14), the cloog sources were not
>> patched. In the current version, configure and configure.in are
>> changed. This triggers the cloog Makefile to call the folllowing line:
>> autoconf/missing --run aclocal-1.9 -I m4
>>
>> When aclocal-1.9 is not present on the system, all is fine. The script
>> returns with a simple warning saying that aclocal-1.9 isn't installed
>> and that you only need it if you changed configure.in. This comes from
>> the following lines in autoconf/missing:
>>
>> # If it does not exist, or fails to run (possibly an outdated version),
>> # try to emulate it.
>> case "$1" in
>>  aclocal*)
>>    echo 1>&2 "\
>> WARNING: \`$1' is $msg.  You should only need it if
>>         you modified \`acinclude.m4' or \`${configure_ac}'.  You might want
>>         to install the \`Automake' and \`Perl' packages.  Grab them from
>>         any GNU archive site."
>>    touch aclocal.m4
>>    ;;
>>
>>
>> When aclocal-1.9 is present, it actually runs it, with parameter -I
>> m4' as instructed by the cloog package. However, the m4 directory
>> doesn't exist and aclocal chokes on it. According to me this is a
>> problem in the cloog package that should be fixed.
>>
>> But, I'm troubled by the fact that I haven't found reports about this
>> anywhere. Do none of you have aclocal-1.9 installed?
>>
>> What is the best solution here?
>>
>> One thing that works is make sure that aclocal.m4 is more recent than
>> the patched configure files (by touching it) so that the missing
>> script isn't called. This works in the current case because the
>> patching of configure doesn't have impact on the aclocal.m4 file. It
>> may not be a generic fix in case configure is patched with more
>> impact, but it works (I tried).
>>
>> What do you think? Any input is welcome...
>>
> 
> Yann, any input?
> 
> --
> For unsubscribe information see http://sourceware.org/lists.html#faq
> 
> 
I have the same problem with aclocal-1.11.
I have configured using CT-COMP-TOOLS=y
so all autoconf tools are downloaded and set up by ct-ng.

I have not figured how to fix it yet?

Per A.


--
For unsubscribe information see http://sourceware.org/lists.html#faq

Re: crosstool-ng 1.15.2: cloog problems

[Per Arnold Blaasmo]

On 27. juli 2012 12:15, Per Arnold Blaasmo wrote:
> On 25. juni 2012 15:21, Thomas De Schampheleire wrote:
>> On Wed, Jun 13, 2012 at 10:02 AM, Thomas De Schampheleire
>> <patrickdepinguin@gmail.com> wrote:
>>> Hi,
>>>
>>> On Fri, Jun 8, 2012 at 2:16 PM, Thomas De Schampheleire
>>> <patrickdepinguin@gmail.com> wrote:
>>>> [Please keep me in CC]
>>>>
>>>> Hi,
>>>>
>>>> I'm experiencing trouble with cloog in crosstool-ng 1.15.2, and I
>>>> didn't have problems before with 1.13.4. I'm using the same
>>>> configuration.
>>>>
>>>> Note: the machine on which I have these problems is running CentOS
>>>> 5.8, which does not contain the most recent packages of anything. But
>>>> note also that the same machine was used before (1.13.4) without
>>>> problems.
>>>>
>>>> The first problem was this:
>>>>
>>>> [EXTRA]    Building CLooG/ppl
>>>> [ALL  ]    make[3]: Entering directory
>>>> `/repo/central/jenkins/workspace/buildroot-eglibc-toolchain/output/build/build-toolchain/.build/powerpc-unknown-linux-gnu/build/build-cloog-ppl-host-x86_64-build_unknown-linux-gnu'
>>>> [ALL  ]    cd /repo/central/jenkins/workspace/buildroot-eglibc-toolchain/output/build/build-toolchain/.build/src/cloog-ppl-0.15.9
>>>> && /bin/sh /repo/central/jenkins/workspace/buildroot-eglibc-toolchain/output/build/build-toolchain/.build/src/cloog-ppl-0.15.9/autoconf/missing
>>>> --run aclocal-1.9 -I m4
>>>>
>>>> [ALL  ]    aclocal: couldn't open directory `m4': No such file or directory
>>>> [ERROR]    make[3]: ***
>>>> [/repo/central/jenkins/workspace/buildroot-eglibc-toolchain/output/build/build-toolchain/.build/src/cloog-ppl-0.15.9/aclocal.m4]
>>>> Error 1
>>>> [ALL  ]    make[3]: Leaving directory
>>>> `/repo/central/jenkins/workspace/buildroot-eglibc-toolchain/output/build/build-toolchain/.build/powerpc-unknown-linux-gnu/build/build-cloog-ppl-host-x86_64-build_unknown-linux-gnu'
>>>>
>>>> The m4 directory is indeed not present in cloog-ppl so it shouldn't be
>>>> referenced anyway.
>>>> I could fix this problem by changing the cloog Makefile.in and
>>>> Makefile.am so that the m4 directory is not included (remove
>>>> ACLOCAL_AMFLAGS setting).
>>>
>>> So I tracked down the first problem (assuming the second is a
>>> consequence of the first).
>>>
>>> In previous crosstool-ng versions (1.14), the cloog sources were not
>>> patched. In the current version, configure and configure.in are
>>> changed. This triggers the cloog Makefile to call the folllowing line:
>>> autoconf/missing --run aclocal-1.9 -I m4
>>>
>>> When aclocal-1.9 is not present on the system, all is fine. The script
>>> returns with a simple warning saying that aclocal-1.9 isn't installed
>>> and that you only need it if you changed configure.in. This comes from
>>> the following lines in autoconf/missing:
>>>
>>> # If it does not exist, or fails to run (possibly an outdated version),
>>> # try to emulate it.
>>> case "$1" in
>>>  aclocal*)
>>>    echo 1>&2 "\
>>> WARNING: \`$1' is $msg.  You should only need it if
>>>         you modified \`acinclude.m4' or \`${configure_ac}'.  You might want
>>>         to install the \`Automake' and \`Perl' packages.  Grab them from
>>>         any GNU archive site."
>>>    touch aclocal.m4
>>>    ;;
>>>
>>>
>>> When aclocal-1.9 is present, it actually runs it, with parameter -I
>>> m4' as instructed by the cloog package. However, the m4 directory
>>> doesn't exist and aclocal chokes on it. According to me this is a
>>> problem in the cloog package that should be fixed.
>>>
>>> But, I'm troubled by the fact that I haven't found reports about this
>>> anywhere. Do none of you have aclocal-1.9 installed?
>>>
>>> What is the best solution here?
>>>
>>> One thing that works is make sure that aclocal.m4 is more recent than
>>> the patched configure files (by touching it) so that the missing
>>> script isn't called. This works in the current case because the
>>> patching of configure doesn't have impact on the aclocal.m4 file. It
>>> may not be a generic fix in case configure is patched with more
>>> impact, but it works (I tried).
>>>
>>> What do you think? Any input is welcome...
>>>
>>
>> Yann, any input?
>>
>> --
>> For unsubscribe information see http://sourceware.org/lists.html#faq
>>
>>
> I have the same problem with aclocal-1.11.
> I have configured using CT-COMP-TOOLS=y
> so all autoconf tools are downloaded and set up by ct-ng.
> 
> I have not figured how to fix it yet?
> 
> Per A.
> 
> 
> --
> For unsubscribe information see http://sourceware.org/lists.html#faq
> 
> 
> 
Hmmm....
Running it on my Fedora 17 box worked OK, but the previous attempt was
on a RHEL 5.8 box.

I am not sure why this difference is?

Per A.

--
For unsubscribe information see http://sourceware.org/lists.html#faq

Re: crosstool-ng 1.15.2: cloog problems

[Per Arnold Blaasmo]

On 27. juli 2012 12:44, Per Arnold Blaasmo wrote:
> On 27. juli 2012 12:15, Per Arnold Blaasmo wrote:
>> On 25. juni 2012 15:21, Thomas De Schampheleire wrote:
>>> On Wed, Jun 13, 2012 at 10:02 AM, Thomas De Schampheleire
>>> <patrickdepinguin@gmail.com> wrote:
>>>> Hi,
>>>>
>>>> On Fri, Jun 8, 2012 at 2:16 PM, Thomas De Schampheleire
>>>> <patrickdepinguin@gmail.com> wrote:
>>>>> [Please keep me in CC]
>>>>>
>>>>> Hi,
>>>>>
>>>>> I'm experiencing trouble with cloog in crosstool-ng 1.15.2, and I
>>>>> didn't have problems before with 1.13.4. I'm using the same
>>>>> configuration.
>>>>>
>>>>> Note: the machine on which I have these problems is running CentOS
>>>>> 5.8, which does not contain the most recent packages of anything. But
>>>>> note also that the same machine was used before (1.13.4) without
>>>>> problems.
>>>>>
>>>>> The first problem was this:
>>>>>
>>>>> [EXTRA]    Building CLooG/ppl
>>>>> [ALL  ]    make[3]: Entering directory
>>>>> `/repo/central/jenkins/workspace/buildroot-eglibc-toolchain/output/build/build-toolchain/.build/powerpc-unknown-linux-gnu/build/build-cloog-ppl-host-x86_64-build_unknown-linux-gnu'
>>>>> [ALL  ]    cd /repo/central/jenkins/workspace/buildroot-eglibc-toolchain/output/build/build-toolchain/.build/src/cloog-ppl-0.15.9
>>>>> && /bin/sh /repo/central/jenkins/workspace/buildroot-eglibc-toolchain/output/build/build-toolchain/.build/src/cloog-ppl-0.15.9/autoconf/missing
>>>>> --run aclocal-1.9 -I m4
>>>>>
>>>>> [ALL  ]    aclocal: couldn't open directory `m4': No such file or directory
>>>>> [ERROR]    make[3]: ***
>>>>> [/repo/central/jenkins/workspace/buildroot-eglibc-toolchain/output/build/build-toolchain/.build/src/cloog-ppl-0.15.9/aclocal.m4]
>>>>> Error 1
>>>>> [ALL  ]    make[3]: Leaving directory
>>>>> `/repo/central/jenkins/workspace/buildroot-eglibc-toolchain/output/build/build-toolchain/.build/powerpc-unknown-linux-gnu/build/build-cloog-ppl-host-x86_64-build_unknown-linux-gnu'
>>>>>
>>>>> The m4 directory is indeed not present in cloog-ppl so it shouldn't be
>>>>> referenced anyway.
>>>>> I could fix this problem by changing the cloog Makefile.in and
>>>>> Makefile.am so that the m4 directory is not included (remove
>>>>> ACLOCAL_AMFLAGS setting).
>>>>
>>>> So I tracked down the first problem (assuming the second is a
>>>> consequence of the first).
>>>>
>>>> In previous crosstool-ng versions (1.14), the cloog sources were not
>>>> patched. In the current version, configure and configure.in are
>>>> changed. This triggers the cloog Makefile to call the folllowing line:
>>>> autoconf/missing --run aclocal-1.9 -I m4
>>>>
>>>> When aclocal-1.9 is not present on the system, all is fine. The script
>>>> returns with a simple warning saying that aclocal-1.9 isn't installed
>>>> and that you only need it if you changed configure.in. This comes from
>>>> the following lines in autoconf/missing:
>>>>
>>>> # If it does not exist, or fails to run (possibly an outdated version),
>>>> # try to emulate it.
>>>> case "$1" in
>>>>  aclocal*)
>>>>    echo 1>&2 "\
>>>> WARNING: \`$1' is $msg.  You should only need it if
>>>>         you modified \`acinclude.m4' or \`${configure_ac}'.  You might want
>>>>         to install the \`Automake' and \`Perl' packages.  Grab them from
>>>>         any GNU archive site."
>>>>    touch aclocal.m4
>>>>    ;;
>>>>
>>>>
>>>> When aclocal-1.9 is present, it actually runs it, with parameter -I
>>>> m4' as instructed by the cloog package. However, the m4 directory
>>>> doesn't exist and aclocal chokes on it. According to me this is a
>>>> problem in the cloog package that should be fixed.
>>>>
>>>> But, I'm troubled by the fact that I haven't found reports about this
>>>> anywhere. Do none of you have aclocal-1.9 installed?
>>>>
>>>> What is the best solution here?
>>>>
>>>> One thing that works is make sure that aclocal.m4 is more recent than
>>>> the patched configure files (by touching it) so that the missing
>>>> script isn't called. This works in the current case because the
>>>> patching of configure doesn't have impact on the aclocal.m4 file. It
>>>> may not be a generic fix in case configure is patched with more
>>>> impact, but it works (I tried).
>>>>
>>>> What do you think? Any input is welcome...
>>>>
>>>
>>> Yann, any input?
>>>
>>> --
>>> For unsubscribe information see http://sourceware.org/lists.html#faq
>>>
>>>
>> I have the same problem with aclocal-1.11.
>> I have configured using CT-COMP-TOOLS=y
>> so all autoconf tools are downloaded and set up by ct-ng.
>>
>> I have not figured how to fix it yet?
>>
>> Per A.
>>
>>
>> --
>> For unsubscribe information see http://sourceware.org/lists.html#faq
>>
>>
>>
> Hmmm....
> Running it on my Fedora 17 box worked OK, but the previous attempt was
> on a RHEL 5.8 box.
> 
> I am not sure why this difference is?
> 
> Per A.
> 
> --
> For unsubscribe information see http://sourceware.org/lists.html#faq
> 
> 
> 
I found a workaround at
http://www.mail-archive.com/fink-users@lists.sourceforge.net/msg30365.html

I solved it by adding a m4 folder to the cloog-ppl-<version>.tar.gz file.

I did this in a build job (we use Jenkins) by:
1. first extract the original cloog-ppl.tar.gz to a tmp folder
2. make a empty dir called 'm4' in the top of cloog source folder.
3. pack the folder back to a tar.gz file overwriting the orginal
cloog-ppl-<version>.tar.gz
4. start ct-ng with this modified cloog-ppl.tar.gz file.

I guess a better solution is to add a patch file to ct-ng that adds the
empty folder.

Per A.

--
For unsubscribe information see http://sourceware.org/lists.html#faq

Re: crosstool-ng 1.15.2: cloog problems

[Per Arnold Blaasmo]

[-- Attachment #1: Type: text/plain, Size: 5910 bytes --]

On 27. juli 2012 13:53, Per Arnold Blaasmo wrote:
> On 27. juli 2012 12:44, Per Arnold Blaasmo wrote:
>> On 27. juli 2012 12:15, Per Arnold Blaasmo wrote:
>>> On 25. juni 2012 15:21, Thomas De Schampheleire wrote:
>>>> On Wed, Jun 13, 2012 at 10:02 AM, Thomas De Schampheleire
>>>> <patrickdepinguin@gmail.com> wrote:
>>>>> Hi,
>>>>>
>>>>> On Fri, Jun 8, 2012 at 2:16 PM, Thomas De Schampheleire
>>>>> <patrickdepinguin@gmail.com> wrote:
>>>>>> [Please keep me in CC]
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I'm experiencing trouble with cloog in crosstool-ng 1.15.2, and I
>>>>>> didn't have problems before with 1.13.4. I'm using the same
>>>>>> configuration.
>>>>>>
>>>>>> Note: the machine on which I have these problems is running CentOS
>>>>>> 5.8, which does not contain the most recent packages of anything. But
>>>>>> note also that the same machine was used before (1.13.4) without
>>>>>> problems.
>>>>>>
>>>>>> The first problem was this:
>>>>>>
>>>>>> [EXTRA]    Building CLooG/ppl
>>>>>> [ALL  ]    make[3]: Entering directory
>>>>>> `/repo/central/jenkins/workspace/buildroot-eglibc-toolchain/output/build/build-toolchain/.build/powerpc-unknown-linux-gnu/build/build-cloog-ppl-host-x86_64-build_unknown-linux-gnu'
>>>>>> [ALL  ]    cd /repo/central/jenkins/workspace/buildroot-eglibc-toolchain/output/build/build-toolchain/.build/src/cloog-ppl-0.15.9
>>>>>> && /bin/sh /repo/central/jenkins/workspace/buildroot-eglibc-toolchain/output/build/build-toolchain/.build/src/cloog-ppl-0.15.9/autoconf/missing
>>>>>> --run aclocal-1.9 -I m4
>>>>>>
>>>>>> [ALL  ]    aclocal: couldn't open directory `m4': No such file or directory
>>>>>> [ERROR]    make[3]: ***
>>>>>> [/repo/central/jenkins/workspace/buildroot-eglibc-toolchain/output/build/build-toolchain/.build/src/cloog-ppl-0.15.9/aclocal.m4]
>>>>>> Error 1
>>>>>> [ALL  ]    make[3]: Leaving directory
>>>>>> `/repo/central/jenkins/workspace/buildroot-eglibc-toolchain/output/build/build-toolchain/.build/powerpc-unknown-linux-gnu/build/build-cloog-ppl-host-x86_64-build_unknown-linux-gnu'
>>>>>>
>>>>>> The m4 directory is indeed not present in cloog-ppl so it shouldn't be
>>>>>> referenced anyway.
>>>>>> I could fix this problem by changing the cloog Makefile.in and
>>>>>> Makefile.am so that the m4 directory is not included (remove
>>>>>> ACLOCAL_AMFLAGS setting).
>>>>>
>>>>> So I tracked down the first problem (assuming the second is a
>>>>> consequence of the first).
>>>>>
>>>>> In previous crosstool-ng versions (1.14), the cloog sources were not
>>>>> patched. In the current version, configure and configure.in are
>>>>> changed. This triggers the cloog Makefile to call the folllowing line:
>>>>> autoconf/missing --run aclocal-1.9 -I m4
>>>>>
>>>>> When aclocal-1.9 is not present on the system, all is fine. The script
>>>>> returns with a simple warning saying that aclocal-1.9 isn't installed
>>>>> and that you only need it if you changed configure.in. This comes from
>>>>> the following lines in autoconf/missing:
>>>>>
>>>>> # If it does not exist, or fails to run (possibly an outdated version),
>>>>> # try to emulate it.
>>>>> case "$1" in
>>>>>  aclocal*)
>>>>>    echo 1>&2 "\
>>>>> WARNING: \`$1' is $msg.  You should only need it if
>>>>>         you modified \`acinclude.m4' or \`${configure_ac}'.  You might want
>>>>>         to install the \`Automake' and \`Perl' packages.  Grab them from
>>>>>         any GNU archive site."
>>>>>    touch aclocal.m4
>>>>>    ;;
>>>>>
>>>>>
>>>>> When aclocal-1.9 is present, it actually runs it, with parameter -I
>>>>> m4' as instructed by the cloog package. However, the m4 directory
>>>>> doesn't exist and aclocal chokes on it. According to me this is a
>>>>> problem in the cloog package that should be fixed.
>>>>>
>>>>> But, I'm troubled by the fact that I haven't found reports about this
>>>>> anywhere. Do none of you have aclocal-1.9 installed?
>>>>>
>>>>> What is the best solution here?
>>>>>
>>>>> One thing that works is make sure that aclocal.m4 is more recent than
>>>>> the patched configure files (by touching it) so that the missing
>>>>> script isn't called. This works in the current case because the
>>>>> patching of configure doesn't have impact on the aclocal.m4 file. It
>>>>> may not be a generic fix in case configure is patched with more
>>>>> impact, but it works (I tried).
>>>>>
>>>>> What do you think? Any input is welcome...
>>>>>
>>>>
>>>> Yann, any input?
>>>>
>>>> --
>>>> For unsubscribe information see http://sourceware.org/lists.html#faq
>>>>
>>>>
>>> I have the same problem with aclocal-1.11.
>>> I have configured using CT-COMP-TOOLS=y
>>> so all autoconf tools are downloaded and set up by ct-ng.
>>>
>>> I have not figured how to fix it yet?
>>>
>>> Per A.
>>>
>>>
>>> --
>>> For unsubscribe information see http://sourceware.org/lists.html#faq
>>>
>>>
>>>
>> Hmmm....
>> Running it on my Fedora 17 box worked OK, but the previous attempt was
>> on a RHEL 5.8 box.
>>
>> I am not sure why this difference is?
>>
>> Per A.
>>
>> --
>> For unsubscribe information see http://sourceware.org/lists.html#faq
>>
>>
>>
> I found a workaround at
> http://www.mail-archive.com/fink-users@lists.sourceforge.net/msg30365.html
> 
> I solved it by adding a m4 folder to the cloog-ppl-<version>.tar.gz file.
> 
> I did this in a build job (we use Jenkins) by:
> 1. first extract the original cloog-ppl.tar.gz to a tmp folder
> 2. make a empty dir called 'm4' in the top of cloog source folder.
> 3. pack the folder back to a tar.gz file overwriting the orginal
> cloog-ppl-<version>.tar.gz
> 4. start ct-ng with this modified cloog-ppl.tar.gz file.
> 
> I guess a better solution is to add a patch file to ct-ng that adds the
> empty folder.
> 
> Per A.
> 
> --
> For unsubscribe information see http://sourceware.org/lists.html#faq
> 
> 
> 
OK, final workaround :-)
Here is a patch file that can bee copied to the cloog-ppl patch folder.

Per A.


[-- Attachment #2: 101-missing_m4_folder.patch --]
[-- Type: application/x-patch, Size: 260 bytes --]

[-- Attachment #3: Type: text/plain, Size: 71 bytes --]

--
For unsubscribe information see http://sourceware.org/lists.html#faq

Re: crosstool-ng 1.15.2: cloog problems

[Yann E. MORIN]

Per-Arnold, Thomas, All,

On Friday 27 July 2012 15:50:02 Per Arnold Blaasmo wrote:
> >>>>>> I'm experiencing trouble with cloog in crosstool-ng 1.15.2, and I
> >>>>>> didn't have problems before with 1.13.4. I'm using the same
> >>>>>> configuration.
[--SNIP--]
> > I found a workaround at
> > http://www.mail-archive.com/fink-users@lists.sourceforge.net/msg30365.html
> > 
> > I solved it by adding a m4 folder to the cloog-ppl-<version>.tar.gz file.
[--SNIP--]
> > I guess a better solution is to add a patch file to ct-ng that adds the
> > empty folder.
> OK, final workaround :-)
> Here is a patch file that can bee copied to the cloog-ppl patch folder.

Sorry to come back on this one that late... Real life can be demanding at
times...

I fixed it in a different way: always create the m4/ directory right after
cloog-ppl is extracted. I'll push it very soon.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

--
For unsubscribe information see http://sourceware.org/lists.html#faq