Re: [GiNaC-list] modify source, run make, then ...
Hi,
If I modify a .cpp source file (say to change a thrown error message to pinpoint the location in the code where the error is being generated) and then run 'make' within >> the subdirectory containing the .cpp source file to generate an updated .o file, do I have to do anything else to incorporate my modified error message? Could you please be more specific? What is exactly that .cpp file? Is it a part of your program, or GiNaC (or > any other shared library)?
The file, r.cpp, is part of another shared library, xloops.
I think not It depends. (Sorry, I need to know more details to give a useful answer).
By modifying r.cpp, running 'make' and then running 'make install' the changes made to r.cpp were incorporated (the error message thrown was the modified message). After stumbling upon the solution it appears my original question should have been posted to a beginner's gcc msg board and not GiNaC. Sorry for the clutter. Sincerely, Chris Bouchard
Hi, On Fri, Jul 11, 2008 at 05:56:57AM -0500, Chris Bouchard wrote:
The file, r.cpp, is part of another shared library, xloops.
[skipped]
By modifying r.cpp, running 'make' and then running 'make install' the changes made to r.cpp were incorporated (the error message thrown was the modified message).
Another way is to start your program with proper LD_LIBRARY_PATH *without* installing the shared library to its final location, i.e. LD_LIBRARY_PATH=/path/to/xloops/xloops/.libs /path/to/the/binary This method is useful if you don't want to override the previous version of shared library for some reason.
After stumbling upon the solution it appears my original question should have been posted to a beginner's gcc msg board and not GiNaC. Sorry for the clutter.
No problem. BTW, the question has very little to do with gcc. It's rather 'How do ELF shared libraries work on *nixy OSes?' Best regards, Alexei -- All science is either physics or stamp collecting.
participants (2)
-
Alexei Sheplyakov
-
Chris Bouchard