On Monday 15 October 2012 04:35:09 Gregory M. Turner wrote:
On 10/14/2012 9:29 PM, Mike Frysinger wrote:
Python clearly has an amazing community, so I hate to say anything
negative... but I sometimes wish they would build less and buy more.
build systems are hard to get right. python is in
On 10/14/2012 9:29 PM, Mike Frysinger wrote:
On Sunday 14 October 2012 04:49:28 Gregory M. Turner wrote:
Thirdly has been addressed ad nauseam in this thread and will be
solved by prepending the LDFLAG rather than appending, or, preferably,
by patching autotools (but only if I can find a
On Monday 15 October 2012 04:35:09 Gregory M. Turner wrote:
On 10/14/2012 9:29 PM, Mike Frysinger wrote:
On Sunday 14 October 2012 04:49:28 Gregory M. Turner wrote:
Thirdly has been addressed ad nauseam in this thread and will be
solved by prepending the LDFLAG rather than appending, or,
On 10/12/2012 4:03 AM, Gregory M. Turner wrote:
First, something puts in all kinds of inappropriate amd64 multilib paths
(this ends up being harmless as wrong-arch libraries get rejected at
link-time and treated as non-matches for -lclauses... still, WTF?).
Secondly, something puts the built-in
On Sunday 14 October 2012 04:49:28 Gregory M. Turner wrote:
Thirdly has been addressed ad nauseam in this thread and will be
solved by prepending the LDFLAG rather than appending, or, preferably,
by patching autotools (but only if I can find a simple, low-maintenance
approach that is likely to
On 10/11/2012 2:40 PM, Marien Zwart wrote:
I'm going to do something potentially rude and comment on this without
having read the entire thread.
On Thu, Oct 11, 2012 at 10:39 PM, Gregory M. Turner g...@malth.us wrote:
Anyhow one thing I have figured out is how things can work correctly on
On 10/10/2012 9:14 PM, Mike Frysinger wrote:
On Wednesday 10 October 2012 23:37:26 Gregory M. Turner wrote:
(1) is worse than (2), but it does have some quasi-legitimate usages.
For example, prefix bootstrap does this (or used to), as do many of the
crossdev-wrapper scripts. I've also resorted
On Thursday 11 October 2012 05:35:21 Gregory M. Turner wrote:
On 10/10/2012 9:14 PM, Mike Frysinger wrote:
On Wednesday 10 October 2012 23:37:26 Gregory M. Turner wrote:
(1) is worse than (2), but it does have some quasi-legitimate usages.
For example, prefix bootstrap does this (or used
On 10/11/2012 8:50 AM, Mike Frysinger wrote:
On Thursday 11 October 2012 05:35:21 Gregory M. Turner wrote:
On 10/10/2012 9:14 PM, Mike Frysinger wrote:
it's not particularly important, but on one hand, the LDFLAGS parsing logic
should not be in the tree ever.
I've no major attachment to it.
I'm going to do something potentially rude and comment on this without
having read the entire thread.
On Thu, Oct 11, 2012 at 10:39 PM, Gregory M. Turner g...@malth.us wrote:
Anyhow one thing I have figured out is how things can work correctly on
Linux wihtout -L.: on Linux, the python plugins
On 10/6/2012 1:31 AM, Fabian Groffen wrote:
On 06-10-2012 00:47:57 -0700, Gregory M. Turner wrote:
In dev-lang/python*, we use
append-ldflags '-L.'
to ensure linking is performed against the built libpython.so in-tree,
rather than than in the one in $(libdir). But, this doesn't work if
On Wednesday 10 October 2012 18:47:46 Gregory M. Turner wrote:
+ if [[ ${CHOST} == *-cygwin* ]] ; then
+ fpeconfig=--without-fpectl
just re-use myconf. this is what it's for.
+ myconf=${myconf} ac_cv_func_bind_textdomain_codeset=yes
just export it:
export
On 10/9/2012 2:26 PM, Mike Frysinger wrote:
On Saturday 06 October 2012 03:47:57 Gregory M. Turner wrote:
My god, I am a horrible self-editor. Sorry. Please ignore the magnum
opus above and allow me to try again.
In dev-lang/python*, we use
append-ldflags '-L.'
to ensure linking is
On 10/10/2012 20:37, Gregory M. Turner wrote:
If the Makefiles are building against libraries expected to be in
${PWD}, it seems to me that the Makefiles should know to look there
automatically.
Using the -L . -lfoo is a very bad style in general. Just think what
happen if you're trying to
On Wednesday 10 October 2012 23:37:26 Gregory M. Turner wrote:
(1) is worse than (2), but it does have some quasi-legitimate usages.
For example, prefix bootstrap does this (or used to), as do many of the
crossdev-wrapper scripts. I've also resorted to such usage, myself,
when repairing a
On Saturday 06 October 2012 03:47:57 Gregory M. Turner wrote:
My god, I am a horrible self-editor. Sorry. Please ignore the magnum
opus above and allow me to try again.
In dev-lang/python*, we use
append-ldflags '-L.'
to ensure linking is performed against the built libpython.so
My god, I am a horrible self-editor. Sorry. Please ignore the magnum
opus above and allow me to try again.
In dev-lang/python*, we use
append-ldflags '-L.'
to ensure linking is performed against the built libpython.so in-tree,
rather than than in the one in $(libdir). But, this doesn't
On 06-10-2012 00:47:57 -0700, Gregory M. Turner wrote:
My god, I am a horrible self-editor. Sorry. Please ignore the magnum
opus above and allow me to try again.
In dev-lang/python*, we use
append-ldflags '-L.'
to ensure linking is performed against the built libpython.so in-tree,
Gregory M. Turner posted on Sat, 06 Oct 2012 00:47:57 -0700 as excerpted:
If you tried to read my first post, thanks for not offing yourself like
the guys who get stuck sitting next to Ted Striker in _Airplane!_
It was worth it just for this:
LDFLAGS=-Wl,--engage-warp-engines
19 matches
Mail list logo
