Re: [Denemo-devel] The missing regex in mxe build

[Jeremiah Benham]

Since you have had success compiling master before, I suggest you do something like this:

git diff master | less
git diff master -- gub/spec/python.py

Then if you want something from master branch you can do something like:

git checkout master -- gub/specs/python.py

This will pull the python.py from master.

Jeremiah

On Feb 26, 2013 11:56 AM, "Richard Shann" <address@hidden> wrote:

On Tue, 2013-02-26 at 16:38 +0000, Richard Shann wrote:
> On Tue, 2013-02-26 at 16:36 +0000, Richard Shann wrote:
> > On Tue, 2013-02-26 at 09:50 -0600, Jeremiah Benham wrote:
> > > with the denemo.py file I sent
> > Ah - this could be relevant - the one you sent is different from the
> > one
> > in the repository on release-0.9.6-mingw branch. (Although, as it has
> > failed while trying to build python, perhaps this couldn't be the
> > cause
> > of the failure). I'll try the denemo.py you sent.
>
> Well that also failed on the python build ...
The library it is looking for is in two places in fact

address@hidden:~/gub$ find . -name libpython2.4.so.1.0
./target/tools/build/python-2.4.5/libpython2.4.so.1.0
./target/tools/install/python-2.4.5-root/home/rshann/gub/target/tools/root/usr/lib/libpython2.4.so.1.0

The first of these I take it is the temporary location where it has been
built, the second looks suspicious, as if a setting of LD_LIBRARY_PATH
has gone wrong. I notice that janneke's gub has a radically different
python.py file, and a patch referring to the gcc -R option, which
appears in the python.log of my build as an "unrecognised option". It
seems that -R is equivalent to -rpath for directories (not that I
understand that option either).

As you can tell, I am rather wading through treacle here...

Richard



_______________________________________________
Denemo-devel mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/denemo-devel