[RFC PR guile/21104] Fix GDB build failure with Guile 2.2

2018-01-21 Thread Doug Evans
Hi. This patch gets gdb building again with guile 2.2. Regression tested with guile 2.0.{13,14} and 2.2.3 on amd64-linux. [might also test with 2.2.{0,1,2}] I still need to at least add a NEWS item and update the docs as these Scheme functions are no longer present:

Re: Question: link to wrong library

2018-01-21 Thread Chaos Eternal
or try this LDFLAGS=-Wl,-rpath On Mon, Jan 22, 2018, 09:08 Nala Ginrut wrote: > I think you may need LD_LIBRARY_PATH > > 2018年1月21日 23:46,"陶青云" 写道: > >> Hi. I'm new to guile. I compiled it from source without `make install`. >> >> I write a simple

Re: Question: link to wrong library

2018-01-21 Thread Nala Ginrut
I think you may need LD_LIBRARY_PATH 2018年1月21日 23:46,"陶青云" 写道: > Hi. I'm new to guile. I compiled it from source without `make install`. > > I write a simple C file and use the flowing command to compile it. > `gcc -pthread -I. -L ./libguile/.libs -lguile-2.2 -lgc

Question: link to wrong library

2018-01-21 Thread 陶青云
Hi. I'm new to guile. I compiled it from source without `make install`. I write a simple C file and use the flowing command to compile it. `gcc -pthread -I. -L ./libguile/.libs -lguile-2.2 -lgc test.c` it successed. but the a.out is always link to my system guile library. $ ldd ./a.out

Re: Thread 1 "guile" received signal SIGPWR, Power fail/restart.

2018-01-21 Thread Eli Zaretskii
> From: Mark H Weaver > Date: Sat, 20 Jan 2018 23:45:54 -0500 > Cc: Guile Devel > > SIGPWR is used internally by libgc. If I recall correctly, it's done to > suspend all threads within their signal handlers before performing a > garbage collection. I

Re: Thread 1 "guile" received signal SIGPWR, Power fail/restart.

2018-01-21 Thread Amirouche Boubekki
On 2018-01-21 05:45, Mark H Weaver wrote: Amirouche Boubekki writes: I have a guile crash that I can reproduce all the time so far that says: Thread 1 "guile" received signal SIGPWR, Power fail/restart. SIGPWR is used internally by libgc. If I recall correctly,