Issue 16801 - unset HOME breaks python build nastily...
Summary: unset HOME breaks python build nastily...
Status: CLOSED FIXED
Alias: None
Product: Build Tools
Classification: Code
Component: code (show other issues)
Version: OOo 1.1 RC
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: OOo 1.1 RC
Assignee: Martin Hollmichel
QA Contact: issues@tools
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-07-14 09:29 UTC by mmeeks
Modified: 2004-02-07 10:09 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments
patch to allow building without $HOME set (1.15 KB, patch)
2003-07-20 14:44 UTC, joergbudi
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this issue.
Description mmeeks 2003-07-14 09:29:05 UTC
if you unset the HOME environment variable, the OO.o build works perfectly
except for python/ this is particularly annoying for any packages as most Linux
build systems deliberately unset HOME to avoid user-specifics being compiled in.

The error message is obtuse and most unhelpful; it'd be great to fix this before
1.1.

Thanks.
Comment 1 joergbudi 2003-07-20 08:54:03 UTC
Waiting for rc3-branch to commit.
Comment 2 joergbudi 2003-07-20 14:44:55 UTC
Created attachment 7876 [details]
patch to allow building without $HOME set
Comment 3 joergbudi 2003-07-20 14:47:34 UTC
Martin, either commit the patch or give me access rights to do it, I
still get

cvs commit -m "#16801# python can now be built, when HOME variable is
not set" makefile.mk
User jbu doesnt have <Commit> access to an entry in external
Comment 4 Martin Hollmichel 2003-07-21 07:33:43 UTC
committed to ooo11rc3
Comment 5 Martin Hollmichel 2004-02-07 10:07:49 UTC
mark as verified.
Comment 6 Martin Hollmichel 2004-02-07 10:09:50 UTC
close issue.