Make problem Mac OS X

Make problem Mac OS X

[Hans Aberg]

I got the problem below when installing guile-1.8.2 under Mac OS X  
10.4.10 PPC G4, gcc version
powerpc-apple-darwin8-gcc-4.0.1 (GCC) 4.0.1 (Apple Computer, Inc.  
build 5367). I have installed libtool-1.5.24 and gmp-4.2.2 (but  
should some environmental variables be set?). It says  
rl_pending_input is undeclared.

   Hans Aberg


/bin/sh ./libtool --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H  -I. - 
I. -I.. -I./..    -g -O2 -MT readline.lo -MD -MP -MF .deps/ 
readline.Tpo -c -o readline.lo readline.c
mkdir .libs
  gcc -DHAVE_CONFIG_H -I. -I. -I.. -I./.. -g -O2 -MT readline.lo -MD - 
MP -MF .deps/readline.Tpo -c readline.c  -fno-common -DPIC -o .libs/ 
readline.o
readline.c: In function ‘rl_cleanup_after_signal’:
readline.c:109: error: ‘rl_pending_input’ undeclared (first use in  
this function)
readline.c:109: error: (Each undeclared identifier is reported only once
readline.c:109: error: for each function it appears in.)
readline.c: In function ‘scm_init_readline’:
readline.c:562: warning: assignment from incompatible pointer type
make[4]: *** [readline.lo] Error 1
make[3]: *** [all-recursive] Error 1
make[2]: *** [all] Error 2
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2



_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile

Re: Make problem Mac OS X

[Ludovic Courtès]

Hi,

Hans Aberg <haberg@math.su.se> writes:

> readline.c: In function ‘rl_cleanup_after_signal’:
> readline.c:109: error: ‘rl_pending_input’ undeclared (first use in
> this function)

What version of GNU Readline do you have?

Here, it works fine with 5.2.

Thanks,
Ludovic.



_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile

Re: Make problem Mac OS X

[David Fang]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 798 bytes --]

> Hans Aberg <haberg@math.su.se> writes:
>
>> readline.c: In function ÿÿrl_cleanup_after_signalÿÿ:
>> readline.c:109: error: ÿÿrl_pending_inputÿÿ undeclared (first use in
>> this function)
>
> What version of GNU Readline do you have?
>
> Here, it works fine with 5.2.

Hi,
 	Also works with readline 5.0.  Note, however, that libreadline on 
