Обсуждение: Latest HEAD fails to build
Hi all,
After pulling the the latest commit -- e3d77ea6b4e425093db23be492f236896dd7b501, I am getting following error on compiling,
cp: cannot stat ‘./dynloader.h’: No such file or directory
Things were working fine till ac27c74def5d8544530b13d5901308a342f072ac atleast.
Anybody having a clue about that...
--
Regards,
Rafia Sabih
EnterpriseDB: http://www.enterprisedb.com/
> On 10 Sep 2018, at 11:22, Rafia Sabih <rafia.sabih@enterprisedb.com> wrote: > > Hi all, > > After pulling the the latest commit -- e3d77ea6b4e425093db23be492f236896dd7b501, I am getting following error on compiling, > cp: cannot stat ‘./dynloader.h’: No such file or directory > > Things were working fine till ac27c74def5d8544530b13d5901308a342f072ac atleast. > > Anybody having a clue about that… I ran into the same thing this morning. I think you have a leftover build artefact in src/include/dynloader.h from a build prior to it’s removal. Try to remove the file and make install again. cheers ./daniel
On Mon, Sep 10, 2018 at 2:56 PM, Daniel Gustafsson <daniel@yesql.se> wrote:
-- > On 10 Sep 2018, at 11:22, Rafia Sabih <rafia.sabih@enterprisedb.com> wrote:
>
> Hi all,
>
> After pulling the the latest commit -- e3d77ea6b4e425093db23be492f236896dd7b501, I am getting following error on compiling,
> cp: cannot stat ‘./dynloader.h’: No such file or directory
>
> Things were working fine till ac27c74def5d8544530b13d5901308a342f072ac atleast.
>
> Anybody having a clue about that…
I ran into the same thing this morning. I think you have a leftover build
artefact in src/include/dynloader.h from a build prior to it’s removal. Try to
remove the file and make install again.
Hi Daniel,
Thanks for the interest and help you offered. But I didn't quite get it, I tried maintaner-clean and distclean but it didn't work.
Regards,
Rafia Sabih
EnterpriseDB: http://www.enterprisedb.com/
> On 10 Sep 2018, at 11:35, Rafia Sabih <rafia.sabih@enterprisedb.com> wrote: > On Mon, Sep 10, 2018 at 2:56 PM, Daniel Gustafsson <daniel@yesql.se <mailto:daniel@yesql.se>> wrote: > > On 10 Sep 2018, at 11:22, Rafia Sabih <rafia.sabih@enterprisedb.com <mailto:rafia.sabih@enterprisedb.com>> wrote: > > > > Hi all, > > > > After pulling the the latest commit -- e3d77ea6b4e425093db23be492f236896dd7b501, I am getting following error on compiling, > > cp: cannot stat ‘./dynloader.h’: No such file or directory > > > > Things were working fine till ac27c74def5d8544530b13d5901308a342f072ac atleast. > > > > Anybody having a clue about that… > > I ran into the same thing this morning. I think you have a leftover build > artefact in src/include/dynloader.h from a build prior to it’s removal. Try to > remove the file and make install again. > > Hi Daniel, > > Thanks for the interest and help you offered. But I didn't quite get it, I tried maintaner-clean and distclean but it didn'twork. I believe it is because since 842cb9fa62fc995980 distclean and maintainer-clean don’t know about that file and thus won't try to remove it either (I can confirm that distclean didn’t work for me either). I’ve only skimmed the change though so I might be missing something. cheers ./daniel
Re: Rafia Sabih 2018-09-10 <CAOGQiiPQGgEvzPwScdZ6x3inb8RE8hfPXSrR6mXAB54EBJunYA@mail.gmail.com> > Thanks for the interest and help you offered. But I didn't quite get it, I > tried maintaner-clean and distclean but it didn't work. git clean -xdf Christoph
On Mon, Sep 10, 2018 at 4:10 PM, Christoph Berg <myon@debian.org> wrote:
Re: Rafia Sabih 2018-09-10 <CAOGQiiPQGgEvzPwScdZ6x3inb8RE8hfPXSrR6mXAB54EBJunYA@mail.gm ail.com>
> Thanks for the interest and help you offered. But I didn't quite get it, I
> tried maintaner-clean and distclean but it didn't work.
git clean -xdf
Thanks Christoph, it worked.
--
Regards,
Rafia Sabih
EnterpriseDB: http://www.enterprisedb.com/
Rafia Sabih <rafia.sabih@enterprisedb.com> writes: >>> I tried maintaner-clean and distclean but it didn't work. FWIW, my invariable habit is to do "make distclean" *before* git pull, not after. That avoids synchronization problems like this one, where the updated makefiles don't know about some build product that used to get made. maintainer-clean or "git clean -dfx" are less desirable options because they'll force you to redo the flex and bison runs, which are rather expensive. regards, tom lane