-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
while i have access to the w32 build machine in the PdLab i have a hard time getting anything useful to compile.
this is mainly, because i cannot access the binaries built by the pd-extended autobuild, and i don't want build the whole shebang myself.
what is the preferred way to get anything going on that machine?
fgmasdr IOhannes
On Nov 2, 2011, at 9:12 AM, IOhannes m zmoelnig wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
while i have access to the w32 build machine in the PdLab i have a hard time getting anything useful to compile.
this is mainly, because i cannot access the binaries built by the pd-extended autobuild, and i don't want build the whole shebang myself.
what is the preferred way to get anything going on that machine?
I assume you need access to the binaries for the linking. You can point your PD_PATH to /home/pd/auto-build/pd-extended/pd and as long as last night's build succeeded in building the core of Pd-extended, there will be binaries there. It should be read everyone.
Or you could just copy the pd-extended/pd folder somewhere in the pddev account and keep a location account. Or even check out pure-data.git, and build it there.
.hc
----------------------------------------------------------------------------
Man has survived hitherto because he was too ignorant to know how to realize his wishes. Now that he can realize them, he must either change them, or perish. -William Carlos Williams
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2011-11-02 14:43, Hans-Christoph Steiner wrote:
I assume you need access to the binaries for the linking. You can point your PD_PATH to /home/pd/auto-build/pd-extended/pd and as long as last night's build succeeded in building the core of Pd-extended, there will be binaries there. It should be read everyone.
unfortunately not. i looked at the autobuild-logs and the externals/Makefile to see how things are built there; attached (make.log) is what i got when trying to build externals/windowing in exactly the same way as the autobuild.
(the make.log shows problems with header files, which are of course quite easy to overcome; unfortunately i get the same problems when linking)
Or you could just copy the pd-extended/pd folder somewhere in the pddev account and keep a location account.
well, no; attached (copying.log) is the output when i try to do the copy.
Or even check out pure-data.git, and build it there.
that would be a good idea, but: - - the machine is a bit slow; compiling Pd takes ages - - i still haven't spent enough time to get a usable build, even when i did find a bit of time to try to compile Pd myself. - - i'd rather spend my time in getting my broken code to work than to "fix" things which already appear to work anyhow
fgmasdr IOhannes
On Nov 2, 2011, at 10:05 AM, IOhannes m zmoelnig wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2011-11-02 14:43, Hans-Christoph Steiner wrote:
I assume you need access to the binaries for the linking. You can point your PD_PATH to /home/pd/auto-build/pd-extended/pd and as long as last night's build succeeded in building the core of Pd-extended, there will be binaries there. It should be read everyone.
unfortunately not. i looked at the autobuild-logs and the externals/Makefile to see how things are built there; attached (make.log) is what i got when trying to build externals/windowing in exactly the same way as the autobuild.
(the make.log shows problems with header files, which are of course quite easy to overcome; unfortunately i get the same problems when linking)
Or you could just copy the pd-extended/pd folder somewhere in the pddev account and keep a location account.
well, no; attached (copying.log) is the output when i try to do the copy.
Or even check out pure-data.git, and build it there.
that would be a good idea, but:
- the machine is a bit slow; compiling Pd takes ages
- i still haven't spent enough time to get a usable build, even when i
did find a bit of time to try to compile Pd myself.
- i'd rather spend my time in getting my broken code to work than to
"fix" things which already appear to work anyhow
I forced everything in the 'pd' account to be read everyone, hope that helps.
.hc
----------------------------------------------------------------------------
As we enjoy great advantages from inventions of others, we should be glad of an opportunity to serve others by any invention of ours; and this we should do freely and generously. - Benjamin Franklin
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2011-11-02 16:30, Hans-Christoph Steiner wrote:
I forced everything in the 'pd' account to be read everyone, hope that helps.
thanks. i guess this will only become active after the next autobuild run, correct? for now, i still have: $ ls -lha /home/pd/auto-build/pd-extended/pd/src/m_pd.h - -rwx------ 1 pd None 26K Nov 2 03:32 /home/pd/auto-build/pd-extended/pd/src/m_pd.h
fgmasdr IOhannes
On Nov 2, 2011, at 11:58 AM, IOhannes m zmoelnig wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2011-11-02 16:30, Hans-Christoph Steiner wrote:
I forced everything in the 'pd' account to be read everyone, hope that helps.
thanks. i guess this will only become active after the next autobuild run, correct? for now, i still have: $ ls -lha /home/pd/auto-build/pd-extended/pd/src/m_pd.h
- -rwx------ 1 pd None 26K Nov 2 03:32
/home/pd/auto-build/pd-extended/pd/src/m_pd.h
It should be active now. Cygwin's perms don't always reflect the situation, since Windows does not have user/group/other, only ACLs. So sometimes the ACLs don't match up well to the user/group/other style. Did you try to read the file?
.hc
----------------------------------------------------------------------------
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2011-11-02 16:59, Hans-Christoph Steiner wrote:
On Nov 2, 2011, at 11:58 AM, IOhannes m zmoelnig wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2011-11-02 16:30, Hans-Christoph Steiner wrote:
I forced everything in the 'pd' account to be read everyone, hope that helps.
thanks. i guess this will only become active after the next autobuild run, correct? for now, i still have: $ ls -lha /home/pd/auto-build/pd-extended/pd/src/m_pd.h
- -rwx------ 1 pd None 26K Nov 2 03:32
/home/pd/auto-build/pd-extended/pd/src/m_pd.h
It should be active now. Cygwin's perms don't always reflect the situation, since Windows does not have user/group/other, only ACLs. So sometimes the ACLs don't match up well to the user/group/other style. Did you try to read the file?
hmm weird. cygwin shows -rwx------ mingw shows -rwxr-xr-x
the output of the compilation on mingw is: gcc -I"/home/pd/auto-build/pd-extended/pd/src" -DPD -DVERSION='"0.1"' - -mms-bitfields -DPD -DHAVE_G_CANVAS_H - -I/home/pd/auto-build/pd-extended/pd/src -Wall -W -ggdb - -I/home/pd/auto-build/pd-extended/externals/Gem -mms-bitfields -DMSW - -DNT -D'O_NONBLOCK=1' -D'srand48(n)=srand((n))' - -D'drand48()=((double)rand()/RAND_MAX)' -D'bzero(p,n)=memset(p,0,n)' -O3 - -funroll-loops -fomit-frame-pointer -o "iemnet.o" -c "iemnet.c" In file included from iemnet.c:25:0: iemnet.h:36:18: fatal error: C:/MinGW/msys/1.0/home/pd/auto-build/pd-extended/pd/src/m_pd.h: Permission denied compilation terminated.
no idea
fgmasdr IOhannes
.hc
http://at.or.at/hans/
Pd-dev mailing list Pd-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
On Nov 2, 2011, at 12:03 PM, IOhannes m zmoelnig wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2011-11-02 16:59, Hans-Christoph Steiner wrote:
On Nov 2, 2011, at 11:58 AM, IOhannes m zmoelnig wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2011-11-02 16:30, Hans-Christoph Steiner wrote:
I forced everything in the 'pd' account to be read everyone, hope that helps.
thanks. i guess this will only become active after the next autobuild run, correct? for now, i still have: $ ls -lha /home/pd/auto-build/pd-extended/pd/src/m_pd.h
- -rwx------ 1 pd None 26K Nov 2 03:32
/home/pd/auto-build/pd-extended/pd/src/m_pd.h
It should be active now. Cygwin's perms don't always reflect the situation, since Windows does not have user/group/other, only ACLs. So sometimes the ACLs don't match up well to the user/group/other style. Did you try to read the file?
hmm weird. cygwin shows -rwx------ mingw shows -rwxr-xr-x
the output of the compilation on mingw is: gcc -I"/home/pd/auto-build/pd-extended/pd/src" -DPD -DVERSION='"0.1"'
- -mms-bitfields -DPD -DHAVE_G_CANVAS_H
- -I/home/pd/auto-build/pd-extended/pd/src -Wall -W -ggdb
- -I/home/pd/auto-build/pd-extended/externals/Gem -mms-bitfields -DMSW
- -DNT -D'O_NONBLOCK=1' -D'srand48(n)=srand((n))'
- -D'drand48()=((double)rand()/RAND_MAX)' -D'bzero(p,n)=memset(p,0,n)' -O3
- -funroll-loops -fomit-frame-pointer -o "iemnet.o" -c "iemnet.c"
In file included from iemnet.c:25:0: iemnet.h:36:18: fatal error: C:/MinGW/msys/1.0/home/pd/auto-build/pd-extended/pd/src/m_pd.h: Permission denied compilation terminated.
no idea
Ah, ok, I think I fixed that. I forgot that the msys home tree is separate from the rest.
.hc
----------------------------------------------------------------------------
If you are not part of the solution, you are part of the problem.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2011-11-02 22:07, Hans-Christoph Steiner wrote:
Ah, ok, I think I fixed that. I forgot that the msys home tree is separate from the rest.
seems to work ok, thanks for the fix.
fgmasdr IOhannes
-
Hans-Christoph Steiner -
IOhannes m zmoelnig