similar to: Installation

This is an updated version of my patches to get rsync to build and run its tests on the Stratus VOS operating system. I have updated this patch to apply cleanly to the current copy of HEAD. I also ran the test suite and discovered that I needed to tweak a few spots in the Makefile to append the executable suffix (VOS is one of the few systems that has a required executable suffix). There are a

Hi, I have a little request, which should be considered "very very very very low priority" but would be useful nonetheless... in Makefile.in there are two lines with additional space at end of line and my editor strip it, so I must hand-edit the cygwin-specific patch in order to create the package (nothing serious: only patch is using /usr instead of /usr/local as a default prefix and

I am guessing that since the error is on the first instance of the use of foo$(VAR): foo.o construct, that the Irix makefile parser doesn't know how to deal with this line. Obviously they don't use GNU make.... So here is a patch to Makefile.in that simplifies the use of variables. This only uses constructs that should work in all makes. It should not break anything, and it

I just did a make clean to tidy up a bit and found four objects were missed. The seem to belong to the CHECK_PROGS set. Not sure where best to put them so created a CHECK_OBJS variable and added it to the clean rule. -- ________________________________________________________________ J.W. Schultz Pegasystems Technologies email address: jw@pegasys.ws Remember Cernan and

I had to make some patches to rsync to get it to build on VOS. We are a POSIX-96 (but not Unix) system. Here is the subset of the patches that I think are general to all platforms. I have tested these here. I was surprised that CPPFLAGS is not available to the compilation rules in the Makefile. Most other packages (e.g. Samba) seem to allow CPPFLAGS to be set by the user. Since this is how I

** This is a resend of mail I originally sent on September 5th. I am still interested in getting these patches applied, and getting a new config.guess and config.sub. Is there anything else I need to do in order to get these changes accepted? Thanks. PG ** I had to make some patches to rsync to get it to build on VOS. We are a POSIX-96 (but not Unix) system.

I am getting the following errors when compiling SAMBA 2.2.4 on HP-UX 11.00. Anyone have any ideas on what's causing the problem? Using FLAGS = -O -I./popt -Iinclude -I./include -I./ubiqx -I./smbwrapper -D_HPUX_SOURCE -D_POSIX_SOURCE -D_LARGEFILE64_SOURCE -D_ALIGNMENT_REQUIRED=1 -D_MAX_ALIGNMENT=4 -DLOGFILEBASE="/opt/samba/var" -DCONFIGFILE="/opt/samba/etc/smb.conf"

I am getting the following link errors when compiling SAMBA 2.2.4 on HP-UX 11.00. Anyone have any ideas on what's causing the problem? Using FLAGS = -O -I./popt -Iinclude -I./include -I./ubiqx -I./smbwrapper -D_HPUX_SOURCE -D_POSIX_SOURCE -D_LARGEFILE64_SOURCE -D_ALIGNMENT_REQUIRED=1 -D_MAX_ALIGNMENT=4 -DLOGFILEBASE="/opt/samba/var"

Hi -- I've added splint annotations to rsync code from CVS. The resulting work-in-progress is at ftp://people.redhat.com/jbj/rsync-splint.tar.gz Splint is a lightweight assertion checker, details at http://www.splint.org Any interest in including splint annotations in rsync source code? If so, inquire privately and I'll try to assist. 73 de Jeff -- Jeff Johnson ARS N3NPQ

Wayne, i like the diff -u idea. I find -c awkward. It seems to me that the shell script could test for support of -u and if present use it instead of -c. ala if [ -n "`diff -u /dev/null /dev/null 2>&1`" ] then difftype="-c" else difftype="-u" fi diff $difftype "$2"/"$f" "$3"/"$f" || failed=YES or something

2010/2/17 Arnaud Quette > 2010/2/17 Arjen de Korte: > > Citeren Charles Lepple: > > > >> I wonder if there are any cross-compilation targets we could use to test > >> some of the word-size assumptions. Also, we could add in some static > >> analysis tools. > > FYI, I submitted NUT to the Coverity Scan program > (http://scan.coverity.com) last

Hi, I would like to ask you to consider the attached patch for inclusion into the next samba release. The patch addresses the following three points: 1. 'make install' with VPATH fails at one point ( $(srcdir)/script/findsmb vs. script/findsmb ) 2. support for 'make DESTDIR=<somewhere> install' (e.g. to build a binary package) 3. support for 'configure

I am trying to understand idea for splint, but it use Fortran code. Does anyone know how to see that Fortran code? Is splint a not-knot spline method? Thanks, jfm [[alternative HTML version deleted]]

The first patch will make "make install-strip" work. The second spends a few cycles avoiding "1 files to consider." Both are trivial but IMHO useful. --- Makefile.orig Wed Mar 13 06:38:42 2002 +++ Makefile Wed Mar 13 06:40:58 2002 @@ -12,6 +12,7 @@ LDFLAGS= INSTALLCMD=/bin/install -c +INSTALLMAN=/bin/install -c srcdir=. @@ -56,8 +57,8 @@ ${INSTALLCMD} -m 755 rsync

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Recent versions of rsync have a "regression test" called "chmod-option" that when run fails, this should be causing rsync to be rejected as broken by all distros and sysadmins. A bit of research show that no one has mentioned this test since it was last worked on in late September, nor does it show up as a current bug

I remember seeing a patch here a long while back that I thought was going to be committed for making the install relocatable (i.e. allowing for a DESTDIR to be specified during a "make install"). I can't find it, and I'm not sure I am remembering correctly, anyway, so here is a shot at it. Tested both the install and uninstall, run as "make install

Greetings - Does CRAN or someone similar make a splint / lint-like syntax checker for R? I realize that both ESS and the debug package and similar tools have debugging and error analysis features, but those appear to require running the code through the R buffer. I'd like something that did basic syntax and object-name verification for code that was to run in batch, as a precursor to

According to the Samba documentation, the manpages are supposed to be installed with Samba. Quote: docs/manpages: You don't need to worry about these yet; during the installation, the files will be installed so that you can use the man command to read them. But you can take a look in the directory to see which manpages are available. My problem: Samba4 on 64bit Fedora 17 will not

>From 2.6.2's Makefile: install: all ... ${INSTALLCMD} ${STRIP} -m 755 rsync$(EXEEXT) ${DESTDIR}${bindir} ... install-strip: $(MAKE) STRIP='-s' install This doesn't work (at least) on OpenBSD, because install(1) there will use the value of the environment variable STRIP as the command to run for stripping the executable. Renaming the variable will take care of this. ---

https://bugzilla.samba.org/show_bug.cgi?id=7625 Summary: "Don't know how to make ./*.c" Product: rsync Version: 3.0.7 Platform: s390 OS/Version: Other Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned at samba.org ReportedBy: sebastian.hoffman at