From: Andrew Cagney <ac131313@redhat.com>
To: msarasa@fh-konstanz.de
Cc: gdb@sources.redhat.com
Subject: Re: ser-tcp ser-unix question
Date: Thu, 20 Mar 2003 00:14:00 -0000 [thread overview]
Message-ID: <3E7907DF.2070409@redhat.com> (raw)
In-Reply-To: <1048074199.3e7857d755845@webmail.fh-konstanz.de>
> 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?
Andrew
next prev parent reply other threads:[~2003-03-20 0:14 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-20 0:14 ` Andrew Cagney [this message]
2003-03-20 9:17 ` msarasa
2003-03-20 14:53 ` Andrew Cagney
2003-03-19 11:42 ` msarasa
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=3E7907DF.2070409@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=msarasa@fh-konstanz.de \
/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