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:
it's as if configure never did its job??
I know this must be a very easy fix... any help would be very much appreciated! Thanks!
I try to compile Samba 3.0.27a under AIX with LDAP and KErberos.
The configure work fine:
CFLAGS:
-I/opt/pware/include -I/opt/pware/lib/ -I/opt/pware/open_ldap_exec/lib/ -I/software/samba/oldap/usr/lib -I/software/samba/oldap/usr/include
./configure --prefix=/opt/pware/samba/3.0.27a... (1 Reply)
Compiling samba 3.0.27a under AIX
I try to compile Samba 3.0.27a under AIX with LDAP and KErberos.
The configure work fine:
CFLAGS:
-I/opt/pware/include -I/opt/pware/lib/ -I/opt/pware/open_ldap_exec/lib/ -I/software/samba/oldap/usr/lib -I/software/samba/oldap/usr/include
./configure... (2 Replies)
OS: Solaris 10
I downloaded a binary from samba.org (3.0.24)
I extracted the file and ran the following command:
# ./configure --prefix=/usr/sfw --with-configdir=/etc/sfw --with-winbind
Now I am trying to understand the compile process but I can't find many answers online
... (10 Replies)
Hello, I asked this question in the AIX subforum but never received an answer, probably because the AIX forum is not that heavily trafficked. Anyway, here it is..
I have never had any issues like this when compiling applications from source. When I try to compile samba-3.5.0pre2, configure runs... (9 Replies)
People i download the lastest version of samba i`am tryng to compile it in a solaris 9 i'm reading the how to of samba, i am in the first step making the autogen.sh but show me this when i do ./autogen.sh
./autogen.sh: running script/mkversion.sh
./script/mkversion.sh: 'include/version.h'... (0 Replies)
Hi all,
I am getting the following error While installing Samba 3.4.1 on Solaris 10.
#./autogen.sh
./autogen.sh : autoheader : not found
./autogen.sh : test : argument expected
Please help me as I am in a critical state of the project.
Warm regards,
Sathya (10 Replies)
I am trying to compile a c++ source file print_options.cpp and getting lot of errors
g++ -I/media/ios120/chrisd/research/tomso-branches/tomso_12_05 /media/ios120/chrisd/research/tomso-branches/tomso_12_05/libs/program_options/print_options.cpp
In file included from... (2 Replies)
Need assistance in compile a source code with PERL flags
Compile source code CDFconvert-2.2.3 which requires Fortran 90,Perl interpreter , Perl/TK module , NetCDF library , Gempak
I have all the above required libraries .
Issue is when compiling the source code it looks for local... (4 Replies)
I am running Fedora V21 and had their default Samba installed. But I wanted to put up a PDC with ADS, so I uninstalled samba and down loaded the Samba 4.4.5 source along with the Kerberos devel kit etc.
I then configured and compiled etc and it indicated it was successful.
But I can't load the... (0 Replies)
Discussion started by: griffinmt
0 Replies
LEARN ABOUT CENTOS
mren
mren(1) General Commands Manual mren(1)Name
mren - rename an existing MSDOS file
Note of warning
This manpage has been automatically generated from mtools's texinfo documentation, and may not be entirely accurate or complete. See the
end of this man page for details.
Description
The mren command is used to rename or move an existing MS-DOS file or subdirectory. Its syntax is:
mren [-voOsSrRA] sourcefile targetfile
Mren renames an existing file on an MS-DOS file system.
In verbose mode, Mren displays the new filename if the name supplied is invalid.
If the first syntax is used (only one source file), and if the target name doesn't contain any slashes or colons, the file (or subdirec-
tory) is renamed in the same directory, instead of being moved to the current mcd directory as would be the case with mmove. Unlike the MS-
DOS version of REN, mren can be used to rename directories.
See Also
Mtools' texinfo doc
Viewing the texi doc
This manpage has been automatically generated from mtools's texinfo documentation. However, this process is only approximative, and some
items, such as crossreferences, footnotes and indices are lost in this translation process. Indeed, these items have no appropriate repre-
sentation in the manpage format. Moreover, not all information has been translated into the manpage version. Thus I strongly advise you
to use the original texinfo doc. See the end of this manpage for instructions how to view the texinfo doc.
* To generate a printable copy from the texinfo doc, run the following commands:
./configure; make dvi; dvips mtools.dvi
* To generate a html copy, run:
./configure; make html
A premade html can be found at `http://www.gnu.org/software/mtools/manual/mtools.html'
* To generate an info copy (browsable using emacs' info mode), run:
./configure; make info
The texinfo doc looks most pretty when printed or as html. Indeed, in the info version certain examples are difficult to read due to the
quoting conventions used in info.
mtools-4.0.18 09Jan13 mren(1)