cgdb-users

[Cgdb-users] compiling on OS X leopard

[Badi' Abdul-W. <ali...@gm...>]

Hi.
I'm trying to get cgdb compiled and installed on my Apple laptop  
running OS 10.5. I've tried compiling from source and using MacPorts.  
They both halt compiling on the same error (this is from the MacPort  
attempt):

[~/src/cvs-svn/cgdb]: port install cgdb
--->  Building cgdb with target all
Error: Target org.macports.build returned: shell command " cd "/opt/ 
local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_devel_cgdb/work/cgdb-0.6.4" && make all "  
returned error 2
Command output: make  all-recursive
Making all in lib
Making all in gdbmi
make  all-recursive
Making all in src
make[5]: Nothing to be done for `all'.
make[5]: Nothing to be done for `all-am'.
make[3]: Nothing to be done for `all-am'.
Making all in various
Making all in util
Making all in src
if gcc -DHAVE_CONFIG_H -I. -I. -I../../..   -I/opt/local/include - 
I./../include -O2 -MT pseudo.o -MD -MP -MF ".deps/pseudo.Tpo" -c -o  
pseudo.o pseudo.c; \
         then mv -f ".deps/pseudo.Tpo" ".deps/pseudo.Po"; else rm -f  
".deps/pseudo.Tpo"; exit 1; fi
pseudo.c: In function 'pty_open':
pseudo.c:338: error: 'I_PUSH' undeclared (first use in this function)
pseudo.c:338: error: (Each undeclared identifier is reported only once
pseudo.c:338: error: for each function it appears in.)
make[4]: *** [pseudo.o] Error 1
make[3]: *** [all-recursive] Error 1
make[2]: *** [all-recursive] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2

Does anyone have any idea as to what's going on? This seems to be  
specific to the apple os, since I compiled and installed on a linux  
box I have access to.

Thanks.

Re: [Cgdb-users] compiling on OS X leopard

[Bob R. <bob...@co...>]

On Thu, Nov 15, 2007 at 10:51:54AM -0800, Badi' Abdul-Wahid wrote:
> Hi.
> I'm trying to get cgdb compiled and installed on my Apple laptop  
> running OS 10.5. I've tried compiling from source and using MacPorts.  
> They both halt compiling on the same error (this is from the MacPort  
> attempt):

Hmmm, neosun had this compiling at some point. Have you seen the
mac os X link here:
http://cgdb.sourceforge.net/download.php

It has a binary which you can use, unless you are relying on trunk/ for
some reason.

> pseudo.c: In function 'pty_open':
> pseudo.c:338: error: 'I_PUSH' undeclared (first use in this function)
> pseudo.c:338: error: (Each undeclared identifier is reported only once
> pseudo.c:338: error: for each function it appears in.)

Hmm, this could be a problem. I didn't write this code, I borrowed it
from the ssh project. So, either autoconf screwed up, and brought you
down the wrong path in psuedo.c or pseudo.c needs to be modified to work
on the specific OS you are compiling for.

> Does anyone have any idea as to what's going on? This seems to be  
> specific to the apple os, since I compiled and installed on a linux  
> box I have access to.

Well, we would first need to know how to open a pty on mac os 10.5. Once
we figured that out, we can determine what's going wrong with psuedo.c.
Do you have a /dev/ptmx directory? How about /dev/ptc?

Thanks,
Bob Rossi

Re: [Cgdb-users] compiling on OS X leopard

[Badi' Abdul-W. <ali...@gm...>]

On Nov 15, 2007, at 11:08 AM, Bob Rossi wrote:
> Hmmm, neosun had this compiling at some point. Have you seen the
> mac os X link here:
> http://cgdb.sourceforge.net/download.php
>
> It has a binary which you can use, unless you are relying on trunk/  
> for
> some reason.

I did see that. I'm trying to compile from source because I want  
tighter control over what I put on my computer, and (mainly) for the  
learning experience. I'm a bit new to using the *nixes and variants.


On Nov 15, 2007, at 11:08 AM, Bob Rossi wrote:
>> Does anyone have any idea as to what's going on? This seems to be
>> specific to the apple os, since I compiled and installed on a linux
>> box I have access to.
>
> Well, we would first need to know how to open a pty on mac os 10.5.  
> Once
> we figured that out, we can determine what's going wrong with  
> psuedo.c.
> Do you have a /dev/ptmx directory? How about /dev/ptc?

I do have a /dev/ptmx:
badi@eru [~/src/cvs-svn/cgdb]: file /dev/ptmx
/dev/ptmx: character special (15/2)

On Nov 15, 2007, at 11:58 AM, Bob Rossi wrote:
> Hi Badi,
>
> If I import the newest release of psuedo.c, will you test?

Sure.

btw, I wonder if this could have something to do with readline. I was  
having difficulty getting readling5.2 to build. I ended up changing  
the support/shobj-conf in the readline source directory to allow for  
darwin9 (leopard). The only changes I made were:
145:	darwin8*)									<----->	darwin9*)
and
156:	SHOBJ_LDFLAGS='-undefined dynamic_lookup' <----> 	SHOBJ_LDFLAGS='- 
undefined dynamic_lookup -dynamiclib'

Heres the link to my discovery on how to accomplish that:
http://forums.macosxhints.com/showthread.php?p=421408

Re: [Cgdb-users] compiling on OS X leopard

[Horst S. <sch...@us...>]

On Thu, 15 Nov 2007, Bob Rossi wrote:
> Well, we would first need to know how to open a pty on mac os 10.5. Once
> we figured that out, we can determine what's going wrong with psuedo.c.
> Do you have a /dev/ptmx directory? How about /dev/ptc?

I suggest looking at the location you borrowed that code from in the
first place, maybe they already have a solution that works for Leopard
(MacOS 10.5). As Cgdb builds fine on 10.4 here, it's very possible that
this is a 10.5 only issue.

(MacOS 10.4.11)
$ sudo port install cgdb
Password:
--->  Fetching cgdb
--->  Attempting to fetch cgdb-0.6.4.tar.gz from
http://downloads.sourceforge.net/cgdb
--->  Verifying checksum(s) for cgdb
--->  Extracting cgdb
--->  Configuring cgdb
--->  Building cgdb with target all
--->  Staging cgdb into destroot
--->  Installing cgdb 0.6.4_0
--->  Activating cgdb 0.6.4_0
--->  Cleaning cgdb
$

Kind regards,
 Horst

-- 
PGP-Key 0xD40E0E7A

Re: [Cgdb-users] compiling on OS X leopard

[Bob R. <bob...@co...>]

On Thu, Nov 15, 2007 at 08:50:35PM +0100, Horst Schirmeier wrote:
> On Thu, 15 Nov 2007, Bob Rossi wrote:
> > Well, we would first need to know how to open a pty on mac os 10.5. Once
> > we figured that out, we can determine what's going wrong with psuedo.c.
> > Do you have a /dev/ptmx directory? How about /dev/ptc?
> 
> I suggest looking at the location you borrowed that code from in the
> first place, maybe they already have a solution that works for Leopard
> (MacOS 10.5). 

Hi Badi,

If I import the newest release of psuedo.c, will you test?

Thanks,
Bob Rossi

Re: [Cgdb-users] compiling on OS X leopard

[Bob R. <bob...@co...>]

On Thu, Nov 15, 2007 at 08:50:35PM +0100, Horst Schirmeier wrote:
> On Thu, 15 Nov 2007, Bob Rossi wrote:
> > Well, we would first need to know how to open a pty on mac os 10.5. Once
> > we figured that out, we can determine what's going wrong with psuedo.c.
> > Do you have a /dev/ptmx directory? How about /dev/ptc?
> 
> I suggest looking at the location you borrowed that code from in the
> first place, maybe they already have a solution that works for Leopard
> (MacOS 10.5). As Cgdb builds fine on 10.4 here, it's very possible that
> this is a 10.5 only issue.
> 
> (MacOS 10.4.11)
> $ sudo port install cgdb
> Password:
> --->  Fetching cgdb
> --->  Attempting to fetch cgdb-0.6.4.tar.gz from
> http://downloads.sourceforge.net/cgdb
> --->  Verifying checksum(s) for cgdb
> --->  Extracting cgdb
> --->  Configuring cgdb
> --->  Building cgdb with target all
> --->  Staging cgdb into destroot
> --->  Installing cgdb 0.6.4_0
> --->  Activating cgdb 0.6.4_0
> --->  Cleaning cgdb

Great to see that it works on 10.4. Is it possible that you could send
us the translation unit for pseudo.c? That way, we could compare the
two examples. If you can set the CFLAGS, add -save-temps, then after the
build, psuedo.i should be left around by the compiler.

Thanks,
Bob Rossi

Re: [Cgdb-users] compiling on OS X leopard

[Horst S. <sch...@us...>]

On Thu, 15 Nov 2007, Bob Rossi wrote:
> On Thu, Nov 15, 2007 at 08:50:35PM +0100, Horst Schirmeier wrote:
> > On Thu, 15 Nov 2007, Bob Rossi wrote:
> > > Well, we would first need to know how to open a pty on mac os 10.5. Once
> > > we figured that out, we can determine what's going wrong with psuedo.c.
> > > Do you have a /dev/ptmx directory? How about /dev/ptc?
> > 
> > I suggest looking at the location you borrowed that code from in the
> > first place, maybe they already have a solution that works for Leopard
> > (MacOS 10.5). As Cgdb builds fine on 10.4 here, it's very possible that
> > this is a 10.5 only issue.
> > 
> > (MacOS 10.4.11)
> > $ sudo port install cgdb
> > Password:
> > --->  Fetching cgdb
> > --->  Attempting to fetch cgdb-0.6.4.tar.gz from
> > http://downloads.sourceforge.net/cgdb
> > --->  Verifying checksum(s) for cgdb
> > --->  Extracting cgdb
> > --->  Configuring cgdb
> > --->  Building cgdb with target all
> > --->  Staging cgdb into destroot
> > --->  Installing cgdb 0.6.4_0
> > --->  Activating cgdb 0.6.4_0
> > --->  Cleaning cgdb
> 
> Great to see that it works on 10.4. Is it possible that you could send
> us the translation unit for pseudo.c? That way, we could compare the
> two examples. If you can set the CFLAGS, add -save-temps, then after the
> build, psuedo.i should be left around by the compiler.

Sorry, I totally forgot about this request. Is it still an open issue?

-Horst

-- 
PGP-Key 0xD40E0E7A

Re: [Cgdb-users] compiling on OS X leopard

[Badi' Abdul-W. <ali...@gm...>]

On May 21, 2008, at 1:23 AM, Horst Schirmeier wrote:

> Sorry, I totally forgot about this request. Is it still an open issue?

Yes and no:
Yes: it still has the same problem compiling.
No: well, it was never really a high priority task for me to to get  
working. I was trying out a lo of different tools at the time. I'll  
probably take another stab (or several) at it once school lets out for  
the summer and post my results.

Thanks for the feedback though. :)

B.A.