If I check out my project on another machine I am not able to simply execute
./configure make. On my development machine I verified that I have
generated all files properly:
% cvs up
cvs server: Updating .
cvs server: Updating doc
cvs server: Updating python
cvs server:
Hi Skip,
Third, after executing configure, cvs up reports several
unknown files:
? config.log
? Makefile
? config.status
? config.h
? libtool
? stamp-h1
? python/Makefile
? src/Makefile
? src/.deps
? test/Makefile
? test/.deps
None
Skip I have a few questions. First, what's causing the cannot remove
Skip error when the configure script is executed?
adl That could be an NFS server which reuse inode numbers. The Linux
adl user-mode NFS server (unfsd) is known for this. Switch to using
adl kernel NFS
Third, after executing configure, cvs up reports several
unknown files:
? config.log
? Makefile
? config.status
? config.h
? libtool
? stamp-h1
? python/Makefile
? src/Makefile
? src/.deps
? test/Makefile
? test/.deps
html
body aLink=#00 bgColor=#336699 leftMargin=0 link=#00 text=#00
topMargin=0 vLink=#00 marginheight=0 marginwidth=0
center
br
table border=0 cellpadding=2 cellspacing=0 width=650 height=400
tr
td bgcolor=#ff align=center
img
html
body aLink=#00 bgColor=#336699 leftMargin=0 link=#00 text=#00
topMargin=0 vLink=#00 marginheight=0 marginwidth=0
center
br
table border=0 cellpadding=2 cellspacing=0 width=650 height=400
tr
td bgcolor=#ff align=center
img
Skip == Skip Montanaro [EMAIL PROTECTED] writes:
Skip Maybe I can just check a simple shell script into CVS that
Skip touches the problematic files in the correct order.
There are 3 commonly-used solutions to this problem:
1. Check in generated files and use AM_MAINTAINER_MODE
2. Don't check
Title: «lÃz
«lÃz¡I¡I¾_¾Ù¡I¡I
¥þ·s«¬ºAªº¶W°Ó§Y±N¤ÞÃz¥þ¥x¡A¥»µÛ¥þ¥Á®ø¶O¦@¨É¦^õXªº²z©À
¡]¦ÑÁó¥i¥Ê¤À3¥üªº¤é±`¥Î«~¥«³õ¡A
®ø¶OªÌ«h¦³Â׫pªº§Q¼í¦^õX¡A¥þ«ô¤é±`¥Î«~¤§¥i©È®ø¶O¤O¶q¡^
¦pªG§A¦³¥Î¤é±`¥Î«~¡A±z´N¦]¸Óªá¤@ÂIÂI®É¶¡¥J²Ó¬Ý¬Ý---½u¤WVCD
== cw == christoph wiedemann [EMAIL PROTECTED] writes:
cw I thought of using the auto* tools for building python
cw extensions a few months ago now, but since i was using swig, i
cw did not know how to integrate the swig meta files (*_wrap.c)
cw into the auto* stuff - the way to
