OpenMacNews wrote:
hi florian,
I used a fresh checkout of pgadmin3, and, apart from
chmod 755 complete-bundle.sh
I had to change nothing, and it worked...


ok, i'm confused then too. how exactly do _you_ execute a script if its perms do not include the execute flag? what happens if you simply attempt to invoke the script directly at cmd-line?

if you invoke it as an arg to "sh" (sh complete-bundle.sh), then sure ... but directly (./complete-bundle.sh)?

what ARE your complete-bundle.sh's perms in a virgin DL?

again, mine are:

-rw-r--r-- 1 devuser admin 1306 Apr 12 00:36 pkg/mac/complete-bundle.sh

I _had_ to change the permissions of complete-bundle.sh - thats what I mean with "apart from chmod 755 complete-bundle.sh, I had to change nothing".

Maybe my limited knowledge of the english language caused confusion here,
so I'll rephrase "I used a fresh checkout of pgadmin3, and, apart from
chmod 755 complete-bundle.sh I had to change nothing and it worked":

What I wanted to say way:
I did a fresh checkout
Then I modified the permissions of complete-bundle.sh
Without _any_ further modifications I did
sh ./bootstrap
./configure <my configure args>
make
make install

This worked, and produced a valid .app (It crashes when opening a dialog, but
that is a wx problem I guess)

strange -- i can't imagine what's different abt our 2 systems ...

Could you post the output of wx-config --rezflags ?

here's the output from BOTH wxwidgets-cvs and wxwidgets-255

% /usr/local/wxWidgets-cvs/bin/wx-config --rezflags
/Developer/Tools/Rez -d __DARWIN__ -t APPL Carbon.r /usr/local/wxWidgets-cvs/lib/libwx_macud-2.6.0.r -o

% /usr/local/wxWidgets-255/bin/wx-config --rezflags
/Developer/Tools/Rez -d __DARWIN__ -t APPL Carbon.r /usr/local/wxWidgets-255/lib/libwx_macu-2.5.5.r -o
Does the file /usr/local/wxWidgets-255/lib/libwx_macu-2.5.5.r
exist on your system? If so, I'd say that your build
of wx cvs is in some way broken - maybe you should
report that to the wx mailinglist.

greetings, Florian Pflug

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature



Reply via email to