[Linux]Error when building .deb package for rev2526

[Michael]

Hello,

I am trying to build a .deb package of revision 2526 (Ubuntu 6.06, GCC 4.0.3), but I get the following error:

creating libastyle.la
(cd .libs && rm -f libastyle.la && ln -s ../libastyle.la libastyle.la)
make[5]: *** No rule to make target `astyle/compiler_defines.h', needed by `all-am'.  Stop.
make[5]: Leaving directory `/home/michael/codeblocks/trunk/src/plugins/astyle'
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory `/home/michael/codeblocks/trunk/src/plugins/astyle'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/home/michael/codeblocks/trunk/src/plugins'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/michael/codeblocks/trunk/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/michael/codeblocks/trunk'
make: *** [build-stamp] Error 2

I have tried to do a ./configure --enable-contrib, but it did not solve the problem.

Any idea?

Thank you.

Best wishes,
Michael

[Der Meister]

Delete this file - it was removed in revision 2523.

[Michael]

Delete this file - it was removed in revision 2523.

Hello,

Thank you for the help.

After checking the file astyle/compiler_defines.h is not present (it has probably been already removed). May be the makefile has not been updated.

Best wishes,
Michael

[Michael]

Delete this file - it was removed in revision 2523.

After checking the file astyle/compiler_defines.h is not present (it has probably been already removed). May be the makefile has not been updated.

It seems that I needed:

1) sudo aclocal
2) sudo ./bootstrap
3) sudo ./configure --enable-contrib

Now it seems to build fine .

Best wishes,
Michael

[Game_Ender]

1) sudo aclocal
2) sudo ./bootstrap
3) sudo ./configure --enable-contrib

The real question is why weren't you doing this from start? Maybe I am paranoid but I have always been suspicious that autotool created build files will work after an update.  So I have figured you need to regenerate the build system after each update.

I don't think the aclocal is needed I would do:

Code

make distclean
./bootstrap
./configure --enable-contrib
make
sudo make install # sudo only need if install system wide

By the way, why do you have to be root to bootstrap and configure?  Is that do to the package building environment?

[Michael]

1) sudo aclocal
2) sudo ./bootstrap
3) sudo ./configure --enable-contrib

The real question is why weren't you doing this from start? Maybe I am paranoid but I have always been suspicious that autotool created build files will work after an update.  So I have figured you need to regenerate the build system after each update.

When I have tried to build a .deb package of rev2526 (with the changes suggested by daniel2000), I got an error. I have remarked that sometime re-doing a ./configure solved the problem. Anyway, not in this case. So, I have re-done a ./bootstrap to regenerate all. But during the bootstrap, I was told to do an aclocal.

Anyway, I am still learning Linux .

I don't think the aclocal is needed I would do:

Code

make distclean
./bootstrap
./configure --enable-contrib
make
sudo make install # sudo only need if install system wide

I was told to run aclocal (I never run it before).

By the way, why do you have to be root to bootstrap and configure?  Is that do to the package building environment?

No, probaly just a mistake from my part .

Best wishes,
Michael

[TheTuxKeeper]

I was told to run aclocal (I never run it before).

./bootstrap is running aclocal, so I think either that it's not necessary to run it by your own

The real question is why weren't you doing this from start? Maybe I am paranoid but I have always been suspicious that autotool created build files will work after an update.  So I have figured you need to regenerate the build system after each update.

You don't trust autotools  :twisted:
Usually autotools does what it should, regenerate the build system if needed. But I think there are scenarios where autotools needs a manual regeneration of the build system. But I never had problems with autotools due to an outdated build system.

[Michael]

I was told to run aclocal (I never run it before).

./bootstrap is running aclocal, so I think either that it's not necessary to run it by your own

Hello,

Ok, I understand . Anyway, ./bootstrap asked me to run aclocal....so I did as it wanted..... :roll:

Best wishes,
Michael