My Travis builds get link errors and I don't know why

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

My Travis builds get link errors and I don't know why

Paul Licameli
My branch track-panel-refactor fails to build on Travis, with link errors.

This branch adds many new source files and changes src/Makefile.am.

My previous experience is that it is enough to edit Makefile.am when I add files.

Is this no longer so?  Did something change in Travis builds so that the generation of Makefile.in is not part of the build?

I do not have the means to edit Makefile.in myself.

Your humble Release Manager needs to stop putting off his education in doing Linux builds for himself.

PRL


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
audacity-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: My Travis builds get link errors and I don't know why

James Crook
In .travis.yml you could try reinstating:

 script:
     - aclocal --install -I m4 && automake && ./configure && make


Which I replaced by:

script:
    -  time ./configure && time make -j2


to get a faster build.
Or you could do automake locally on your machine, and push the results to GitHub and not modify the .yml file.

And no, I don't understand this stuff either.

--James.




On 5/23/2017 7:37 PM, Paul Licameli wrote:
My branch track-panel-refactor fails to build on Travis, with link errors.

This branch adds many new source files and changes src/Makefile.am.

My previous experience is that it is enough to edit Makefile.am when I add
files.

Is this no longer so?  Did something change in Travis builds so that the
generation of Makefile.in is not part of the build?

I do not have the means to edit Makefile.in myself.

Your humble Release Manager needs to stop putting off his education in
doing Linux builds for himself.

PRL



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot


_______________________________________________
audacity-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-devel



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
audacity-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: My Travis builds get link errors and I don't know why

Stevethefiddle
In reply to this post by Paul Licameli
On 23 May 2017 at 19:37, Paul Licameli <[hidden email]> wrote:
> My branch track-panel-refactor fails to build on Travis, with link errors.
>
> This branch adds many new source files and changes src/Makefile.am.
>
> My previous experience is that it is enough to edit Makefile.am when I add
> files.

You need to run automake after adding new files to the Makefile.am
Previously that was run on each build but has since been removed from
the Travis build script.

This will probably do it:

aclocal --install -I m4 && automake

You should then push to GitHub again (after checking that it builds)
so that everyone gets the newly generated makefile.in files.

Then run ./configure and make in the normal  way.

Steve

>
> Is this no longer so?  Did something change in Travis builds so that the
> generation of Makefile.in is not part of the build?
>
> I do not have the means to edit Makefile.in myself.
>
> Your humble Release Manager needs to stop putting off his education in doing
> Linux builds for himself.
>
> PRL
>

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
audacity-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: My Travis builds get link errors and I don't know why

Darrell Walisser
In reply to this post by Paul Licameli


On Tue, May 23, 2017 at 2:37 PM, Paul Licameli <[hidden email]> wrote:
My branch track-panel-refactor fails to build on Travis, with link errors.


​I've been seeing this also when merging lately, also in my local builds. My particular problem appears to be that my libtool version is 2.4.6 and Travis is still on 2.4.2.

For the moment, I found a forced autoreconf seems to guarantee the generated files are in sync. I didn't find the magical combination of aclocal and friends, the ones mentioned thus far didn't work for me.

autoreconf --no-recursive --install --force

The --no-recursive part keeps it out of lib-src where there isn't a problem.

​Note you will have to add "autopoint" package to get this command in Travis.​

​Sample config from my crosscompile branch:​


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
audacity-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-devel
Loading...