Opened 12 years ago

Closed 12 years ago

#31635 closed defect (fixed)

xattr fails to build with latest version of xcode due to depricated -buildstyle switch

Reported by: pkutzner+macports@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 2.0.3
Keywords: Cc: macports@…
Port: xattr

Description (last modified by ryandesign (Ryan Carsten Schmidt))

xattr will not build due to the -buildstyle switch being removed from xcode in the most recent update. Build fails with the following text:

shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_sysutils_xattr/xattr/work/eXttra" && /usr/bin/xcodebuild  -project "eXttra.xcode" -target "xattr"  -buildstyle Deployment " returned error 64
Error: Target org.macports.build returned: shell command failed (see log for details)
Warning: the following items did not execute (for xattr): org.macports.activate org.macports.build org.macports.destroot org.macports.install
Log for xattr is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_sysutils_xattr/xattr/main.log
Error: Status 1 encountered during processing.

Attachments (1)

main.log (5.4 KB) - added by pkutzner+macports@… 12 years ago.
Build log for xattr failing to build under latest xcode tools

Download all attachments as: .zip

Change History (7)

Changed 12 years ago by pkutzner+macports@…

Attachment: main.log added

Build log for xattr failing to build under latest xcode tools

comment:1 Changed 12 years ago by pkutzner+macports@…

As an update, here's the full error output to the screen when attempting to build, along with the command used to build. I realized I had only pasted the tail-end of it:

pkutzner@masami:~$ POSIXLY_CORRECT=1 sudo port -v install xattr
Password:
--->  Computing dependencies for xattr.
--->  Building xattr
xcodebuild: error: option '-buildstyle' is no longer supported

Usage: xcodebuild [-project <projectname>] [[-target <targetname>]...|-alltargets] [-configuration <configurationname>] [-arch <architecture>]... [-sdk [<sdkname>|<sdkpath>]] [<buildsetting>=<value>]... [<buildaction>]...
       xcodebuild -workspace <workspacename> -scheme <schemeName> [-configuration <configurationname>] [-arch <architecture>]... [-sdk [<sdkname>|<sdkpath>]] [<buildsetting>=<value>]... [<buildaction>]...
       xcodebuild -version [-sdk [<sdkfullpath>|<sdkname>] [<infoitem>] ]
       xcodebuild -list [[-project <projectname>]|[-workspace <workspacename>]]
       xcodebuild -showsdks
Options:
    -usage                print full usage
    -verbose              provide additional status output
    -project NAME         build the project NAME
    -target NAME          build the target NAME
    -alltargets           build all targets
    -workspace NAME       build the workspace NAME
    -scheme NAME          build the scheme NAME
    -configuration NAME   use the build configuration NAME for building each target
    -xcconfig PATH        apply the build settings defined in the file at PATH as overrides
    -arch ARCH            build each target for the architecture ARCH; this will override architectures defined in the project
    -sdk SDK              use SDK as the name or path of the base SDK when building the project
    -parallelizeTargets   build independent targets in parallel
    -jobs NUMBER          specify the maximum number of concurrent build operations
    -showsdks             display a compact list of the installed SDKs
    -list                 lists the targets and configurations in a project, or the schemes in a workspace
    -find BINARY          display the full path to BINARY in the provided SDK
    -version              display the version of Xcode; with -sdk will display info about one or all installed SDKs
shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_sysutils_xattr/xattr/work/eXttra" && /usr/bin/xcodebuild  -project "eXttra.xcode" -target "xattr"  -buildstyle Deployment " returned error 64
Error: Target org.macports.build returned: shell command failed (see log for details)
Warning: the following items did not execute (for xattr): org.macports.activate org.macports.build org.macports.destroot org.macports.install
Log for xattr is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_sysutils_xattr/xattr/main.log
Error: Status 1 encountered during processing.
To report a bug, see <http://guide.macports.org/#project.tickets>

comment:2 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)

Description: modified (diff)
Keywords: xattr removed

Please remember to use WikiFormatting.

comment:3 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)

Surely the xattr port isn't needed anymore? This was a quick and dirty program created shortly after Tiger was introduced, because Tiger did not include any such program. But surely Leopard, Snow Leopard and Lion have such a program built in? I see a /usr/bin/xattr already installed on my Snow Leopard machine. Give that a try.

comment:4 Changed 12 years ago by macports@…

I confirmed this issue while trying to build xattr today. The reason why I wanted to try the MacPorts version of xattr is that it appears the Apple version is hiding information from the user. The ArsTechnica review of Snow Leopard mentioned that they could see the ACLs for a file on an HFS+ volume (stored as extended attributes) using the Leopard version of xattr, which were not showing when using the Snow Leopard version of xattr. In addition, Amit Singh documents on his site for fileXray (a tool for reading HFS+ metadata) that his tool can "display all extended attributes, including ones that are "special" (normally hidden or actively filtered by the kernel, such as Access Control Lists)". That's great but it's an $80 program, and can only perform read-only access because it is for forensic examiners.

comment:5 Changed 12 years ago by macports@…

Cc: macports@… added

Cc Me!

comment:6 Changed 12 years ago by jmroot (Joshua Root)

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.