On 19 Jul, O'Connor, Daniel wrote:
>
>> On 19 Jul 2015, at 02:56, Simon J. Gerraty wrote:
>>
>> O'Connor, Daniel wrote:
>>> However, Crochet _does_ build on the NFS client _and_ when the
>>> source tree isn't in /usr/src which makes this issue very strange
>>> :-/
>>
>> I've seen similar error
> On 20 Jul 2015, at 11:40, Simon J. Gerraty wrote:
>
> O'Connor, Daniel wrote:
So, it seems MAKEOBJDIRPREFIX only works as an environmental variable
>
>> Weird, I could have sworn I have set it on the command line and had it
>> work, but..
>
> In most "normal" usage you will likely not
O'Connor, Daniel wrote:
> >> So, it seems MAKEOBJDIRPREFIX only works as an environmental variable
> Weird, I could have sworn I have set it on the command line and had it
> work, but..
In most "normal" usage you will likely not notice a difference.
It is only when a makefile is "being clever" t
> On 20 Jul 2015, at 04:29, Simon J. Gerraty wrote:
> O'Connor, Daniel wrote:
>>
>> But this did not..
>> make -j 8 buildworld MAKEOBJDIRPREFIX=/src/obj-amd64
>
> Nor should it.
> There are several makefiles in the tree that expect to be able to
> change MAKEOBJDIRPREFIX in the environment of
O'Connor, Daniel wrote:
> Yeah the subject is wrong (I just updated it).
>
> I just did a build like so and it worked..
> env MAKEOBJDIRPREFIX=/src/obj-amd64 make -j 8 buildworld
That's the right way to use it.
> But this did not..
> make -j 8 buildworld MAKEOBJDIRPREFIX=/src/obj-amd64
Nor sho
> Given that we have (or at least had at one time) some of those magical
> "..." paths that cause bmake to search up the hierarchy for its .mk
> files, I wonder if an odd relationship between src and obj dir confuses
> it, or if it somehow wanders into a wrong src tree while searching?
Based on Da
On Sun, Jul 19, 2015 at 10:31:36AM -0600, Ian Lepore wrote:
>
> I've been following this saga (on irc and here) as much as I have time
> for, and I can't escape the feeling that it is the directory structure
> at fault somehow, but I can't quite put my finger on it.
>
> I never (ever) build f
On Sun, Jul 19, 2015 at 10:24:11AM -0600, Ian Lepore wrote:
> ...
> Was there anything (at all) in /var/log/messages about ntpd? Even the
> routine messages (such as what interfaces it binds to) might give a bit
> of a clue about how far it got in its init before it died.
>
Sorry; there mig
On Sat, 2015-07-18 at 10:26 -0700, Simon J. Gerraty wrote:
> O'Connor, Daniel wrote:
> > However, Crochet _does_ build on the NFS client _and_ when the source
> > tree isn't in /usr/src which makes this issue very strange :-/
>
> I've seen similar errors in rescue... (no NFS) though I cannot
> q
On Sat, 2015-07-18 at 05:09 -0700, David Wolfskill wrote:
> Lousy timing (no pun intended -- it's early in the day for me),
> given the recent MFC, but as I was booting my laptop to yesterday's
> head:
>
> FreeBSD g1-245.catwhisker.org 11.0-CURRENT FreeBSD 11.0-CURRENT #127
> r285652M/285652:110
Hi there,
I'm using the latest CURRENT image they're updated not long ago.
It somehow manages to pull the right drivers to get X working. :)
Thanks for the suggestion.
El lun., 13 jul. 2015 a las 13:15, Daniel Peyrolon ()
escribió:
> Hi,
>
> > what about PCBSD?
> Probably should have said somet
> On 19 Jul 2015, at 02:56, Simon J. Gerraty wrote:
>
> O'Connor, Daniel wrote:
>> However, Crochet _does_ build on the NFS client _and_ when the source
>> tree isn't in /usr/src which makes this issue very strange :-/
>
> I've seen similar errors in rescue... (no NFS) though I cannot
> quite
12 matches
Mail list logo
