Sponsored Content
Top Forums UNIX for Advanced & Expert Users Compiling Samba from Source on AIX, Active Directory, LDAP, Kerberos Post 302389528 by raidzero on Monday 25th of January 2010 07:45:37 AM
Old 01-25-2010
Thanks for the reply. I am using gcc, I am not sure what makefile I am using, whichever the default one is that the configure script produces? I am not that familiar with the logistics of compiling from source, general make and configure errors I can deal with (typically missing/incorrect dependencies) but this I am unsure of. How do I determine the Makefile?
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

LDAP request from unix into Active Directory

Hi all, I experienced a problem when making a LDAP search from Unix Netscape or Unix Mozilla adressbooks into my Active Directory LDAP db for email addresses. I add my Domain Controller hostname and the LDAP root dir to search in. For example: Name: AD LDAP server: gullvi Search Root:... (0 Replies)
Discussion started by: tonlu
0 Replies

2. AIX

Compiling samba from source in AIX 5.3

Hello all. I have never had any issues like this when compiling applications from source. When I try to compile samba-3.5.0pre2, configure runs with no issues, but when the time comes to make, this happens: make: make 1254-025 There must be an existing description file or specify a target. ... (4 Replies)
Discussion started by: raidzero
4 Replies

3. Red Hat

ldap and active directory

Hi Friends, I need your help to get some solution of one of my problem. Ours is a mixed domain. Most of the servers are windows and very little linux servers. We are using the MS AD for authentication. My problem is, I want to authenticate linux servers against AD. I donot want to use any... (1 Reply)
Discussion started by: arumon
1 Replies

4. Solaris

LDAP Problem during Kerberos setting for Win server 03 Active Directory

Hi, FYI, I'm new in Solaris I'm trying to use Kerberos on authenticating LDAP Client with the Active Directory on Windows Server 2003 on both Solaris 10 5/08 and Solaris 10 9/10 by referring to the pdf file kerberos_s10.pdf available at sun official site. ... (0 Replies)
Discussion started by: chongzh
0 Replies

5. AIX

Trouble with Kerberos/LDAP and AIX 6.1

The KRB5ALDAP compound load module is giving me fits. Everything looks like it should be working, but no. Goal: Integrate AIX host with Active Directory using a KRB5ALDAP compound load module so that users can be created in AD and used in AIX, with unix attributes (registry values) being... (2 Replies)
Discussion started by: jgeiger
2 Replies

6. HP-UX

HP-UX SSH and Active Directory Kerberos with Samba

The situation: i have a AD server with samba4,all clients ssh-kerberos works fine,except hpux :p wich works only for few days..then i must re-export(sic!) the keys with samba-tool domain exportkeytab 11.keytab --principal=host/hpux.fqdn Why after few days ssh return error "server not found... (1 Reply)
Discussion started by: Linusolaradm1
1 Replies

7. AIX

Samba 3.6.22 on AIX 7.1 with Windows AD (Kerberos and winbind)

Hi all, I have installed samba 3.6.22 on AIX 7.1 and join a windows AD with success. All seem to work fine, I have configured smb.conf, methods.cfg, kerberos, user .... the following command work fine wbinfo -u, wbinfo -g, wbinfo -i, wbinfo -s, wbinfo -S, lsuser, id... The unique... (20 Replies)
Discussion started by: PhilippeA
20 Replies

8. UNIX for Beginners Questions & Answers

Active Directory OR LDAP

Hi, How can we check users added through LDAP or AD. Users added through a group of AD or LDAP group. (2 Replies)
Discussion started by: Nishit
2 Replies

9. AIX

AIX 7.1 - Samba 4 File Shares and Integration with Active Directory Issues

Hi. Ive recently upgraded Samba on an AIX server to Samba 4. The aim is to allow a specific group of Windows AD users to access some AIX file shares (with no requirement to enter passwords) - using AD to authenticate. Currently I have: Samba 4 installed ( and 3 daemons running) Installed... (1 Reply)
Discussion started by: linuxsnake
1 Replies

10. AIX

Samba 3.6 on AIX 7.1 - Windows 10 Access to AIX file shares using Active Directory authentication

I am running AIX 7.1 and currently we have samba 3.6.25 installed on the server. As it stands some AIX folders are shared that can be accessed by certain Windows users. The problem is that since Windows 10 the guest feature no longer works so users have to manually type in their Windows login/pwd... (14 Replies)
Discussion started by: linuxsnake
14 Replies
AUTOMAKE(1)						      General Commands Manual						       AUTOMAKE(1)

NAME
automake - automatically create Makefile.in's from Makefile.am's SYNOPSIS
automake [ -a | --add-missing ] [ --amdir=DIR ] [ --build-dir=DIR ] [ -c | --copy ] [ --cygnus ] [ -f | --force-missing ] [ --foreign ] [ --gnits ] [ --gnu ] [ --help ] [ -i | --ignore-deps ] [ --include-deps ] [ --no-force ] [ -o DIR ] [ --output-dir=DIR ] [ --srcdir-name=DIR ] [ -v | --verbose ] [ --version ] [ --Werror | --Wno-error ] DESCRIPTION
To create all the Makefile.ins for a package, run the automake program in the top level directory, with no arguments. automake will auto- matically find each appropriate Makefile.am (by scanning configure.in) and generate the corresponding Makefile.in. Note that automake has a rather simplistic view of what constitutes a package; it assumes that a package has only one configure.in, at the top. If your package has multiple configure.ins, then you must run automake in each directory holding a configure.in. You can optionally give automake an argument; .am is appended to the argument and the result is used as the name of the input file. This feature is generally only used to automatically rebuild an out-of-date Makefile.in. Note that automake must always be run from the topmost directory of a project, even if being used to regenerate the Makefile.in in some subdirectory. This is necessary because automake must scan configure.in, and because automake uses the knowledge that a Makefile.in is in a subdirectory to change its behavior in some cases. automake accepts the following options: -a --add-missing Automake requires certain common files to exist in certain situations; for instance config.guess is required if configure.in runs AC_CANONICAL_HOST. Automake is distributed with several of these files; this option will cause the missing ones to be automatically added to the package, whenever possible. In general if Automake tells you a file is missing, try using this option. By default Automake tries to make a symbolic link pointing to its own copy of the missing file; this can be changed with --copy. --libdir=DIR Look for Automake data files in directory DIR instead of in the installation directory. This is typically used for debugging. -c --copy When used with --add-missing, causes installed files to be copied. The default is to make a symbolic link. --cygnus Causes the generated Makefile.ins to follow Cygnus rules, instead of GNU or Gnits rules. -f --force-missing When used with --add-missing, causes standard files to be rebuilt even if they already exist in the source tree. This involves removing the file from the source tree before creating the new symlink (or, with --copy, copying the new file). --foreign Set the global strictness to foreign. --gnits Set the global strictness to gnits. --gnu Set the global strictness to gnu. This is the default strictness. --help Print a summary of the command line options and exit. -i --ignore-deps This disables the dependency tracking feature. --include-deps This enables the dependency tracking feature. This feature is enabled by default. This option is provided for historical reasons only and probably should not be used. --no-force Ordinarily automake creates all Makefile.ins mentioned in configure.in. This option causes it to only update those Makefile.ins which are out of date with respect to one of their dependents. -o DIR --output-dir=DIR Put the generated Makefile.in in the directory DIR. Ordinarily each Makefile.in is created in the directory of the corresponding Makefile.am. This option is used when making distributions. -v --verbose Cause Automake to print information about which files are being read or created. --version Print the version number of Automake and exit. --Werror --Wno-error --Werror will cause all warnings issued by automake to become errors. Errors affect the exit status of automake, while warnings do not. --Wno-error, the default, causes warning to be treated as warnings only. SEE ALSO
aclocal(1), and the Texinfo documentation for automake AUTHORS
Automake was written primarily by David Mackenzie and Tom Tromey. This manpage written by Ben Pfaff <pfaffben@pilot.msu.edu> for the Debian GNU/Linux automake package. 28 Jan 2002 AUTOMAKE(1)
All times are GMT -4. The time now is 04:43 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy