Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

compiling rsync 2.3.1 on BSDI-4.0...

2 views
Skip to first unread message

Carlos M. Gutierrez

unread,
May 20, 1999, 3:00:00 AM5/20/99
to

I am trying to compile rsync 2.3.1 on a BSDI 4.0 machine with patches up
to just before 4.0.1.

I untarred the distribution,

% gunzip rsync-2.3.1.tar.gz
% tar xvf rsync-2.3.1.tar
% cd rsync-2.3.1
% ./configure

(long configure output, seems accurate for BSDI4.0)

% make

and eventually I get an error regarding 'ap_signal' in cleanup.o:

gcc -O -o rsync rsync.o generator.o receiver.o cleanup.o sender.o
exclude.o util.o main.o checksum.o match.o syscall.o log.o options.o flist.o io.o
compat.o hlink.o token.o uidlist.o socket.o fileio.o params.o loadparm.o
clientserver.o access.o connection.o authenticate.o lib/getopt.o lib/fnmatch.o lib/compat.o
lib/snprintf.o lib/mdfour.o zlib/deflate.o zlib/infblock.o zlib/infcodes.o
zlib/inffast.o zlib/inflate.o zlib/inftrees.o zlib/infutil.o zlib/trees.o
zlib/zutil.o zlib/adler32.o
cleanup.o: In function `_exit_cleanup':
cleanup.o(.text+0x1f): undefined reference to `ap_signal'
main.o: In function `main':
main.o(.text+0xf2b): undefined reference to `ap_signal'
main.o(.text+0xfdc): undefined reference to `ap_signal'
main.o(.text+0xfe8): undefined reference to `ap_signal'
main.o(.text+0xff4): undefined reference to `ap_signal'
main.o(.text+0x1000): more undefined references to `ap_signal' follow
*** Error code 1

Checking cleanup.c, I find no references to 'ap_signal'. Perhaps I am not
including some shared library?

If somebody has compiled this, and could drop me a clue I'll appreciate
it. Thanks!

Carlos M. Gutierrez
WEPA! Search Puerto Rico!
http://wepa.com/

--
To unsubscribe, send 'unsubscribe' to bsdi-user...@mailinglists.org
Archives of this list can be found at: http://www.nexial.com/mailinglists/

Tim Williams

unread,
May 20, 1999, 3:00:00 AM5/20/99
to
Howdy,

I have a Sendmail MX question. It's probably basic, but I am missing something.

Dedicated ISDN customer "foo.com" dials in and receives static IP address .100. They are
running an NT Exchange server and we are just sending them their mail to their server. For
this to work, we have the following setup. (It's not actually working, hence the note.:)

in the named/db.foo.com we have:
IN NS ns1.domain.com.
IN NS ns2.domain.com.

IN MX 02 mx1.foo.com.
IN MX 05 mx1.domain.com.
IN MX 10 mx2.domain.com.

IN A 211.111.111.5
www IN A 211.111.111.5
mail IN CNAME mx1
mx1 IN A 211.111.111.100

the /etc/named.conf file has a normal input, just like all the other hosted virtuals. Does
anyone have an idea what I could be missing, or maybe has the correct formula for what I'm
trying to achieve?

thanks a million,
tim

--
Tim Williams

William White

unread,
May 20, 1999, 3:00:00 AM5/20/99
to
You are missing the period(.) behind the mx


>mail IN CNAME mx1

should be

mail IN CNAME mx1.domain.com.

Alan Clegg

unread,
May 20, 1999, 3:00:00 AM5/20/99
to
> You are missing the period(.) behind the mx
>
>
> >mail IN CNAME mx1
>
> should be
>
> mail IN CNAME mx1.domain.com.

No, assuming that we are in the zone domain.com, that is assumed.

AlanC {noting to the list that the original poster never stated was was
actually failing}

Alan Clegg

unread,
May 20, 1999, 3:00:00 AM5/20/99
to
> > You are missing the period(.) behind the mx
> >
> >
> > >mail IN CNAME mx1
> >
> > should be
> >
> > mail IN CNAME mx1.domain.com.
>
> No, assuming that we are in the zone domain.com, that is assumed.

Note that I +should+ have said in the zone foo.com, and he is refering
back to mx1.foo.com, and not mx1.domain.com.

AlanC

Tim Williams

unread,
May 20, 1999, 3:00:00 AM5/20/99
to
Oops.
Thanks Alan,

With the configuration shown earlier in db.foo.com, I was getting "user
unknown" from mx1.domain.com. I then realized that I needed to take
foo.com
out of the /etc/mail/sendmail.cw file since I didn't want mx1.domain.com
to
get mail for foo.com. I removed that and then I'm getting a "relaying
denied" error when trying to send to any...@foo.com.

I tried fixing sendmail.cf by adding
# MX map (to allow relaying to hosts that we MX for)
Kmxserved bestmx -z /etc/mail/relay-domains

and then made /etc/mail/relay-domains and I put foo.com in that file.

Now It's bouncing between mx1.domain.com and mx2.domain.com until it
dies. (quits after 26 hops)


Thanks for your response.

tim
Alan Clegg wrote:

> > Howdy,
> >
> > I have a Sendmail MX question. It's probably basic, but I am missing
> > something.
>

> Um... what is not working? You've shown what appears to be an OK bind
> configuration file, but not stated what the error(s) are that you are
> seeing.
>
> AlanC

--
Tim Williams
Digital West Networks
t...@digitalwest.net
http://www.digitalwest.net
tel(805)781-9378 fax(805)781-9379 1(888)781-WEST

0 new messages