New Ticket     Tickets     Wiki     Browse Source     Timeline     Roadmap     Ticket Reports     Search

Ticket #25760 (closed defect: fixed)

Opened 4 years ago

Last modified 3 years ago

icu pkgdata fails to backslash space in path

Reported by: hteo@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 1.9.1
Keywords: Cc: srl@…
Port: icu

Description (last modified by ryandesign@…) (diff)

Not sure if this is a macports problem or upstream problem.

My macports working directory resides on a second harddisk, mounted on "/Volumes/Secondary HD". Notice the space in the path. For some reason, pkgdata fails to backslash the space. So for example,

## Makefile for icudt38l created by pkgdata
## from ICU Version 3.8.1

SRCDIR=/Volumes/Secondary HD/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_tex_texlive-bin/work/texlive-20091107-source/libs/icu/icu-build/data/out/build/icudt38l

So when I compile say R, which uses icu, I encounter compile error in the libs/icu/icu-build directory, like the following:

DYLD_LIBRARY_PATH=../stubdata:../lib:../tools/ctestfw:$DYLD_LIBRARY_PATH  MAKEFLAGS= ../bin/pkgdata -O ../data/icupkg.inc -q -c -s /Volumes/Secondary HD/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_tex_texlive-bin/work/texlive-20091107-source/libs/icu/icu-build/data/out/build/icudt38l -d ../lib -M'PKGDATA_LDFLAGS=""' -e icudt38 -T ./out/tmp -p icudt38l -L sicudata -m static "./out/tmp/icudata.lst"
Error opening <HD/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_tex_texlive-bin/work/texlive-20091107-source/libs/icu/icu-build/data/out/build/icudt38l>.
error loading input file lists: U_FILE_ACCESS_ERROR
make: *** [packagedata] Error 2

Change History

comment:1 in reply to: ↑ description ; follow-up: ↓ 2 Changed 4 years ago by ryandesign@…

  • Description modified (diff)

Replying to hteo@…:

My macports working directory resides on a second harddisk

How was this accomplished?

We certainly don't support the MacPorts prefix containing a space; the problem you're experiencing may be an extension of that.

P.S: Don't forget to use WikiFormatting

comment:2 in reply to: ↑ 1 Changed 4 years ago by hteo@…

Replying to ryandesign@…:

Replying to hteo@…:

My macports working directory resides on a second harddisk

How was this accomplished?

We certainly don't support the MacPorts prefix containing a space; the problem you're experiencing may be an extension of that.

I created a directory /Volumes/Secondary HD/macports, and soft-linked it to /opt/local/var/macports.

I did this because my primary boot drive is an SSD. So while the /opt tree still resides on the boot drive, I wanted to keep macports's working directory off the SSD onto the secondary drive.

I understand that it's possible that this may be a generic issue, but I singled out the icu port because of all the ports that I have installed, only 2 so far has this problem (R and texlive). Both used icu, and both encountered compilation errors in the icu part of the code and not anywhere else in the code. So I thought it may be specific to icu. After some debugging, I thought it's a path problem related to pkgdata.

comment:3 follow-up: ↓ 6 Changed 4 years ago by srl@…

I think it's an upstream (ICU) problem. It looks like there just arent' quotes around the -s option (it's probably called from the Makefile). Please file a bug there http://icu-project.org and reference this one.

comment:4 Changed 4 years ago by srl@…

  • Cc srl@… added

Cc Me!

comment:5 Changed 4 years ago by jmr@…

  • Owner changed from macports-tickets@… to nox@…

comment:6 in reply to: ↑ 3 Changed 4 years ago by hteo@…

I've submitted a new ticket at icu-projects: http://bugs.icu-project.org/trac/ticket/7883

comment:7 Changed 3 years ago by jmr@…

  • Owner changed from nox@… to macports-tickets@…

comment:8 Changed 3 years ago by jmr@…

  • Status changed from new to closed
  • Resolution set to fixed

Upstream ticket is marked as fixed in 4.6, and we're at 4.6.1 now.

Note: See TracTickets for help on using tickets.