Re: can't build a gettext package

2005-01-17 Thread Kris Kennaway
On Mon, Jan 17, 2005 at 11:57:25AM -0500, daniel quinn wrote:
 i've managed to build packages for everything else on the system, and gettext 
 seems to compile and install just fine, but for some reason, building the 
 package fails:
 
   ===  Building package for gettext-0.14.1
   Creating package /usr/ports/packages/All/gettext-0.14.1.tbz
   Registering depends: libiconv-1.9.2_1.
   Creating bzip'd tar ball in '/usr/ports/packages/All/gettext-0.14.1.tbz'
   tar: include/autosprintf.h: Could not stat: No such file or directory
   tar: lib/libasprintf.a: Could not stat: No such file or directory
   tar: lib/libasprintf.so: Could not stat: No such file or directory
   tar: lib/libasprintf.so.0: Could not stat: No such file or directory
   tar: share/doc/libasprintf/autosprintf.html: Could not stat: No such file or
   directory 
   pkg_create: make_dist: tar command failed with code 256
   *** Error code 1
 
 now i understand what the error means, what i don't understand is why the 
 error exists in the first place.  if these files aren't created with the 
 initial make, why is the packager trying to include them?  and how do i fix 
 this?

Those files are expected to be installed when the package is built on
FreeBSD.  Since your system didn't build them, there must be something
different about it.  You could check the output of the configure and
build scripts to find out why, or just use a precompiled package from
the FTP site if you don't care this much.

Kris



pgp0FsBPLlApu.pgp
Description: PGP signature


Re: can't build a gettext package

2005-01-17 Thread daniel quinn
On January 17, 2005 06:16 pm, Kris Kennaway wrote:
 Those files are expected to be installed when the package is built on
 FreeBSD.  Since your system didn't build them, there must be something
 different about it.  You could check the output of the configure and
 build scripts to find out why, or just use a precompiled package from
 the FTP site if you don't care this much.

there's not much different with this machine when compared to a default 
install other than the make.conf file, which i've been experimenting with.  
maybe i've gibbled something in there?:

  CC=gcc
  CXX=g++
  CPUTYPE?=p3
  CFLAGS+= -O2 -pipe
  CXXFLAGS+= -fmemoize-lookups -fsave-memoized
  NO_BLUETOOTH=   true# do not build Bluetooth related stuff
  NO_USB= true# do not build usbd(8) and related programs
  #
  # these were in there as defaults:
  #
  PERL_VER=5.8.5
  PERL_VERSION=5.8.5
  PERL_ARCH=mach
  NOPERL=yo
  NO_PERL=yo
  NO_PERL_WRAPPER=yo



-- 
to be upset over what you don't have... is to waste what you do have.
  - ken keyes jr.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: can't build a gettext package

2005-01-17 Thread Kris Kennaway
On Mon, Jan 17, 2005 at 06:57:23PM -0500, daniel quinn wrote:
 On January 17, 2005 06:16 pm, Kris Kennaway wrote:
  Those files are expected to be installed when the package is built on
  FreeBSD.  Since your system didn't build them, there must be something
  different about it.  You could check the output of the configure and
  build scripts to find out why, or just use a precompiled package from
  the FTP site if you don't care this much.
 
 there's not much different with this machine when compared to a default 
 install other than the make.conf file, which i've been experimenting with.  
 maybe i've gibbled something in there?:
 
   CC=gcc
   CXX=g++
   CPUTYPE?=p3
   CFLAGS+= -O2 -pipe

You definitely don't want this if you're on 4.x.

   CXXFLAGS+= -fmemoize-lookups -fsave-memoized

You probably don't want this.

Kris


pgpMj0x4BDuUA.pgp
Description: PGP signature


Re: can't build a gettext package

2005-01-17 Thread daniel quinn
On January 17, 2005 07:43 pm, Kris Kennaway wrote:
 On Mon, Jan 17, 2005 at 06:57:23PM -0500, daniel quinn wrote:
  On January 17, 2005 06:16 pm, Kris Kennaway wrote:
   Those files are expected to be installed when the package is built on
   FreeBSD.  Since your system didn't build them, there must be something
   different about it.  You could check the output of the configure and
   build scripts to find out why, or just use a precompiled package from
   the FTP site if you don't care this much.
 
  there's not much different with this machine when compared to a default
  install other than the make.conf file, which i've been experimenting
  with. maybe i've gibbled something in there?:
 
CC=gcc
CXX=g++
CPUTYPE?=p3
CFLAGS+= -O2 -pipe

 You definitely don't want this if you're on 4.x.

i'm running 5.3-RELEASE.  is this still not ok?

CXXFLAGS+= -fmemoize-lookups -fsave-memoized

 You probably don't want this.

k thanks.

-- 
the more law and order are made prominent,
the more thieves and robbers there will be.
  - lao-tsu
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: can't build a gettext package

2005-01-17 Thread Kris Kennaway
On Mon, Jan 17, 2005 at 08:00:35PM -0500, daniel quinn wrote:
 On January 17, 2005 07:43 pm, Kris Kennaway wrote:
  On Mon, Jan 17, 2005 at 06:57:23PM -0500, daniel quinn wrote:
   On January 17, 2005 06:16 pm, Kris Kennaway wrote:
Those files are expected to be installed when the package is built on
FreeBSD.  Since your system didn't build them, there must be something
different about it.  You could check the output of the configure and
build scripts to find out why, or just use a precompiled package from
the FTP site if you don't care this much.
  
   there's not much different with this machine when compared to a default
   install other than the make.conf file, which i've been experimenting
   with. maybe i've gibbled something in there?:
  
 CC=gcc
 CXX=g++
 CPUTYPE?=p3
 CFLAGS+= -O2 -pipe
 
  You definitely don't want this if you're on 4.x.
 
 i'm running 5.3-RELEASE.  is this still not ok?

Yes, in fact.  Use the default setting.  5.3-STABLE uses -O2 -pipe
-fno-strict-alias (the latter is important), but I'm not certain this
will work on 5.3-RELEASE.

Kris


pgpwGTfoK1TXx.pgp
Description: PGP signature