Bug 11839 - Make Samba 4.4.2 on AIX 6100-09-06-1543 error
Summary: Make Samba 4.4.2 on AIX 6100-09-06-1543 error
Status: RESOLVED DUPLICATE of bug 11621
Alias: None
Product: Samba 4.1 and newer
Classification: Unclassified
Component: Build (show other bugs)
Version: 4.4.2
Hardware: PPC AIX
: P5 normal (vote)
Target Milestone: ---
Assignee: Samba QA Contact
QA Contact: Samba QA Contact
Depends on:
Reported: 2016-04-14 15:07 UTC by Rogerio Martini
Modified: 2016-04-15 16:12 UTC (History)
1 user (show)

See Also:

Configure log (2.54 MB, application/x-compress)
2016-04-14 15:07 UTC, Rogerio Martini
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Rogerio Martini 2016-04-14 15:07:41 UTC
Created attachment 11998 [details]
Configure log

Since Samba 4.1.x is deprecated, I tried building new version 4.4.2 to solve new security issues. But after run configure using this syntax bellow, make was failed like we see:

# ./configure --prefix=/usr/local/samba --check-c-compiler=xlc --without-ad-dc --without-ldap --without-ads


Checking configure summary                                                                      : ok
Checking compiler for PIE support                                                               : no
Checking compiler for full RELRO support                                                        : no
Checking if toolchain accepts -fstack-protector                                                 : no
'configure' finished successfully (2m45.646s)

# make


[ 477/3350] Compiling lib/util/util.c
"../lib/util/time.c", line 63.5: 1506-294 (S) Syntax error in expression on #if directive.
[ 478/3350] Compiling lib/util/idtree.c
[ 479/3350] Compiling lib/util/fault.c
[ 480/3350] Compiling lib/util/substitute.c
Waf: Leaving directory `/opt/tivit/samba-4.4.2/bin'
Build failed:  -> task failed (err #1):
        {task: cc time.c -> time_13.o}
make: 1254-004 The error code from the last command is 1.

Comment 1 Christian Ambach 2016-04-15 16:12:41 UTC

*** This bug has been marked as a duplicate of bug 11621 ***