The Samba-Bugzilla – Bug 209
Build error on library bin/libsmbclient.a
Last modified: 2005-11-14 09:28:30 UTC
I am trying to build the SAMBA3.0.0Beta2 Solaris 9. Now the build looks
completes with one error, which is:
Compiling libads/kerberos.c with -fPIC
Linking libsmbclient non-shared library bin/libsmbclient.a
sh: ar: not found
*** Error code 1 (ignored)
Linking libsmbclient shared library bin/libsmbclient.so
Compiling modules/vfs_recycle.c with -fPIC
Building plugin bin/recycle.so
Compiling modules/vfs_audit.c with -fPIC
Building plugin bin/audit.so
Compiling modules/vfs_extd_audit.c with -fPIC
Building plugin bin/extd_audit.so
Compiling modules/vfs_netatalk.c with -fPIC
Building plugin bin/netatalk.so
Compiling modules/vfs_fake_perms.c with -fPIC
Building plugin bin/fake_perms.so
Then I try to package it and I get this:
# sh makepkg.sh
Assuming Samba distribution is rooted at /u01/XIP/Samba/samba-3.0.0beta2..
Could not find /u01/XIP/Samba/samba-3.0.0beta2/source/bin/make_smbcodepage to
Please create the binaries before packaging.
## Building pkgmap from package prototype file.
ERROR in prototype:
no object for <checkinstall> found in search path
no object for <docs/NT4_PlainPassword.reg> found in root directory
no object for <docs/Win95_PlainPassword.reg> found in root directory
no object for <docs/Win98_PlainPassword.reg> found in root directory
no object for <docs/Win2000_PlainPassword.reg> found in root directory
pkgmk: ERROR: unable to build pkgmap from prototype file
## Packaging was not successful.
The samba package is in /tmp
It looks like the make_smbcodepage never gets build. Is this because of the
error I got at build time?
Created attachment 46 [details]
The packaging problem is a separate problem which I have broken out in to bug 209.
One day I will learn to type properly. The packaging bug is bug 218.
Are you sure your development environment is installed properly? I just rebuilt
samba 3.0 CVS and had no trouble running ar on libsmbclient.a
sun1:/export/home/tpot/samba-3.0/source$ which ar
You are correct the development environment was incorrect. I can build it now.
OK, thanks for pointing out the packaging bug anyhow.
originally reported against 3.0.0beta2. CLeaning out
non-production release versions.