List Info

Thread: v2 Python toolset doesn't faithfully reproduce v1




v2 Python toolset doesn't faithfully reproduce v1
user name
2006-07-23 00:05:01
Vladimir Prus <ghostcs.msu.su> writes:

> On Saturday 22 July 2006 15:57, David Abrahams wrote:
>> Vladimir Prus <ghostcs.msu.su> writes:
>> > Yep, we'll end up with two copies of symbols,
but is this going to cause
>> > real problems?
>>
>> Yes.
>
> Are they already summarised somewhere? I've already
changed not to do so, but 
> it would be nicer to have rationale explained
somewhere.

I don't think there's any need for a rationale explaining
why we are
linking with python in the usual way.  It's python.org's
job to
rationalize that if they so choose.

-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build
v2 Python toolset doesn't faithfully reproduce v1
user name
2006-07-23 11:59:30
As a result of yesterday's changes to
tools/build/v2/python.jam,
several python tests are now failing on Solaris.  When
linking with
the Python library, at least on this platform, one needs to
also link
with -lrt to pull in definitions for the sem_* and fdatasync
functions.

The <threading>multi requirement used to pull this in
automatically,
but if I am following this thread correctly, that
requirement was
removed.

See the link errors at http://tinyurl.com/fpedz

-- 
Caleb Epstein
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build
v2 Python toolset doesn't faithfully reproduce v1
user name
2006-07-24 05:22:55
On Sunday 23 July 2006 15:59, Caleb Epstein wrote:
> As a result of yesterday's changes to
tools/build/v2/python.jam,
> several python tests are now failing on Solaris.  When
linking with
> the Python library, at least on this platform, one
needs to also link
> with -lrt to pull in definitions for the sem_* and
fdatasync
> functions.
>
> The <threading>multi requirement used to pull
this in automatically,
> but if I am following this thread correctly, that
requirement was
> removed.
>
> See the link errors at http://tinyurl.com/fpedz

Hi Caleb,

I've realized this can happen, but only late on Saturday,
when off-line. I'll 
roll a fix today.

Sorry,
Volodya


_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build
v2 Python toolset doesn't faithfully reproduce v1
user name
2006-07-24 06:16:34
On Sunday 23 July 2006 15:59, Caleb Epstein wrote:
> As a result of yesterday's changes to
tools/build/v2/python.jam,
> several python tests are now failing on Solaris.  When
linking with
> the Python library, at least on this platform, one
needs to also link
> with -lrt to pull in definitions for the sem_* and
fdatasync
> functions.
>
> The <threading>multi requirement used to pull
this in automatically,
> but if I am following this thread correctly, that
requirement was
> removed.

Caleb,
should be fixed now, can you verify things are back to
normal for you?

Thanks,
Volodya
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build
v2 Python toolset doesn't faithfully reproduce v1
user name
2006-07-26 02:18:06
On 7/24/06, Vladimir Prus <ghostcs.msu.su> wrote:

> should be fixed now, can you verify things are back to
normal for you?

Nope.  See http://tinyurl.com/fpedz
.  We are still missing -lrt in
the link line.

I believe the reason this configuration
(gcc-4.1.1_sunos_i86pc) fails
and my gcc-3.4.3-sunos configuration does not is that the
gcc-3.4.3-sunos libPython is a shared library dynamically
linked with
librt.so.  The gcc-4.1.1 setup is using a static libPython,
so -lrt it
is required at link time.  I no longer have access to the
gcc-3.4.3-sunos machine to verify this, though, and I will
need to
have that machine discontinue regression tests once
RC_1_34_0 is out
the door

Adding -lrt in when linking with libPython on Solaris should
solve the problem.

