#9210: pkg-config prefix statements in SAGE_LOCAL/lib/pkg-config not changed
upon
Sage move
---------------------------+------------------------------------------------
Reporter: jason | Owner: drkirkby
Type: defect | Status: needs_review
Priority: major | Milestone: sage-4.6
Component: build | Keywords:
Author: Jason Grout | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
---------------------------+------------------------------------------------
Comment(by jason):
Replying to [comment:31 drkirkby]:
> Replying to [comment:30 jason]:
> > Replying to [comment:26 drkirkby]:
> > > This is simply not working for me. The system is a Sun Ultra 27
running !OpenSolaris on an Intel Xeon processor. This is what I did.
> >
> > You didn't quite follow the instructions.
>
> I think it was a case of not exactly explaining what I did. I believe I
did run Sage in the original location. When I extracted the tar file for a
second time, it showed the file
>
> {{{$SAGE_LOCAL/lib/sage-current-location.txt}}}
>
> But prior to running Sage that file did not exist. Then when I moved
Sage, the contents of
>
> $SAGE_LOCAL/lib/sage-current-location.txt
>
> changed, but the contents of the .pc files did not substantially change.
>
> I will revisit this - but I'm still not convinced it is working myself.
It might be a platform specific problem.
The fact that in your before tarball, the pkgconfig files did not start
with SAGE_ROOT leads me to believe that the sage-current-location.txt file
was created *before* the patch was applied, and was never deleted and sage
run before moving the directory. With the new patch applied, when that
file is created, the pkgconfig files should be modified to include a
SAGE_ROOT line at the very top.
I tried to use the python OS-agnostic functions everywhere, so on the
surface, I doubt it's an OS-specific problem.
So, if you have time, please try again, and make sure that after the patch
is applied, the sage-current-location.txt file is deleted which for
convenience, are repeated below:
To review, this should be sufficient:
#. Download and build Sage (important; it must be a fresh build from
source).
#. Apply the patch at the ticket to the scripts repository (in
SAGE_ROOT/local/bin):
http://trac.sagemath.org/sage_trac/raw-attachment/ticket/9210/trac-9210
-rewrite-sage-location.patch
#. Delete the file SAGE_ROOT/local/lib/sage-current-location.txt, if it
exists
#. Now run Sage, then exit (this updates the sage-current-location and
pkgconfig files appropriately). Check to make sure that sage-current-
location.txt is now created, and that each pkgconfig file starts with a
line "SAGE_ROOT=" (followed by the build directory)
#. Move the sage directory and run Sage again. The SAGE_ROOT/local/lib
/sage-current-location.txt should be updated, and the pkgconfig files in
SAGE_ROOT/local/lib/pkgconfig/ should also be updated to the new path (you
can check the freetype2.pc file, for example, to see the new sage
directory is listed there in the SAGE_ROOT variable).
Thanks!
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9210#comment:32>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
