Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: msarasa@fh-konstanz.de
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: ser-tcp ser-unix question
Date: Thu, 20 Mar 2003 09:17:00 -0000	[thread overview]
Message-ID: <1048151863.3e7987378659e@webmail.fh-konstanz.de> (raw)
In-Reply-To: <3E7907DF.2070409@redhat.com>

Quoting Andrew Cagney <ac131313@redhat.com>:

> > When i've made this , what should I do to build the gnu tools with the new
> 
> > file? I've tried to add ser-sim.c to configure.in (which is my file) in the
> 
> > line : SER_HARDWIRE = " ser-tcp.o ser-unix.o ser-pipe.o" , but eventhough I
> 
> > wrote SER_HARDWIRE = " ser-tcp.o ser-unix.o ser-pipe.o ser-sim.o",and then
> 
> > runned configure the makefile remains unaltered at this point(ser-sim.o , 
> > nowhere, the other yes). What I'm doing wrong? These ser-* files seems a 
> > little bit strange to me, because they're not included in any other file,
> so I 
> > thought that the only relation with the rest of gnu comes by the configure
> 
> > file. 
> 
> That should be all you need.  Perhaphs you need an _initialize_ser_xxx() 
> function to force linking of the file?


Thanks for your help & support!!
I've made this , and I have just one more problem that is:

I've made a new ser-sim.c file, actually It seems like ser-pipe.c but with 
empty functions for open/close and a _initialize.... function which is a copy 
from _initialize_ser_pipe() but that use the new empty sim_open() and 
sim_close.
I've made the gdb to obtain a ser-sim.o file.
I've changed the configure.in file to add this file where the other ser-** 
are. I ran configure , and I've obtained no ser-sim.o entry in the Makefile, 
where the other ser-*.o are. Not yet in init.c. 
But, when I've changed manually Makefile and added the ser-sim.o file where 
the other files are, I've got the desired init.c file , with the 
_initialize_ser_sim() function in its code. 

What should I do to make this clean from configure??

Thanks for the form!  I'll fill it 
Best regards, Miguel.



  reply	other threads:[~2003-03-20  9:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-18 16:18 msarasa
2003-03-18 16:53 ` Andrew Cagney
2003-03-19 11:42   ` msarasa
2003-03-19 11:42   ` msarasa
2003-03-20  0:14     ` Andrew Cagney
2003-03-20  9:17       ` msarasa [this message]
2003-03-20 14:53         ` Andrew Cagney

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1048151863.3e7987378659e@webmail.fh-konstanz.de \
    --to=msarasa@fh-konstanz.de \
    --cc=ac131313@redhat.com \
    --cc=gdb@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox