ah, that's the "compile" file to manually delete before ./autogen.sh etc.


Le 19/05/2014 19:53, Antoine Villeret a écrit :
same here,

deleting Makefile, Makefile.in, configure and re-run ./autogen.sh doesn't help

but cloning a fresh copy of repo and ./autogen.sh && ./configure && make works

weird...

+
a

--
do it yourself
http://antoine.villeret.free.fr


2014-05-19 19:42 GMT+02:00 Cyrille Henry <[email protected] 
<mailto:[email protected]>>:



    Le 14/05/2014 14:55, IOhannes m zmoelnig a écrit :

        -----BEGIN PGP SIGNED MESSAGE-----
        Hash: SHA256

        On 2014-05-13 13:25, Antoine Villeret wrote:

            hello,

            I got the same here with ubuntu 12.04 even if I do : ./configure
            --without-glew --without-glewmx


        did you run
        $ ./autogen.sh

        it seems like your Makefile's have not been udpated from Makefile.am
        (in theory this should happen automatically; but sometimes - esp. when
        you have also upgraded automake - this fails; ./autogen.sh forces the
        regeneration)

    yes, i did ./autogen.sh, then ./configure.sh, then make fail with :

    make[3]: entrant dans le répertoire « /home/chnry/pd/Gem/src/Gem »

    make[3]: *** Pas de règle pour fabriquer la cible « glew.cpp », nécessaire 
pour « libGem_la-glew.lo ». Arrêt.

    glew.cpp did not exist, but glew.c did.

    simlinking glew.c to glew.cpp and ./autogen.sh ; ./configure.sh; make did 
work.


    c



        fgmasdr
        IOhannes
        -----BEGIN PGP SIGNATURE-----
        Version: GnuPG v1
        Comment: Using GnuPG with Icedove - http://www.enigmail.net/

        iQIcBAEBCAAGBQJTc2evAAoJELZQGc__R/ejb4GBAP/__3h13ujnjXLc0m3mB7jffiam
        yhWFL1Ab4jQU5M5LD3+__A8ncxJH4oy393tfGa4oMGrMauuKI2c__HDJvg39z9dO6dny
        mU1sFTX3GQgN1IUR4MRoWd0Q5lJ1E2__05ZgOTS6bXFXFdsl10siFFI/__AVozgaFdZU
        CgQrNpF82B+__HPhN2FLABy7fmcIORNXh+__x8qDzwjfvY9YOLCxr+__fixD3XDWA7SOZP
        Zyty4BwtKuV6bBloFTjwhh2zcreZI8__cwRS/__Iawy42fjtqxKF2pTShgHjrsicNunb
        /APZ+__LPy5in6qp8BwyNfbT9sGraUCq+G/__0ndhAJvgetrYsMvvcFoOKeImSIEq8S__X
        nGK43Hs5ww364b72TjB59LuwZB+__HdZPSqQbYrhNMMAvL5TvVH2jHym/__eDPp7HJuJ
        6ce+__1HNHCoEzz2wmf2Zf87VwhzPiLIkgP9__xWNidXX/xEeYudlP/5uO3oE7iACjWd
        2kKtfORdXJSDg3oJb8kwkSSPGB5izo__36cM1VZGRmzMOKDQgf7+__v18ReyWMGAsCYz
        bv8/__bm49oFjvqTIUYZp9OFkKJmA4lBs6g8__BCj3yRFN/eBKLYYdU6E7TpojVmUNoZ
        BqYwvuT+wiD+__jX35ZtWg2SSHOHdzUSlMDjSb3wo/__t1ZDBARZ2Otv5Lh++pC7Kaes
        2ldjdg0VlvfPCpqXq5Vs
        =KftZ
        -----END PGP SIGNATURE-----



        _________________________________________________
        GEM-dev mailing list
        [email protected] <mailto:[email protected]>
        http://lists.puredata.info/__listinfo/gem-dev 
<http://lists.puredata.info/listinfo/gem-dev>


    _________________________________________________
    GEM-dev mailing list
    [email protected] <mailto:[email protected]>
    http://lists.puredata.info/__listinfo/gem-dev 
<http://lists.puredata.info/listinfo/gem-dev>




_______________________________________________
GEM-dev mailing list
[email protected]
http://lists.puredata.info/listinfo/gem-dev


_______________________________________________
GEM-dev mailing list
[email protected]
http://lists.puredata.info/listinfo/gem-dev

Reply via email to