[haiku-bugs] Re: [Haiku] #9547: Building Haiku x86_64 on Haiku x86_64 issues

  • From: "bonefish" <trac@xxxxxxxxxxxx>
  • Date: Thu, 21 Mar 2013 10:48:00 -0000

#9547: Building Haiku x86_64 on Haiku x86_64 issues
-------------------------+----------------------------
   Reporter:  Luposian   |      Owner:  xyzzy
       Type:  bug        |     Status:  assigned
   Priority:  normal     |  Milestone:  R1
  Component:  - General  |    Version:  R1/Development
 Resolution:             |   Keywords:
 Blocked By:             |   Blocking:
Has a Patch:  0          |   Platform:  x86-64
-------------------------+----------------------------

Comment (by bonefish):

 Replying to [comment:5 Luposian]:
 > Do not assume, as an end-user, I automatically know exactly what
 category to position a ticket.  I go with what seems like the closest
 category.   I built the image and I could not copy nor install the files.
 So I naturally assume the build was corrupted.

 When in doubt just leave the component "General".

 > What is Haiku x86_64 classified under?  I assumed it was a branch of the
 R1/A4 code. Was it not?

 x86-64 was originally developed in a branch and merged into the main
 repository master after the last alpha.

 > I will attempt to gather any other missing information as I can.
 >
 >  You want the revision of Haiku x86_64 I used to build the "Haiku64"
 image?  Ok, I'll get that for you.
 >
 >  I got that particular revision as a nightly.
 >
 > I do not recall what revision the image was, after jamming it.  Is there
 a way to find that out?

 If you have pulled the tags `git describe --tags` prints the closest tag.
 `git rev-parse HEAD` gives you the hash of the latest commit (or you can
 get it from the `git log` output). Since I don't think this is build
 system related the information probably isn't relevant.

 > How do I use cp in the terminal?  Haven't done that yet. I'm not a
 "terminal geek" and prefer to do everything at the GUI level, unless
 forced to do otherwise.

 The syntax in this case is `cp <file-to-copy> <destination-directory>`.
 You can drag and drop an entry onto the Terminal window to get its path
 inserted. Please find a file that doesn't copy in Tracker and try to copy
 it with `cp`. The result of this and the syslog are the most interesting
 information ATM.

 BTW, moving to trash is a complete different operation than copying. Let's
 stick to the failing copying please.

--
Ticket URL: <http://dev.haiku-os.org/ticket/9547#comment:8>
Haiku <http://dev.haiku-os.org>
Haiku - the operating system.

Other related posts: