[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-bugs-dist
Subject: [Bug 55371] New: kdebase ./configure doesn't always use KDEDIR variable for default prefix
From: Razathorn <raz () chewies ! net>
Date: 2003-03-01 9:10:23
[Download RAW message or body]
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
http://bugs.kde.org/show_bug.cgi?id=55371
Summary: kdebase ./configure doesn't always use KDEDIR variable
for default prefix
Product: kwin
Version: unspecified
Platform: Compiled Sources
OS/Version: Solaris
Status: UNCONFIRMED
Severity: crash
Priority: NOR
Component: general
AssignedTo: kwin@kde.org
ReportedBy: raz@chewies.net
Version: kdebase 3.1 (using KDE KDE 3.1)
Installed from: Compiled From Sources
Compiler: gcc 3.2.2 solaris 8 32bit compile
OS: Solaris
Sorry... this is not kwin specific... but there was no category for "kdebase". \
Here's the scoop: I have a solaris 8 machine. I ./configured with only \
--disable-java or something like that. I did not use --prefix. KDEDIR var is set to \
/opt/kde-3.1. When I ./configure --help, prefix defaults to /opt/kde-3.1. When i \
ran make install after build, half the stuff went to /opt/kde-3.1, the other half (or \
at least a load of stuff) went into /usr/local. I looked at the top level makefile \
and sure enough, prefix was set to /usr/local.
I am wondering if this is just an autoconf/automake bug... considering I did not \
build from cvs, shouldn't the configure script be created allready and 'not affected \
by my autoconf etc'. If not, just in case.. I am running the following autoconf / \
automake:
autoconf (GNU Autoconf) 2.57
automake (GNU automake) 1.7.2
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic