----------  Forwarded Message  ----------

Subject: samba-4.0.9 wont compile
Date: Wednesday 11 September 2013, 10:31:25
From: "lux-integ" <[email protected]>
To: LFS Support List <[email protected]>

Greetings,

I am trying to compile samba-4.0.9
( http://www.linuxfromscratch.org/blfs/view/svn/basicnet/samba.html ) as per 
the blfs instructions.
My computer has these:
--cpu amd64
--os blfs kernel-3.10.9,gcc-4.8.1, libtirpc-0.23 

when I run make ( or ./waf )  it ends like this:

#-----------------------------------------------------------
[ 491/2709] Compiling lib/param/util.c
../lib/param/loadparm.c:288:13: warning: 'visibility' attribute ignored [-
Wattributes]
      struct loadparm_service *sDefault) { \
             ^
../lib/param/param_functions.c:66:8: note: in expansion of macro 
'FN_LOCAL_STRING'
 static FN_LOCAL_STRING(_printername, szPrintername)
        ^
../lib/param/loadparm.c:288:13: warning: 'visibility' attribute ignored [-
Wattributes]
      struct loadparm_service *sDefault) { \
             ^
../lib/param/param_functions.c:78:8: note: in expansion of macro 
'FN_LOCAL_STRING'
 static FN_LOCAL_STRING(volume, volume)
        ^
[ 492/2709] Compiling dynconfig/dynconfig.c
../lib/param/loadparm.c: In function 'loadparm_init':
../lib/param/loadparm.c:2145:20: error: 'SAMBA_VERSION_STRING' undeclared 
(first use in this function)
        "Samba %s", SAMBA_VERSION_STRING);
                    ^
../lib/param/loadparm.c:2145:20: note: each undeclared identifier is reported 
only once for each function it appears in
[ 493/2709] Compiling lib/util/charset/iconv.c
Waf: Leaving directory `/home/linteg/samba-4.0.9/bin'
Build failed:  -> task failed (err #1): 
        {task: cc loadparm.c -> loadparm_7.o}
#-----------------------------------------------------------

help/advice would be appreciated


sincerely
luxInteg

-----------------------------------------
-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to