From owner-freebsd-ports@FreeBSD.ORG  Sat Apr 10 15:16:38 2004
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id C115A16A4CE
	for <freebsd-ports@freebsd.org>; Sat, 10 Apr 2004 15:16:38 -0700 (PDT)
Received: from cnst.dyns.net (user92.net619.nc.sprint-hsd.net [65.41.40.92])
	by mx1.FreeBSD.org (Postfix) with ESMTP id BEDD143D2D
	for <freebsd-ports@freebsd.org>; Sat, 10 Apr 2004 15:16:37 -0700 (PDT)
	(envelope-from cnst@rbcmail.ru)
Received: from rbcmail.ru (Dell_Inspiron_8100 [192.168.0.1])
	by cnst.dyns.net (8.12.8p1/8.12.8) with ESMTP id i3A5Sjp6028092;
	Sat, 10 Apr 2004 01:28:46 -0400 (EDT)
	(envelope-from cnst@rbcmail.ru)
Message-ID: <40778608.3040505@rbcmail.ru>
Date: Sat, 10 Apr 2004 01:28:40 -0400
From: Constantine <cnst@rbcmail.ru>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB;
	rv:1.6) Gecko/20040113
X-Accept-Language: en-gb, ru, en-us, en
MIME-Version: 1.0
To: freebsd-ports@freebsd.org
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: hard-coded paths
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 10 Apr 2004 22:16:38 -0000

Hello,

I am porting an application that has hard-coded paths for the message 
files. They are defined in the Makefile, but still they are hardcoded in 
the programme. Is there a way to go around this problem? As it is, the 
port will not work on systems with installations different from the one 
of compile time.

I've tried to define relative paths (i.e. ../share/portname), but it 
does not seem to work...

Constantine.