[M3devel] ROOT

jay.krell at cornell.edu jay.krell at cornell.edu
Thu Jul 2 19:34:55 CEST 2009


How about we put .so files only in lib and not in pkg? Or symlink from  
pkg to lib instead of how it used to be the other way around? Those  
would also fix all this.

  - Jay (phone)

On Jul 2, 2009, at 9:21 AM, Jay <jay.krell at cornell.edu> wrote:

>
> Are you up to date in m3-libs/m3core?
> Lots of builds have succeeded with this..
> It isn't great, but that requirement to build from previous 5.4  
> release..
>
> - Jay
>
> ________________________________
>> From: hosking at cs.purdue.edu
>> To: hosking at cs.purdue.edu
>> Date: Thu, 2 Jul 2009 11:54:51 -0400
>> CC: m3devel at elegosoft.com
>> Subject: Re: [M3devel] ROOT
>>
>> If I define ROOT then I get the following error. I think this all  
>> needs reverting!
>>
>> --- building in SOLgnu ---
>>
>> ignoring ../src/m3overrides
>>
>> "/.gollum/u110/u86/hosking/cm3/m3-sys/cm3/src/m3makefile", line 12:  
>> quake runtime error: unable to copy "~/cm3/m3-libs/m3core/src/unix/ 
>> Common/UnixLink.c" to "./UnixLink.c": errno=2
>>
>> --procedure-- -line- -file---
>> cp_if --
>> include_dir 12 /.gollum/u110/u86/hosking/cm3/m3-sys/cm3/src/ 
>> m3makefile
>> 6 /.gollum/u110/u86/hosking/cm3/m3-sys/cm3/SOLgnu/m3make.args
>>
>> Fatal Error: package build failed
>> n
>>
>> On 2 Jul 2009, at 11:49, Tony Hosking wrote:
>>
>> Where did variable ROOT come from? Do I really need to define it?  
>> Seems broken to me to depend on the source directory structure as  
>> it sets that structure in stone.
>>
>>



More information about the M3devel mailing list