Mac OS X in /usr/lib/libreadline.dylib is actually a symlink to libedit 
(BSD editline) which is missing that particular symbol, according to nm. 
(It's also missing from /usr/include/readline/readline.h.)
It's not a perfect substitute for GNU readline.

David Fang
Computer Systems Laboratory
Electrical & Computer Engineering
Cornell University
http://www.csl.cornell.edu/~fang/
 	-- (2400 baud? Netscape 3.0?? lynx??? No problem!)

[-- Attachment #2: Type: text/plain, Size: 137 bytes --]

_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile

Re: Make problem Mac OS X

[Ludovic Courtès]

Hi,

David Fang <fang@csl.cornell.edu> writes:

> It's not a perfect substitute for GNU readline.

Then I guess MacOS X users had better install the "real" GNU Readline.

Alternatively, we could detect whether `rl_pending_input' is available
at configure-time, and `#ifdef' the offending line of code.  However, I
don't know what impact it would have, and that would really be a crude
hack to work around the defects of Editline's compatibility layer, so
it's probably better to leave things as is.

Thanks,
Ludovic.



_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile

Re: Make problem Mac OS X

[Roger Mc Murtrie]

Ludovic wrote:
Then I guess MacOS X users had better install the "real" GNU Readline.  
Alternatively, we could detect whether `rl_pending_input' is available  
at configure-time, and `#ifdef' the offending line of code. However, I  
don't know what impact it would have, and that would really be a crude  
hack to work around the defects of Editline's compatibility layer, so  
it's probably better to leave things as is.
Thanks, Ludovic.

Perhaps, detect if `rl_pending_input' is available at configure-time.
If not, abort the configure with an appropriate message?
Regards
Roger

Re: Make problem Mac OS X

[Roger Mc Murtrie]

Hi Greg,
I've been using locate, find and grep to find missing bits and pieces.
Also the search function of Mac Finder windows (which doesn't seem to  
search all files)
On my machine
locate libltdl
produces
.
.
.
/usr/lib/libltdl.3.1.4.dylib
/usr/lib/libltdl.3.dylib
/usr/lib/libltdl.a
/usr/lib/libltdl.dylib
/usr/lib/libltdl.la

Perhaps for Debian you have to install it yourself. I think the   
libguile-ltdl is a separate thing.
Of course, to use libltdl.a you have to inclide -ltdl in your gcc link  
commands, usually by setting the environment variable before running  
configure:
LDFLAGS=-ltdl
export LDFLAGS
(Although for one package that I build, setting environment variables  
suggested by configure -help results in empty Makefiles!)
Googling libltdl leads to www.gnu.org/software/libtool. Looks like  
libltdl comes with GNU Libtool which I seem to remember having to  
install at some stage

I don't recall getting the  "you may need to run ldconfig". message,  
but I think I've had it from other installs in the past.
I never have found out how to use it. I think it comes from the loader  
and is really a message, perhaps, to gcc rather than humans.

I'm not much more than a "novice" myself, just stumble along with lots  
of trial and error.
Nowadays, package installation seems to involve one battle after  
another!

Good luck
Roger


On 11/01/2008, at 11:56 PM, Gregory Marton wrote:

> This is an ongoing problem -- now on Debian guile build complains of  
> not having libltdl even though 'sudo aptitude install libguile- 
> ltdl-1' claimed it was correctly installed.  How do I go about  
> finding where this libtdl has been put, and telling configure?
>
> Thanks for any help on this,
> Grem
>
>> Hi Roger,
>>
>> So I'm up against this problem now, and trying, as Ludovic  
>> suggests, to install the "real" GNU readline.  I downloaded,  
>> unpacked, configured, made, did sudo make install, and everything  
>> worked fine on my MacBook Pro running 10.4, but at the end it says  
>> "you may need to run ldconfig".  It appeared to install into /usr/ 
>> local/lib successfully.
>>
>> making in the guile directory still gives me this problem, as if it  
>> didn't notice.  Do you know what ldconfig this is of which it  
>> speaks, or how to run it?  Will it help guile recognize the one it  
>> wants?
>>
>> I'm a rank novice at all these things, sorry.
>>
>> Thanks,
>> Grem
>>
>> Roger Mc Murtrie whote on Wed, 09 Jan 2008 23:30:43 -0800
>>> Ludovic wrote:
>>> Then I guess MacOS X users had better install the "real" GNU  
>>> Readline. Alternatively, we could detect whether  
>>> `rl_pending_input' is available at configure-time, and `#ifdef'  
>>> the offending line of code. However, I don't know what impact it  
>>> would have, and that would really be a crude hack to work around  
>>> the defects of Editline's compatibility layer, so it's probably  
>>> better to leave things as is.
>>> Thanks, Ludovic.
>>> Perhaps, detect if `rl_pending_input' is available at configure- 
>>> time.
>>> If not, abort the configure with an appropriate message?
>>> Regards
>>> Roger
>>
>>
>>
>
> -- 
> ------ __@   Gregory A. Marton                http://csail.mit.edu/~gremio/
> --- _` 
> \<,_                                                                .
> -- (*)/ (*)          Quantum Physics: The dreams stuff is made of.
> ~~~~~~~~~~~~~~~~-~~~~~~~~_~~~_~~~~~v~~~~^^^^~~~~~--~~~~~~~~~~~~~~~+ 
> +~~~~~~~

Re: Make problem Mac OS X

[Roger Mc Murtrie]

Hi Greg

I could only get it to work by
./configure --enable-shared=no

Its often safer to use make distclean when and rerunning configure  
when trying to sort out these types of problems.

Now I comment "#undef HAVE_STAT64" in config.h.in to get rid of the  
off64_t problem.
This stops HAVE_STAT64 getting defined in config.h.

Regards
Roger

On 13/01/2008, at 1:51 AM, Gregory Marton wrote:

> Thanks Roger,
>
> In the ltdl case, it turned out I just needed to make clean for  
> configure's updates to take effect.  I'm still stumped on the mac  
> problem though -- readline and rl_pending_input, even with adding "- 
> L /usr/local/bin" to my CFLAGS.  Did you finally get that working?
>
> Thanks,
> Grem
>
>> Hi Greg,
>> I've been using locate, find and grep to find missing bits and  
>> pieces.
>> Also the search function of Mac Finder windows (which doesn't seem  
>> to search all files)
>> On my machine
>> locate libltdl
>> produces
>> .
>> .
>> .
>> /usr/lib/libltdl.3.1.4.dylib
>> /usr/lib/libltdl.3.dylib
>> /usr/lib/libltdl.a
>> /usr/lib/libltdl.dylib
>> /usr/lib/libltdl.la
>>
>> Perhaps for Debian you have to install it yourself. I think the  
>> libguile-ltdl is a separate thing.
>> Of course, to use libltdl.a you have to inclide -ltdl in your gcc  
>> link commands, usually by setting the environment variable before  
>> running configure:
>> LDFLAGS=-ltdl
>> export LDFLAGS
>> (Although for one package that I build, setting environment  
>> variables suggested by configure -help results in empty Makefiles!)
>> Googling libltdl leads to www.gnu.org/software/libtool. Looks like  
>> libltdl comes with GNU Libtool which I seem to remember having to  
>> install at some stage
>>
>> I don't recall getting the  "you may need to run ldconfig".  
>> message, but I think I've had it from other installs in the past.
>> I never have found out how to use it. I think it comes from the  
>> loader and is really a message, perhaps, to gcc rather than humans.
>>
>> I'm not much more than a "novice" myself, just stumble along with  
>> lots of trial and error.
>> Nowadays, package installation seems to involve one battle after  
>> another!
>>
>> Good luck
>> Roger
>>
>>
>> On 11/01/2008, at 11:56 PM, Gregory Marton wrote:
>>
>>> This is an ongoing problem -- now on Debian guile build complains  
>>> of not having libltdl even though 'sudo aptitude install libguile- 
>>> ltdl-1' claimed it was correctly installed.  How do I go about  
>>> finding where this libtdl has been put, and telling configure?
>>> Thanks for any help on this,
>>> Grem
>>>> Hi Roger,
>>>> So I'm up against this problem now, and trying, as Ludovic  
>>>> suggests, to install the "real" GNU readline.  I downloaded,  
>>>> unpacked, configured, made, did sudo make install, and everything  
>>>> worked fine on my MacBook Pro running 10.4, but at the end it  
>>>> says "you may need to run ldconfig".  It appeared to install  
>>>> into /usr/local/lib successfully.
>>>> making in the guile directory still gives me this problem, as if  
>>>> it didn't notice.  Do you know what ldconfig this is of which it  
>>>> speaks, or how to run it?  Will it help guile recognize the one  
>>>> it wants?
>>>> I'm a rank novice at all these things, sorry.
>>>> Thanks,
>>>> Grem
>>>> Roger Mc Murtrie whote on Wed, 09 Jan 2008 23:30:43 -0800
>>>>> Ludovic wrote:
>>>>> Then I guess MacOS X users had better install the "real" GNU  
>>>>> Readline. Alternatively, we could detect whether  
>>>>> `rl_pending_input' is available at configure-time, and `#ifdef'  
>>>>> the offending line of code. However, I don't know what impact it  
>>>>> would have, and that would really be a crude hack to work around  
>>>>> the defects of Editline's compatibility layer, so it's probably  
>>>>> better to leave things as is.
>>>>> Thanks, Ludovic.
>>>>> Perhaps, detect if `rl_pending_input' is available at configure- 
>>>>> time.
>>>>> If not, abort the configure with an appropriate message?
>>>>> Regards
>>>>> Roger
>>> -- 
>>> ------ __@   Gregory A. Marton                http://csail.mit.edu/~gremio/
>>> --- _` 
>>> \< 
>>> ,_                                                                .
>>> -- (*)/ (*)          Quantum Physics: The dreams stuff is made of.
>>> ~~~~~~~~~~~~~~~~-~~~~~~~~_~~~_~~~~~v~~~~^^^^~~~~~--~~~~~~~~~~~~~~~+ 
>>> +~~~~~~~
>>
>
> -- 
> ------ __@   Gregory A. Marton                http://csail.mit.edu/~gremio/
> --- _` 
> \<,_                                                                .
> -- (*)/ (*)         Prediction is hard, especially about the future.
> ~~~~~~~~~~~~~~~~-~~~~~~~~_~~~_~~~~~v~~~~^^^^~~~~~--~~~~~~~~~~~~~~~+ 
> +~~~~~~~

Re: Make problem Mac OS X

[Neil Jerram]

Roger Mc Murtrie <rogermc@iinet.net.au> writes:

> I think the libguile-ltdl is a separate thing.

Yes, libguile-ltdl was a tweaked version of libltdl that we used
during the 1.6.x series, while waiting for upstream to make a fix that
we needed.  It isn't needed anymore.

> On 11/01/2008, at 11:56 PM, Gregory Marton wrote:
>
>> This is an ongoing problem -- now on Debian guile build complains of
>> not having libltdl even though 'sudo aptitude install libguile-
>> ltdl-1' claimed it was correctly installed.  How do I go about
>> finding where this libtdl has been put, and telling configure?

For building Guile 1.8.x on Debian, you need the libltdlN-dev package,
where N is a number.  I am using Debian etch, and have libltdl3-dev.

>>>> Ludovic wrote:
>>>> Then I guess MacOS X users had better install the "real" GNU
>>>> Readline. Alternatively, we could detect whether
>>>> `rl_pending_input' is available at configure-time, and `#ifdef'

How do we test for a library variable (i.e. rl_pending_input) in
configure.in ?

>>>> Perhaps, detect if `rl_pending_input' is available at configure-
>>>> time.
>>>> If not, abort the configure with an appropriate message?
>>>> Regards
>>>> Roger

That sounds good to me, if we can detect it.

Regards,
     Neil