• Scott Dale Robison (9/9) Nov 20 2004 In trying to build STLport for the latest cd release, I got an error
• dt (7/13) Apr 19 2005 Yes. I downloaded and started using new PSDK, then rebuilt STLport 4.5.3
• Scott Michel (3/14) Apr 26 2005 An even "more valid" fix is to use the STLport 4.6.3 update,

Scott Dale Robison <scott isdr.net> writes:

In trying to build STLport for the latest cd release, I got an error 
message about PAGESIZE 128 being inadequate or some such ...

I found two places in dm.mak that specified -p128 in the lib command and 
changed them to -p256, and building finished to completion.

Is this something anyone has seen? I couldn't find any references to it 
in the newsgroups.

Assuming it is a valid fix, someone might want to consider applying it 
to the dm.mak file in the distributed stlport.zip file.

SDR

"dt" <tinkham ucalgary.ca> writes:

"Scott Dale Robison" <scott isdr.net> wrote in message
news:cnmura$2j23$1 digitaldaemon.com...
 In trying to build STLport for the latest cd release, I got an error
 message about PAGESIZE 128 being inadequate or some such ...

 I found two places in dm.mak that specified -p128 in the lib command and
 changed them to -p256, and building finished to completion.

 Is this something anyone has seen? I couldn't find any references to it
 in the newsgroups.

Yes. I downloaded and started using new PSDK, then rebuilt STLport 4.5.3
supplied on DMC CD, and had EXACTLY the same issues and did exactly what you
did. The resulting STLPort libs were significantly bigger then ones supplied
on cd. I am assuming there is no problem, as it appears to be working.

Doug

Scott Michel <scottm aero.org> writes:

Scott Dale Robison wrote:
 In trying to build STLport for the latest cd release, I got an error 
 message about PAGESIZE 128 being inadequate or some such ...
 
 I found two places in dm.mak that specified -p128 in the lib command and 
 changed them to -p256, and building finished to completion.
 
 Is this something anyone has seen? I couldn't find any references to it 
 in the newsgroups.
 
 Assuming it is a valid fix, someone might want to consider applying it 
 to the dm.mak file in the distributed stlport.zip file.

An even "more valid" fix is to use the STLport 4.6.3 update, 
http://mordred.cs.ucla.edu/STLport_DMC/