Albert,
The intent here is to satisfy those who want -DPIC but remove all
macro definition by default. I agree with the suggestion earlier
in this thread of adding a new macro AC_LIBTOOL_PICDEF([PIC])
and we'll plan on this for the release after the next one.
Thanks,
Robert
Albert Chin wrote:
Albert Chin <[EMAIL PROTECTED]> writes:
>
> Is setting a custom -DPIC really necessary?
I wouldn't think so. It's just if it's going to be removed then a way
to ask for it back would be nice.
> How about we just leave the existing -DPIC for the C and C++ tags?
Sounds good to me.
_
On Tue, Jan 21, 2003 at 09:13:54AM +1000, Kevin Ryde wrote:
> Robert Boehne <[EMAIL PROTECTED]> writes:
> >
> > All good ideas, and I don't really have a preference for any of them.
> > If you do, let me know or I'll just pick the one that looks easiest.
>
> I'd think an autoconf macro would be ok
Robert Boehne <[EMAIL PROTECTED]> writes:
>
> All good ideas, and I don't really have a preference for any of them.
> If you do, let me know or I'll just pick the one that looks easiest.
I'd think an autoconf macro would be ok, to be used for instance
AC_LIBTOOL_PICDEF([-DPIC])
AC
Invoking the 72-hour rule and checking this in.
Robert
Robert Boehne wrote:
>
> Ok, here it is. This patch changes AC_LIBTOOL_PROG_COMPILER_PIC
> so that it only appends -DPIC to the default "C" tag and the CXX
> tag for C++. I would also like to deprecate -DPIC in the 1.5 release
> to make it
Kevin,
All good ideas, and I don't really have a preference for any of them.
If you do, let me know or I'll just pick the one that looks easiest.
Robert
Kevin Ryde wrote:
>
> Robert Boehne <[EMAIL PROTECTED]> writes:
> >
> > How about an option to "configure" --define-for-pic="-DPIC"? Users
>
Robert Boehne <[EMAIL PROTECTED]> writes:
>
> How about an option to "configure" --define-for-pic="-DPIC"? Users
> could defeine whatever symbol they like, rather than Libtool specifying
> this.
You mean an option to the libtool script? Sounds ok. I wouldn't
think it'd need to be an actual conf
Robert Boehne <[EMAIL PROTECTED]> writes:
>
> Yet again I am suprised by the diversity of uses for Libtool,
> I hadn't imagined this m4->asm script. I am curious as to what tag
> it uses, the plain old C (empty) tag?
Yes, the rule for automake looks like
.asm.lo:
$(LIBTOOL) --mode=compil
Kevin,
Yet again I am suprised by the diversity of uses for Libtool,
I hadn't imagined this m4->asm script. I am curious as to what tag
it uses, the plain old C (empty) tag?
I think yours is the most valid point I've seen so far for
keeping some libtool-defined macro around, but if you only su
"Boehne, Robert" <[EMAIL PROTECTED]> writes:
>
> Wouldn't replacing -DPIC with -D__PIC__ break a fundamental
> assumption about ANSI compilers, that "__" means compiler-defined
> and not in the userspace?
I had an idea FOO was for applications, _FOO for the compiler, and
__FOO for third party libr
Robert Boehne <[EMAIL PROTECTED]> writes:
>
> I would also like
> to ask anyone who does depend on this to let us know when/where/why &
> how
> so we can add a section to the documentation on how to modify
> code to not need -DPIC.
In GMP we have assembler code (mainly i386) which understands it h
bert
-Original Message-
From: Guido Draheim [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 16, 2003 9:51 AM
To: Boehne, Robert
Cc: Simon Richter; [EMAIL PROTECTED]
Subject: Re: [PATCH] Re: Problem on rs6000-ibm-aix4.3.2.0 (Fortran)
-DPIC
Boehne, Robert schrieb:
>
> IMHO, I have yet
Title: RE: [PATCH] Re: Problem on rs6000-ibm-aix4.3.2.0 (Fortran) -DPIC
Guido,
Can you show me an example of a situation where there is
pic and non-pic code created by a compiler that doesn't define
some preprocessor macro for PIC?
Then if you find one, does it support inline assembl
Boehne, Robert schrieb:
IMHO, I have yet to see an example of how it could be useful
to define "PIC" when it seems that the only way to make use of
it is to have it surround severely implementation-specific stuff
like inline assembler in which case the compiler _should_ be defining
"__PIC__" or s
Boehne, Robert schrieb:
Wouldn't replacing -DPIC with -D__PIC__ break a fundamental
assumption about ANSI compilers, that "__" means compiler-defined
and not in the userspace?
[...]
#if (defined(__pic__) || defined(__PIC__)) && !defined(PIC)
#define PIC 1
#endif
The main problem with remo
Wouldn't replacing -DPIC with -D__PIC__ break a fundamental
assumption about ANSI compilers, that "__" means compiler-defined
and not in the userspace?
IMHO, I have yet to see an example of how it could be useful
to define "PIC" when it seems that the only way to make use of
it is to have it surro
Simon Richter schrieb:
Robert,
Ok, here it is. This patch changes AC_LIBTOOL_PROG_COMPILER_PIC
so that it only appends -DPIC to the default "C" tag and the CXX
tag for C++. I would also like to deprecate -DPIC in the 1.5 release
to make it clear we intend to do away with it. I would also lik
Robert,
> Ok, here it is. This patch changes AC_LIBTOOL_PROG_COMPILER_PIC
> so that it only appends -DPIC to the default "C" tag and the CXX
> tag for C++. I would also like to deprecate -DPIC in the 1.5 release
> to make it clear we intend to do away with it. I would also like
> to ask anyone
Ok, here it is. This patch changes AC_LIBTOOL_PROG_COMPILER_PIC
so that it only appends -DPIC to the default "C" tag and the CXX
tag for C++. I would also like to deprecate -DPIC in the 1.5 release
to make it clear we intend to do away with it. I would also like
to ask anyone who does depend on
Robert,
> I think you can ignore inline assembler for anything other than
> C (including C++). I've never thought about it, but inline assembler
> in Fortran code sounds truly frightening! Anyway, if it was so
> important, why doesn't the compiler define it for you?
Current gcc defines __PIC__
Title: RE: Problem on rs6000-ibm-aix4.3.2.0 (Fortran) -DPIC
Simon,
I think you can ignore inline assembler for anything other than
C (including C++). I've never thought about it, but inline assembler
in Fortran code sounds truly frightening! Anyway, if it was so
important, why doesn&
Robert,
> Ok then, I'll see if I can make "-DPIC" into
> a conditionally-set thing that would be set to "" for anything
> but C and C++. Can we agree on that? ;)
Yes, although it would be nice if the other languages also had a way of
knowing they should emit PIC, at least if they allow condition
Title: RE: Problem on rs6000-ibm-aix4.3.2.0 (Fortran) -DPIC
Ok then, I'll see if I can make "-DPIC" into
a conditionally-set thing that would be set to "" for anything
but C and C++. Can we agree on that? ;)
Robert
-Original Message-
From: Simon Richter
Hi,
> Good point, we never really resolved this issue.
> All in favor of dropping -DPIC entirely say "I"!
I'm against it.
If you have optimized assembler versions of some code for some platforms
(like the STL has, for example) and some of that code is not PIC, it is
a good idea to enclose it i
gt; Sent: Wednesday, January 15, 2003 4:11 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Problem on rs6000-ibm-aix4.3.2.0 (Fortran)
>
>
> On Wed, Jan 15, 2003 at 02:22:15PM -0500, Boehne, Robert wrote:
> > I will look into this, but FYI, -DPIC should not be passed when
> > com
Title: RE: Problem on rs6000-ibm-aix4.3.2.0 (Fortran) -DPIC
Albert,
Good point, we never really resolved this issue.
All in favor of dropping -DPIC entirely say "I"!
Robert
-Original Message-
From: Albert Chin [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 15,
e Edwards [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, January 15, 2003 1:03 PM
> To: [EMAIL PROTECTED]
> Subject: Problem on rs6000-ibm-aix4.3.2.0 (Fortran)
>
>
> I have just run into problems trying to use libtool on a
> rs6000-ibm-aix4.3.2.0 system to build a library written
Title: RE: Problem on rs6000-ibm-aix4.3.2.0 (Fortran)
Steve,
I will look into this, but FYI, -DPIC should not be passed when
compiling Fortran.
Thanks,
Robert
-Original Message-
From: Steve Edwards [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 15, 2003 1:03 PM
To: [EMAIL
I have just run into problems trying to use libtool on a
rs6000-ibm-aix4.3.2.0 system to build a library written in Fortran with
the IBM compiler xlf/xlf90.
There is an immediate compilation failure stating:
xlf90: 1501-210 command option P contains an incorrect subargument
libtool appears to in
29 matches
Mail list logo
