Bug 6871 - Problem compiling samba 4.0.0tp5
Summary: Problem compiling samba 4.0.0tp5
Status: RESOLVED INVALID
Alias: None
Product: Samba 4.0
Classification: Unclassified
Component: Build (show other bugs)
Version: unspecified
Hardware: x86 Linux
: P3 normal (vote)
Target Milestone: ---
Assignee: Jelmer Vernooij
QA Contact: samba4-qa@samba.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-04 12:21 UTC by Pierre
Modified: 2009-11-24 11:24 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Pierre 2009-11-04 12:21:23 UTC
# make proto
make: *** No rule to make target `proto'.  Stop.

# make          
Samba will be compiled with flags:
  CPP        = gcc -E
  CPPFLAGS   = -I./include -I. -I./lib -I./lib/replace -D_SAMBA_BUILD_=4 -DHAVE_CONFIG_H 
  CC         = gcc
  CFLAGS     = -s -O3 -march=i686 -I./include -I. -I./lib -I./lib/replace -D_SAMBA_BUILD_=4 -DHAVE_CONFIG_H 
  PICFLAG    = -fPIC
  LD         = gcc 
  LDFLAGS    = -Wl,--export-dynamic -L./bin/shared
  STLD       = /usr/local/bin/ar
  STLD_FLAGS = -rcs
  SHLD       = gcc
  SHLD_FLAGS = -shared -Wl,-Bsymbolic -L./bin/shared
  SHLIBEXT   = so
  srcdir     = .
  builddir   = .
  pwd        = /tmp/samba-4.0.0tp5/source
Linking bin/shared/libsamba-config.so.0.0.1
gcc: bin/static/libsamba-config.a: No such file or directory
make: *** [bin/shared/libsamba-config.so.0.0.1] Error 1
Comment 1 Matthias Dieter Wallnöfer 2009-11-04 13:02:06 UTC
To be able to handle the bug you should try the following:
1.) use the most recent release from SAMBA 4 you can get, since at the moment we don't support older builds (we've no stable release yet). This means: get either the unstable release alpha8, or (much better) check out our GIT repo (consider http://wiki.samba.org for instructions).
2.) Be also sure to try "make clean". Sometimes the build system doesn't rebuild older binaries or ignores removed files. If this didn't help delete your source folder, reextract from the archive or repo and restart the build from beginning (./autogen.sh; ./configure...). When using GIT instead of this you can apply the "git-clean -d -f -x ." command in the root repo dir to have GIT remove all binaries and autogenerated files for you. Also here restart from beginning.

If this all didn't help we start with the investigations.
Comment 2 Matthias Dieter Wallnöfer 2009-11-12 04:35:54 UTC
Does the problem still happen with newer versions? Otherwise I close this one.
Comment 3 Matthias Dieter Wallnöfer 2009-11-24 11:24:24 UTC
Closing with invalid unless we hear us again.