One of the PLplot developers has been using the macada version of the gcc
compiler on Mac OS X for a long time because that version gives him an
integrated Ada compiler as well. That compiler worked well for cmake-2.4,
but he has recently run into build problems for cmake-2.6.
The issue can be i
Alan W. Irwin schrieb:
> Can somebody recommend a fix to that file so that CMake-2.6.2 works just as
> well as CMake-2.4.8 for the macada version of the gcc compiler?
>
> I have no idea whether gcc should always be expected to recognize the
> -current_version flag.
http://gcc.gnu.org/onlinedocs/g
On 2009-01-28 11:19+0100 Hendrik Sattler wrote:
Alan W. Irwin schrieb:
Can somebody recommend a fix to that file so that CMake-2.6.2 works just as
well as CMake-2.4.8 for the macada version of the gcc compiler?
I have no idea whether gcc should always be expected to recognize the
-current_vers
On Wednesday 28 January 2009, Alan W. Irwin wrote:
> One of the PLplot developers has been using the macada version of the gcc
> compiler on Mac OS X for a long time because that version gives him an
> integrated Ada compiler as well. That compiler worked well for cmake-2.4,
> but he has recently
Alan W. Irwin wrote:
The issue can be illustrated by a simple "hello-world" shared library
build test project with SOVERSION and VERSION specified for the library.
From "make.out_gcc_macada_2.6.2":
--
/usr/local/ada
Alexander Neundorf wrote:
On Wednesday 28 January 2009, Alan W. Irwin wrote:
One of the PLplot developers has been using the macada version of the gcc
compiler on Mac OS X for a long time because that version gives him an
integrated Ada compiler as well. That compiler worked well for cmake-2.4,
Alan W. Irwin wrote:
[]
Is there a better gcc option then -v to find out the _actual_ linker being
used?
Use -Wl,-v :-)
On 10.4, if you run gcc -dynamiclib, the linking is managed by
/usr/bin/libtool which in turn calls /usr/bin/ld, and /usr/bin/libtool
understands the -current_version flag.
On 2009-01-29 00:31+0100 Martin Costabel wrote:
Alan W. Irwin wrote:
[]
Is there a better gcc option then -v to find out the _actual_ linker being
used?
Use -Wl,-v :-)
Thanks very much for that suggestion. It works like a charm on Linux. I
have passed it on to the macada gcc user, and I wi
Martin Costabel schrieb:
> Alan W. Irwin wrote:
> []
>> Is there a better gcc option then -v to find out the _actual_ linker
>> being
>> used?
>
> Use -Wl,-v :-)
>
> On 10.4, if you run gcc -dynamiclib, the linking is managed by
> /usr/bin/libtool which in turn calls /usr/bin/ld, and /usr/bin/lib
This thread has included different questions for the macada gcc user that
have been brought up in various posts. I will try to pass on all his
responses which he finally completed this morning.
Brad:
What is the output of macada gcc with this command line:
gcc -E -dM -x c /dev/null
See at
Hendrik Sattler wrote:
> Martin Costabel schrieb:
>> Alan W. Irwin wrote:
>> []
>>> Is there a better gcc option then -v to find out the _actual_ linker
>>> being
>>> used?
>> Use -Wl,-v :-)
>>
>> On 10.4, if you run gcc -dynamiclib, the linking is managed by
>> /usr/bin/libtool which in turn calls
On 2009-01-29 13:46-0500 Brad King wrote:
Hendrik Sattler wrote:
Martin Costabel schrieb:
Alan W. Irwin wrote:
[]
Is there a better gcc option then -v to find out the _actual_ linker
being
used?
Use -Wl,-v :-)
On 10.4, if you run gcc -dynamiclib, the linking is managed by
/usr/bin/libtool w
Alan W. Irwin wrote:
I suspect the ada/gcc compiler calls ld directly without passing through
/usr/bin/libtool. If this is true, changing "-current_version" to
"-dylib_current_version" should solve the problem.
In Darwin.cmake, this user changed
SET(CMAKE_C_OSX_CURRENT_VERSION_FLAG -Wl,-curr
13 matches
Mail list logo
