Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-ID:	<41DEAA5D.4040501@x-ray.at>
Date:	Fri, 07 Jan 2005 16:27:25 +0100
From:	Reini Urban <rurban AT x-ray DOT at>
User-Agent:	Mozilla/5.0 (Windows; U; Windows NT 5.0; de-AT; rv:1.7) Gecko/20040616
MIME-Version:	1.0
To:	THUFIR HAWAT <thufir DOT hawat AT mail DOT com>
CC:	cygwin AT cygwin DOT com
Subject:	Re: "make all" and "make install" for smake
References:	<20050106221803 DOT CFD04790087 AT cal1-1 DOT us4 DOT outblaze DOT com>
In-Reply-To:	<20050106221803.CFD04790087@cal1-1.us4.outblaze.com>
X-IsSubscribed:	yes

THUFIR HAWAT schrieb:
> as per <C:\cygwin\home\Administrator\smake-1.2\COMPILE>

Please ask further questions about a program not supported by cygwin at 
the right place.
Jörg Schilling suggests using joerg AT schily DOT isdn DOT cs DOT tu-berlin DOT de therefore.

> 
> $ pwd
> /home/Administrator/smake-1.2
> $ make all
> 
> NOTICE: Using bootstrap 'Makefile' to make 'all'
> cd psmake && sh ./MAKE-all
> Checking for working bootstrap make...
> Smake release 1.2a23 (i686-pc-cygwin) Copyright (C) 1985, 87, 88, 91, 
> 1995-2004 Jörg Schilling
> ./psmake/smake all
> 	==> MAKING "all" ON SUBDIRECTORY "SRCROOT/conf"
> 	==> MAKING "all" ON SUBDIRECTORY "SRCROOT/inc"
> 	==> MAKING "all" ON SUBCOMPONENT "SRCROOT/inc/align_test.mk"
> 	==> MAKING "all" ON SUBCOMPONENT "SRCROOT/inc/avoffset.mk"
> 	==> MAKING "all" ON SUBDIRECTORY "SRCROOT/lib"
> 	==> MAKING "all" ON SUBCOMPONENT "SRCROOT/lib/libschily.mk"
> 	==> MAKING "all" ON SUBDIRECTORY "SRCROOT/smake"
> 	==> MAKING "all" ON SUBDIRECTORY "SRCROOT/man"
> 	==> MAKING "all" ON SUBDIRECTORY "SRCROOT/man/man4"
> 	==> MAKING "all" ON SUBCOMPONENT "SRCROOT/man/man4/makefiles.mk"
> 	==> MAKING "all" ON SUBCOMPONENT "SRCROOT/man/man4/makerules.mk"
> 
> $ make install
> make: `install' is up to date.
> 
> 
> $ smake
> bash:  smake:  command not found
> 
> "make all" and "make install" suceeded, so why isn't smake a command now?
> tried deleting the INSTALL file, but had the same results.

$ less BUILD
---
To install the product of a compilation in your system, call:

		smake install

at top level. The binaries will usually be installed in
/opt/schily/bin. The directory /opt/<vendor-name>/ has been agreed
on by all major UNIX vendors in 1989. Unfortunately, still not all
vendors follow this agreement.

If you want to change the default installation directory, edit the
appropriate (system dependent) files in the DEFAULTS directory
(e.g. DEFAULTS/Defaults.sunos5).
---

Now you have to turn on your own brain, and probably you will come to 
the idea that you might want to add /opt/schily/bin to your PATH.
This helps if you want to your shell to find "smake", otherwise you have 
to use "/opt/schily/bin/smake".

Back to the make install problem, though this is a schilling problem not 
ours:

 > $ make install
 > make: `install' is up to date.

There is a bug in the Makefile. Ask Schilling.
psmake/smake install should work, but this seems to be buggy also.

$ psmake/smake install
         ==> MAKING "install" ON SUBDIRECTORY "SRCROOT/conf"
install: nothing to make
         ==> MAKING "install" ON SUBDIRECTORY "SRCROOT/inc"
         ==> MAKING "install" ON SUBCOMPONENT "SRCROOT/inc/align_test.mk"
         ==> MAKING DIRECTORY "/opt/schily/include"
         ==> INSTALLING "/opt/schily/include/align.h"
chown: "bin": ung"ultiger Benutzer
/usr/src/gnu/smake-1.2/smake/OBJ/i686-cygwin32_nt-gcc/smake: Couldn't 
make 'install'.
/usr/src/gnu/smake-1.2/smake/OBJ/i686-cygwin32_nt-gcc/smake: Couldn't 
make 'install'.
smake/OBJ/i686-cygwin32_nt-gcc/smake: Couldn't make 'install'.

BTW:
I like the idea to have a automake-like framework in a single smake 
executable. But first it should work, and 2nd it should not leave random 
Dnull files in the system.
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -