Hello;
I'm attempting create a FreeBSD port from an application that was
developed mainly for linux. The original author did use autoconf so
this will make porting easier.
One problem that I'm having trouble solving is that the configure
script fails with the following error:
checking for a BSD
Hi;
On Thu, Apr 30, 2009 at 01:50, Philip Herron
wrote:
> What i would do is maby take a look inside his configure.ac to figure
> out what he is checking for. And maby see why/how to fix it :). Like
> look for the macro that checks for that specific feature in the shell
> or otherwise.
>
That's
On Thu, Apr 30, 2009 at 06:56, Patrick Welche wrote:
> On Thu, Apr 30, 2009 at 12:44:48AM -0700, Joey Mingrone wrote:
>> checking for a BSD-compatible install... /usr/local/bin/ginstall -c
>> checking whether build environment is sane... configure: error: ls -t
>> appear
Hello Ralf;
On Thu, Apr 30, 2009 at 10:35, Ralf Wildenhues wrote:
> Please check whether the files in the package tarball had time stamps in
> the future (relative to the time when you were building). In that case,
> it may be the distributor's system clock that is wrong.
They seem OK. All the
Hi Eric;
On Thu, Apr 30, 2009 at 12:23, Eric Blake wrote:
> Your ls version is trying to output colors, even though it is in a
> non-interactive context. Almost like using GNU 'ls --color=always'
> instead of the recommended 'ls --color=auto', except that you said it
> wasn't GNU ls. Are you su
Hello;
I'm still working on the FreeBSD port I wrote about a few days ago.
I think the last main hurdle is to get the gettext catalog files to
install in /usr/local/share/locale/ instead of the default
/usr/local/lib/locale/ (when configure is run with no arguments).
Even when I run:
./configur
en I hardcode the value for parcellitelocaledir to
/usr/local/share/locale I see changes in the make output to show
...-DPARCELLITELOCALEDIR=/usr/local/share/locale, but the files still
end up getting installed in /usr/local/lib/locale.
Joey
On Tue, May 5, 2009 at 12:55, Joey Mingrone wrote:
> Hell
Problem solved.. sort of. In case anyone else runs into this problem,
see: http://bugzilla.gnome.org/show_bug.cgi?id=563034
Joey
On Tue, May 5, 2009 at 17:22, Joey Mingrone wrote:
> A bit more information from my earlier post below...
>
> The relevant parts of the author's config
