Merit Network
Can't find what you're looking for? Search the Mail Archives.
  About Merit   Services   Network   Resources & Support   Network Research   News   Events   Home

Discussion Communities: Merit Network Email List Archives

IRRd-Discuss


Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: Could not compile

  • From: Kuniaki Kondo
  • Date: Thu Dec 24 20:55:57 1998

Craig;

From: Craig Labovitz <labovit@merit.edu>
Subject: Re: Could not compile 
Date: Thu, 24 Dec 1998 10:36:55 -0500

> 
> In our own testing, we generally don't do "make installs". I guess we never 
> tested this...

  At least, next time, I hope, when you release the IRRd, it was 
  already tested "make" on FreeBSD (because there is freebsd user.) and 
  "make install".

> 
> I've fixed the Makefiles so that this will work, and I'll put out a new source 
> code snapshot at the end of the day today.

  I'm going to wait this release. :-)

  And, I have a request. I'd like to include the irrd_cacher to the
  IRRd package, because I guess it usually want for IRRd users.
  What do you think about this?

---
Kuniaki Kondo
kuniaki@iij.ad.jp
Internet Initiative Japan Inc.

> 
> - Craig
> 
> 
> 
> at Thu, 24 Dec 1998 10:47:33 +0900, you wrote:
> > Craig;
> > 
> > Thank you for new version.
> > 
> > I compleated compile normally.
> > 
> > Also, when I had exec 'make install', it makes some errors.
> > Because, 'programs/hdr_comm/Makefile' and 'programs/irrd_ops/Makefiles'
> > don't have install section, and 'programs/irr_check/Makefiles' and
> > 'programs/notify/Makefiles' were comment-outed install section.
> > 
> > Is it true?
> > 
> > Thank you.
> > 
> > ---
> > Kuniaki Kondo
> > kuniaki@iij.ad.jp
> > Internet Initiative Japan Inc.
> > 
> > 
> > From: Craig Labovitz <labovit@merit.edu>
> > Subject: Re: Could not compile 
> > Date: Tue, 22 Dec 1998 15:32:41 -0500
> > 
> > > 
> > > Hi Kuniaki,
> > > 
> > > Our main development environment is Solaris, and we are sometimes tardy in 
> > > building/testing on all the other Unix varients. Sorry...
> > > 
> > > I placed a new source code version at
> > >   ftp://www.irrd.net/radb/irrd/source/irrd-v1.1.1-Dec-22-1998.tar.gz
> > > 
> > > I built and tested this version on FreeBSD-2.2.7. I did fairly minimal 
> > > testing, though...
> > > 
> > > Please keep in mind that this is still an early beta (really an alpha) 
> > > release. We are using the code on Solaris, but we HAVE NOT done much testin
> g 
> > > on other platforms.
> > > 
> > > We have also updated the IRRd manual. See
> > >   http://www.irrd.net/irrd.pdf
> > > 
> > > Cheers.
> > > 
> > > - Craig
> > > 
> > > at Mon, 21 Dec 1998 19:17:50 +0900, you wrote:
> > > > Hello;
> > > > 
> > > > I tried compile IRRd 1.1 on FreeBSD-2.2.7.
> > > > However, This made complie errors....
> > > > 
> > > > Following..
> > > > --
> > > > main.c:190: warning: data definition has no type or storage class
> > > > Linking: gcc -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -L/usr/local/lib lex
> .yy.
> > > o ripe181.tab.o irr_attrs.o prefix.o util.o syntax_attrs.o canonical.o hdr_
> buil
> > > d.o main.o -lsocket -lnsl -o irr_check -L../hdr_comm -lhdrs
> > > > ld: -lsocket: no match
> > > > *** Error code 1
> > > > 
> > > > Stop.
> > > > *** Error code 1
> > > > 
> > > > Stop.
> > > > *** Error code 1
> > > > 
> > > > Stop.
> > > > ---
> > > > 
> > > >  This messages happend in irr_check section.
> > > >  Please advice..
> > > > 
> > > > thank you
> > > > ---
> > > > Kuniaki Kondo
> > > > kuniaki@iij.ad.jp
> > > > Internet Initiative Japan Inc.
> > > 
> > > -- 
> > > Craig Labovitz				labovit@merit.edu
> > > Merit Network, Inc.			http://www.merit.edu/~labovit
> > > 4251 Plymouth  Road, Suite C.		(734) 764-0252 (office)
> > > Ann Arbor, MI 48105-2785		(734) 647-3185 (fax)
> > > 
> > > 
> > > 
> 
> -- 
> Craig Labovitz				labovit@merit.edu
> Merit Network, Inc.			http://www.merit.edu/~labovit
> 4251 Plymouth  Road, Suite C.		(734) 764-0252 (office)
> Ann Arbor, MI 48105-2785		(734) 647-3185 (fax)
> 
> 
> 


[an error occurred while processing this directive]