Hello David,
* Dr. David Kirkby wrote on Mon, Aug 10, 2009 at 09:34:44PM CEST:
> AIX tends not to be use by maths/science people.
That doesn't match my experience; although GNU/Linux seems to become
more and more dominant overall.
Cheers,
Ralf
___
Au
Bob Friesenhahn wrote:
On Sun, 9 Aug 2009, Dr. David Kirkby wrote:
I'd love to see a port to HP-UX, where I know at least one person is
interested in Mathematical software, but the userbase is not large.
Wolfram Research gave up development on AIX and IRIX many years ago,
and HP-UX more rece
Bob Friesenhahn wrote:
On Sun, 9 Aug 2009, Dr. David Kirkby wrote:
I can see your point. At the moment, there is no effort at all to
support any operating system that does not Sun or GNU compilers. i.e.
nobody is making any effort at all to support HP-UX, AIX, tru64 etc.
A shame! I certain
Richard Ash wrote:
On Fri, 2009-08-07 at 21:51 +0100, Dr. David Kirkby wrote:
Do you have a better idea how to tell what linker gcc uses?
Why do you actually care? Surely what you want to know is what options
work on the linker that you have to hand? So you will need to test the
linker options
On Fri, 2009-08-07 at 21:51 +0100, Dr. David Kirkby wrote:
> Do you have a better idea how to tell what linker gcc uses?
Why do you actually care? Surely what you want to know is what options
work on the linker that you have to hand? So you will need to test the
linker options you want to use, if
Bob Friesenhahn wrote:
On Fri, 7 Aug 2009, Dr. David Kirkby wrote:
gcc -Wl,-zallextract simple.c
should return an error if the GNU linker is used, as it will not
understand the -zallextract option. But it will not produce any error
if gcc uses the Sun linker, since -zallextract is a valid op
On Fri, 7 Aug 2009, Dr. David Kirkby wrote:
gcc -Wl,-zallextract simple.c
should return an error if the GNU linker is used, as it will not understand
the -zallextract option. But it will not produce any error if gcc uses the
Sun linker, since -zallextract is a valid option.
This is a useles
Ben Pfaff writes:
> Russ Allbery writes:
>> I used to feel that way, but I'm personally switching everything over
>> to it, particularly as I have access to fewer and fewer platforms
>> myself. I don't think it provides as much portability in some cases as
>> hand-tuned linker flags, but unless
"Dr. David Kirkby" writes:
> Russ Allbery wrote:
>> It's a pain in the ass, but sadly the most robust thing for you to do
>> is to write configure probes that try to use the exact linker options
>> that you want to use and see if they work.
> I've done that. Sage will build ok on Solaris if gcc
Russ Allbery wrote:
"Dr. David Kirkby" writes:
What I have done in Sage is to test the version of the linker, to see if
it Sun or GNU. But this relies on the fact the first copy of 'ld' in the
path is the one used when building gcc. That might not be true. So
whilst my hacks do allow Sage to b
Russ Allbery writes:
> "Dr. David Kirkby" writes:
>> I'd rather not use libtool - I don't want to learn yet another
>> tool. Especially since it has already caused me some grief on Solaris.
>
> I used to feel that way, but I'm personally switching everything over to
> it, particularly as I have
"Dr. David Kirkby" writes:
> What I have done in Sage is to test the version of the linker, to see if
> it Sun or GNU. But this relies on the fact the first copy of 'ld' in the
> path is the one used when building gcc. That might not be true. So
> whilst my hacks do allow Sage to build with eithe
Philip Herron wrote:
Hey
Not to sound annoying, but are you maybe approaching the problem the
wrong way around? You use autoconf so you don't have to worry about
these problems. So i take it sage is c or c++ etc..
All you should really care about is making sure your environment has a
compatibl
Russ Allbery wrote:
Philip Herron writes:
All you should really care about is making sure your environment has a
compatible c compiler or whats needed and autoconf does that for you,
with the prog_c macro then it inserts into the makefile etc. And you
just have to make sure your code is compat
Philip Herron writes:
> All you should really care about is making sure your environment has a
> compatible c compiler or whats needed and autoconf does that for you,
> with the prog_c macro then it inserts into the makefile etc. And you
> just have to make sure your code is compatible. I would d
On Fri, 7 Aug 2009, Dr. David Kirkby wrote:
This gcc on Solaris (SPARC) for example is build with both the Sun linker and
assembler.
Parsing the output of gcc -v is not an option, as its not necessary for these
to be specified - one could leave them, and let the gcc configure script
chose o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dr. David Kirkby wrote:
> When building gcc on Solaris, its possible to built it 4 ways.
>
> * Use the Sun linker and Sun assembler * Use the Sun linker and GNU
> assembler * Use the GNU assembler and Sun linker * Use the GNU
> linker and GNU assembler
When building gcc on Solaris, its possible to built it 4 ways.
* Use the Sun linker and Sun assembler
* Use the Sun linker and GNU assembler
* Use the GNU assembler and Sun linker
* Use the GNU linker and GNU assembler.
I'd like to be able to test whether gcc uses the Sun or GNU linker, and
Sun
18 matches
Mail list logo
