Why? And probably an equally stooopid question, “how do I get around it?”
Cheers,
-RK
–
Robert Krten, PARSE Software Devices +1 613 599 8316.
Realtime Systems Architecture, Consulting and Training at www.parse.com
Email my initials at parse dot com.
Why? And probably an equally stooopid question, “how do I get around it?”
Cheers,
-RK
–
Robert Krten, PARSE Software Devices +1 613 599 8316.
Realtime Systems Architecture, Consulting and Training at > www.parse.com
Email my initials at parse dot com.
Uninstall the DDKs, they have a bug in the packaging that makes /usr/include and /usr/lib readonly.
Buh… buh… BUT I need the DDKs! sob whine moan…
So I found where /usr/include hung in the pkg repository and made that directory root
writeable…
Undocumented, wicked, and probably evil, too - but it worked!
I know that the pkg-mangler (or pkg-mugger - Help me Rob, how do you pronounce mgr?) is supposed to
be helping me do something - It’s just at times like this I keep forgetting what problem it solves!
Why? And probably an equally stooopid question, “how do I get around it?”
Cheers,
-RK
–
Robert Krten, PARSE Software Devices +1 613 599 8316.
Realtime Systems Architecture, Consulting and Training at > www.parse.com
Email my initials at parse dot com.
Uninstall the DDKs, they have a bug in the packaging that makes
/usr/include and /usr/lib readonly.
Buh… buh… BUT I need the DDKs! sob whine moan…
So I found where /usr/include hung in the pkg repository and made that directory root
writeable…
Undocumented, wicked, and probably evil, too - but it worked!
I know that the pkg-mangler
(or pkg-mugger - Help me Rob, how do you pronounce mgr?)