Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 17 Jul 2011 12:07:49 +0200
From:      David Arendt <admin@prnet.org>
To:        bf1783@gmail.com
Cc:        freebsd-questions@FreeBSD.org
Subject:   Re: options used to compile packages
Message-ID:  <1310897269.93980.10.camel@server.intern.prnet.org>
In-Reply-To: <CAGFTUwNXsT%2BY_9KHoT27bvbN5z-N%2B%2BQrnfb%2Buca6CAVTz6u9oA@mail.gmail.com>
References:  <CAGFTUwNXsT%2BY_9KHoT27bvbN5z-N%2B%2BQrnfb%2Buca6CAVTz6u9oA@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Hi,

When I did the test, I used FreeBSD 8.2 amd64 using the ports collection
delivered with this distribution.

Yesterday I did a checkout of the latest ports tree. I compiled bash,
xorg, xfce and gdm using the default options. When trying to login using
gdm, it still complains about a missing keyring pam module. When I
disable keyring support in gdm, gdm runs flawlessly. Therefore I thought
that options used to compile the offical packages might be different. If
default options are used to compile them, it should be a some other
problem. To ensure that my build environment is not polluted, I did this
test on a fresh installation. But anyway it doesn't matter as I have a
workaround.

Thanks for your valuable information,
Bye,
David Arendt

On Sat, 2011-07-16 at 18:12 -0400, b. f. wrote:
> > well I don't actually now which package it was, but I compiled gdm (so
> > it should be one of it's dependencies). A compilation resulted in a non
> > working gdm (something with pam support not found on execution). Upon
> > installing gdm and is dependencies from packages, everything worked
> > correctly. Therefore I thought there might be other default options. I
> > am sorry that I cannot be more precise, but I tried it 2 months ago, so
> > I do not remember exactly. I think I will try it again from scratch with
> > latest ports tree and give you more precise information.
> 
> In addition to the obvious possibilities that your test was faulty, or
> that you somehow polluted your build environment, It is also possible
> that:
> 
> -at least one of your ports was a different version than used in the
> default packages, and had a bug;
> 
> -there was a transient build error;
> 
> or
> 
> -you were using a different version of FreeBSD than that used to build
> the default packages that you used, and there is a problem with one of
> the ports on that version of FreeBSD.
> 
> b.





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1310897269.93980.10.camel>