On 14-Aug-07, at 11:25 PM, Christian Biere wrote:
>
>> 2) my little attempt to hack the "$so" variable (suffix) failed, yes.
>
> Retry with the current build.sh please. If "$so" is still
> necessary, I'll let
> it default to "dylib" if "uname -s" gains "darwin" or whatever.
Yes, it looks lik
Matthew Lye wrote:
> Okay, I tried build.sh again, and the previous problem was that
> Configure.sh couldn't find /usr/bin/make when being run from the
> build.sh script.
>
> > [21:32:48|~/prj/gtk-gnutella>./build.sh
> > Would you like to see the instructions? [n]
> > Locating common programs.
Matthew Lye wrote:
> Well, apparently someone rolled a natural 20 on precog.
>
> Currently spotted problems:
> 1)cflags are defined as the "additional" cc flags, rather than the
> optimizer/debugger flags, which are now "-O". Not sure what effect
> this will have.
It should only use -O i
Well, apparently someone rolled a natural 20 on precog.
Currently spotted problems:
1) cflags are defined as the "additional" cc flags, rather than the
optimizer/debugger flags, which are now "-O". Not sure what effect
this will have.
2) my little attempt to hack the "$so" variable
>> When you have some time, could you try build.sh and tell me where it
>> fails or things go wrong?
>>
>
> Sure, I'll give it another go. There was something I didn't like
> about it, or that didn't work, but I can't remember what.
Okay, I tried build.sh again, and the previous problem was that
Matthew Lye wrote:
> At the moment, as of an unknown build, but sometime earlier today,
> selecting multiple search items (in the search listing to the left,
> not the search results) is no longer possible with GTK1.
> Multiple items selected with the shift key held down will appear
> highlig
At the moment, as of an unknown build, but sometime earlier today,
selecting multiple search items (in the search listing to the left,
not the search results) is no longer possible with GTK1.
Multiple items selected with the shift key held down will appear
highlighted only until the key is re
On 14-Aug-07, at 2:37 PM, Christian Biere wrote:
> Matthew Lye wrote:
>> I still use "./Configure.sh" rather than "./build.sh" for
>> some reason (because of the library extensions if I recall correctly,
>> but I'm not sure), but the same stage.
>
> When you have some time, could you try build.sh
Matthew Lye wrote:
> I still use "./Configure.sh" rather than "./build.sh" for
> some reason (because of the library extensions if I recall correctly,
> but I'm not sure), but the same stage.
When you have some time, could you try build.sh and tell me where it
fails or things go wrong? It's ce
On 14-Aug-07, at 1:40 PM, Christian Biere wrote:
>> The following occurred upon startup with a clean build using prior
>> configuration defaults.
>
> Could you tell in terms of commands what this means?
This means starting from scratch, with the prior config file
defaults. I still use "./Conf
Matthew Lye wrote:
> The following occurred upon startup with a clean build using prior
> configuration defaults.
Could you tell in terms of commands what this means? Just running
"make" or "make clean" followed by "make" is not sufficient for proper
re-compilation. I shuffled a lot code around
11 matches
Mail list logo