-- 
Caleb Epstein
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build
v2 Python toolset doesn't faithfully reproduce v1
user name
2006-07-26 08:53:58
On Wednesday 26 July 2006 06:18, Caleb Epstein wrote:
> On 7/24/06, Vladimir Prus <ghostcs.msu.su> wrote:
> > should be fixed now, can you verify things are
back to normal for you?
>
> Nope.  See http://tinyurl.com/fpedz
.  We are still missing -lrt in
> the link line.
>
> I believe the reason this configuration
(gcc-4.1.1_sunos_i86pc) fails
> and my gcc-3.4.3-sunos configuration does not is that
the
> gcc-3.4.3-sunos libPython is a shared library
dynamically linked with
> librt.so.  The gcc-4.1.1 setup is using a static
libPython, so -lrt it
> is required at link time.  I no longer have access to
the
> gcc-3.4.3-sunos machine to verify this, though, and I
will need to
> have that machine discontinue regression tests once
RC_1_34_0 is out
> the door
>
> Adding -lrt in when linking with libPython on Solaris
should solve the
> problem.

Can you tell me the value of jam's JAMUNAME variable on 4.1
config? You can 
get it with:

   bjam -f-
   ECHO $(JAMUNAME) ;
   <Ctrl-D>

Thanks,
Volodya


_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build
v2 Python toolset doesn't faithfully reproduce v1
user name
2006-07-26 19:25:23
On 7/26/06, Vladimir Prus <ghostcs.msu.su> wrote:

> Can you tell me the value of jam's JAMUNAME variable
on 4.1 config? You can
> get it with:
>
>    bjam -f-
>    ECHO $(JAMUNAME) ;
>    <Ctrl-D>

Nope.

% bjam -f-
ECHO $(JAMUNAME)
(Ctrl-D here)
syntax error at EOF
don't know how to make all
...found 1 target...
...can't find 1 target...

Do I need to run this from any particular directory?

-- 
Caleb Epstein
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build
v2 Python toolset doesn't faithfully reproduce v1
user name
2006-07-26 19:31:01
Caleb Epstein wrote:
> On 7/26/06, Vladimir Prus <ghostcs.msu.su> wrote:
> 
>> Can you tell me the value of jam's JAMUNAME
variable on 4.1 config? You can
>> get it with:
>>
>>    bjam -f-
>>    ECHO $(JAMUNAME) ;
>>    <Ctrl-D>
> 
> Nope.
> 
> % bjam -f-
> ECHO $(JAMUNAME)
> (Ctrl-D here)
> syntax error at EOF
> don't know how to make all
> ...found 1 target...
> ...can't find 1 target...
> 
> Do I need to run this from any particular directory?

You forgot the " ;" at the end of the echo line.


-- 
-- Grafik - Don't Assume Anything
-- Redshift Software, Inc. - http://redshift-software
.com
-- rrivera/acm.org - grafik/redshift-software.com
-- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build
v2 Python toolset doesn't faithfully reproduce v1
user name
2006-07-26 19:45:23
On 7/26/06, Rene Rivera <grafikrobotgmail.com> wrote:
> >>    ECHO $(JAMUNAME) ;
> > ECHO $(JAMUNAME)
>
> You forgot the " ;" at the end of the echo
line.

Whoops, thats what I get for not copying & pasting. 
Here's the output:

SunOS moma 5.10 Generic_Patch_118844-30 i86pc

-- 
Caleb Epstein
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build
v2 Python toolset doesn't faithfully reproduce v1
user name
2006-07-27 05:29:56
On Wednesday 26 July 2006 23:25, Caleb Epstein wrote:
> On 7/26/06, Vladimir Prus <ghostcs.msu.su> wrote:
> > Can you tell me the value of jam's JAMUNAME
variable on 4.1 config? You
> > can get it with:
> >
> >    bjam -f-
> >    ECHO $(JAMUNAME) ;
> >    <Ctrl-D>
>
> Nope.
>
> % bjam -f-
> ECHO $(JAMUNAME)

I think you forgot to type <space><semicolon>
there, as written in my 
email 

- Volodya
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build
[1-10] [11-20] [21]

about | contact  Other archives ( Real Estate discussion Medical topics )