On 1/24/21 11:06 PM, Tom Lane wrote:
> Noah Misch writes:
>> On Mon, Jan 18, 2021 at 09:29:53PM +0100, Fabien COELHO wrote:
>>> ... Last two months were a
>>> little overworked for me so I let slip quite a few things. If you want to
>>> disable the animal as Tom suggests, do as you want.
>> Perh
I've added an explicit LD_LIBRARY_PATH, which will be triggered at some
point later.
This seems to have fixed the issue.
I'm sorry for the noise and quite baffled anyway, because according to my
change logs it does not seem that I modified anything from my side about
the dynamic library pa
Hi,
On 2021-02-15 10:05:32 +0100, Fabien COELHO wrote:
> > show? What do you have in seawap's LD_LIBRARY_PATH, and is the
> > problem that you need to add /home/fabien/clgtk/lib to it
>
> Argh. Would it be so stupid? :-( I thought the configuration stuff would
> manage the link path automaticall
Hello Thomas,
Thanks for looking at this, I'm currently far behind on many things and
not very responsive:-(
Here is the creation of llvmjit.so:
g++ ... -o llvmjit.so ... -L/home/fabien/clgtk/lib ... -lLLVMOrcJIT ...
That'd be from llvm-config --ldflags or similar, from this binary:
check
On Sat, Dec 12, 2020 at 8:45 AM Fabien COELHO wrote:
> > +ERROR: could not load library
> > "/home/fabien/pg/build-farm-11/buildroot/HEAD/pgsql.build/tmp_install/home/fabien/pg/build-farm-11/buildroot/HEAD/inst/lib/postgresql/llvmjit.so":
> > libLLVMOrcJIT.so.12git: cannot open shared object fi
Noah Misch writes:
> On Mon, Jan 18, 2021 at 09:29:53PM +0100, Fabien COELHO wrote:
>> ... Last two months were a
>> little overworked for me so I let slip quite a few things. If you want to
>> disable the animal as Tom suggests, do as you want.
> Perhaps he was suggesting that you (buildfarm own
On Mon, Jan 18, 2021 at 09:29:53PM +0100, Fabien COELHO wrote:
> >>>The "no such file" error seems more like a machine local issue to me.
> >>
> >>I'll look into it when I have time, which make take some time. Hopefully
> >>over the holidays.
> >
> >This is still happening ... Any chance you can ha
Hello Alvaro,
The "no such file" error seems more like a machine local issue to me.
I'll look into it when I have time, which make take some time. Hopefully
over the holidays.
This is still happening ... Any chance you can have a look at it?
Indeed. I'll try to look (again) into it soon.
Alvaro Herrera writes:
> On 2020-Dec-11, Fabien COELHO wrote:
>> I'll look into it when I have time, which make take some time. Hopefully
>> over the holidays.
> This is still happening ... Any chance you can have a look at it?
If you don't have time to debug it, perhaps you could just disable
t
On 2020-Dec-11, Fabien COELHO wrote:
> > I hadn't checked that before, but for the last few days there's been a
> > different failure than the one I saw earlier:
> >
> > +ERROR: could not load library
> > "/home/fabien/pg/build-farm-11/buildroot/HEAD/pgsql.build/tmp_install/home/fabien/pg/build
Hello Andres,
I hadn't checked that before, but for the last few days there's been a
different failure than the one I saw earlier:
+ERROR: could not load library
"/home/fabien/pg/build-farm-11/buildroot/HEAD/pgsql.build/tmp_install/home/fabien/pg/build-farm-11/buildroot/HEAD/inst/lib/postgr
Hi,
On 2020-12-07 19:38:19 -0800, Andres Freund wrote:
> On 2020-12-01 12:08:10 -0800, Andres Freund wrote:
> > On 2020-12-01 21:04:44 +0100, Fabien COELHO wrote:
> > > Andres investigated a few days ago, managed to reproduce the issue
> > > locally,
> > > and has one line patch. I'm unsure if it
Hi,
On 2020-12-01 12:08:10 -0800, Andres Freund wrote:
> On 2020-12-01 21:04:44 +0100, Fabien COELHO wrote:
> > Andres investigated a few days ago, managed to reproduce the issue locally,
> > and has one line patch. I'm unsure if it should be prevently back-patched,
> > though.
>
> I see no reaso
Hi,
On 2020-12-01 21:04:44 +0100, Fabien COELHO wrote:
> Andres investigated a few days ago, managed to reproduce the issue locally,
> and has one line patch. I'm unsure if it should be prevently back-patched,
> though.
I see no reason not to backpatch - it's more correct for past versions
of LLV
Hello Thomas,
Since seawasp's bleeding edge LLVM installation moved to "trunk
20201114 c8f4e06b 12.0.0" ~16 days ago, it has been red. Further
updates didn't help it and it's now on "trunk 20201127 6ee22ca6
12.0.0". I wonder if there is something in Fabien's scripting that
needs to be tweaked
Hi,
On 2020-12-01 17:35:49 +1300, Thomas Munro wrote:
> Since seawasp's bleeding edge LLVM installation moved to "trunk
> 20201114 c8f4e06b 12.0.0" ~16 days ago, it has been red. Further
> updates didn't help it and it's now on "trunk 20201127 6ee22ca6
> 12.0.0". I wonder if there is something i
Hi
Since seawasp's bleeding edge LLVM installation moved to "trunk
20201114 c8f4e06b 12.0.0" ~16 days ago, it has been red. Further
updates didn't help it and it's now on "trunk 20201127 6ee22ca6
12.0.0". I wonder if there is something in Fabien's scripting that
needs to be tweaked, perhaps a sy
17 matches
Mail list logo
