[MacPorts] #16888: sbcl-1.0.21 Build fails

MacPorts noreply at macports.org
Sun Nov 23 07:49:42 PST 2008


#16888: sbcl-1.0.21 Build fails
-------------------------------------------------------+--------------------
 Reporter:  mforbes@…                                  |       Owner:  gwright@…           
     Type:  defect                                     |      Status:  assigned            
 Priority:  Normal                                     |   Milestone:  Port Bugs           
Component:  ports                                      |     Version:  1.6.0               
 Keywords:  sbcl x86_thread_state32_t x86-darwin-os.c  |        Port:  sbcl                
-------------------------------------------------------+--------------------

Comment(by gwright@…):

 Replying to [comment:5 mforbes@…]:
 > Version 2.5 (BuildVersion 2, CFBundleShortVersionString 2.5,
 CFBundleVersion 799, SourceVersion 7990000)
 >
 > The first issue does look like an sbcl problem, but the second issue
 (not finding make.sh after failure) should be fixed at the portfile level.
 If this were fixed, then I could patch the sources manually and continue.
 As it stands, I can patch them manually, but then can't resume the port
 install because of problem 2)
 >
 > Is there any way of including a patch with the portfile?  If so, I could
 write one to tide us over, especially if this is only a problem on Tiger.
 >
 > Has anyone been able to verify this?  I would like to confirm that it is
 not just something strange with my setup.  If so, I will send a report to
 SBCL.
 >

 After a build failure, you need to run

 {{{
 $ sudo port clean sbcl
 }}}

 to cleanly restart the build.  This will take care of the make.sh issue.
 There's no general way to deal with
 failed builds under macports since there are so many different build
 procedures.  Arguably the port command
 should drop a hidden file into the build directory and delete it if the
 build succeeds.  If you ever start
 a build and the hidden file is present, the port command could
 automatically do a clean.

 To include patch files, in the port file you need to add:

 {{{
 patchfiles    <name_of_patchfile>
 }}}

 and create a new directory in the port directory called "files/" which
 will contain the patches.

 If you can send me the patch you want to add, I can make the change to the
 portfile.

-- 
Ticket URL: <http://trac.macports.org/ticket/16888#comment:6>
MacPorts <http://www.macports.org/>
Ports system for Mac OS


More information about the macports-tickets mailing list