On Tue, Dec 07, 2010 at 05:13:19PM -0600, robert wrote:
>
> In other matters, I'm setting up another machine to step thru the LFS
> build ... don't know what else to do.
Since your at an impasse here , why not try installing udev and if
it fails to install get a copy of the MAKDEV script , c
robert wrote:
> Ken Moffat wrote:
>> On Tue, Dec 07, 2010 at 01:36:31PM -0600, robert wrote:
>>> So, I don't follow then. Instructions at > 6.59. Udev-161
>>> say: tar -xvf ../udev-config-20100128.tar.bz2 ...
>>> why not *J*xvf?
>> Apart from the other responses, I can't help commenting that 'J'
Ken Moffat wrote:
> On Tue, Dec 07, 2010 at 05:13:19PM -0600, robert wrote:
>> Ken Moffat wrote:
>>> Apart from the other responses, I can't help commenting that 'J' is
>>> not 'j'. I assume you wrote it as a capital for more emphasis, but
>>> with the last two or three releases of tar 'J' is use
On Tue, Dec 07, 2010 at 05:13:19PM -0600, robert wrote:
> Ken Moffat wrote:
> >
> > Apart from the other responses, I can't help commenting that 'J' is
> > not 'j'. I assume you wrote it as a capital for more emphasis, but
> > with the last two or three releases of tar 'J' is used for xz
> > com
Ken Moffat wrote:
> On Tue, Dec 07, 2010 at 01:36:31PM -0600, robert wrote:
>> So, I don't follow then. Instructions at > 6.59. Udev-161
>> say: tar -xvf ../udev-config-20100128.tar.bz2 ...
>> why not *J*xvf?
>
> Apart from the other responses, I can't help commenting that 'J' is
> not 'j'. I a
On Tue, Dec 07, 2010 at 01:36:31PM -0600, robert wrote:
>
> So, I don't follow then. Instructions at > 6.59. Udev-161
> say: tar -xvf ../udev-config-20100128.tar.bz2 ...
> why not *J*xvf?
Apart from the other responses, I can't help commenting that 'J' is
not 'j'. I assume you wrote it as a ca
On Tue, Dec 7, 2010 at 2:07 PM, Neal Murphy wrote:
> On Tuesday 07 December 2010 14:53:10 Bruce Dubbs wrote:
>> When extracting, GNU tar is smart enough to recognize the compression
>> type, if any, without being told. This capability has been in place for
>> several years.
>
> Learn something ne
On Tuesday 07 December 2010 14:53:10 Bruce Dubbs wrote:
> When extracting, GNU tar is smart enough to recognize the compression
> type, if any, without being told. This capability has been in place for
> several years.
Learn something new every day! I've been using the specific option for so
lon
Bruce Dubbs wrote:
> robert wrote:
>> Neal Murphy wrote:
>>> On Tuesday 07 December 2010 04:55:43 robert wrote:
unpacked udev-161.tar.bz2
cd udev-161
then copy and paste ... (the two dearchive operations are "xvf"??? and
not "jxvf"???
>>> 'tar xvf' unpacks a noncompressed tar a
robert wrote:
> Neal Murphy wrote:
>> On Tuesday 07 December 2010 04:55:43 robert wrote:
>>> unpacked udev-161.tar.bz2
>>> cd udev-161
>>> then copy and paste ... (the two dearchive operations are "xvf"??? and
>>> not "jxvf"???
>> 'tar xvf' unpacks a noncompressed tar archvie (.tar).
>> 'tar xvfj'
Mike Hollis wrote:
> On Tue, Dec 07, 2010 at 03:55:43AM -0600, robert wrote:
>>> Mike H.-
>> jumped back out to "root" user
>> asserted root:root for /tools (verified)
>>
>> still at "root":
>> copy and paste everything from 6.2 thru 6.6
>>
>> now in chroot ...
>> move over to 6.59 and ...
Neal Murphy wrote:
> On Tuesday 07 December 2010 04:55:43 robert wrote:
>> unpacked udev-161.tar.bz2
>> cd udev-161
>> then copy and paste ... (the two dearchive operations are "xvf"??? and
>> not "jxvf"???
>
> 'tar xvf' unpacks a noncompressed tar archvie (.tar).
> 'tar xvfj' unpacks a bz2-compre
On Tuesday 07 December 2010 04:55:43 robert wrote:
> unpacked udev-161.tar.bz2
> cd udev-161
> then copy and paste ... (the two dearchive operations are "xvf"??? and
> not "jxvf"???
'tar xvf' unpacks a noncompressed tar archvie (.tar).
'tar xvfj' unpacks a bz2-compressed archive (.tar.bz2).
'tar x
On Tue, Dec 07, 2010 at 03:55:43AM -0600, robert wrote:
> >
> > Mike H.-
>
> jumped back out to "root" user
> asserted root:root for /tools (verified)
>
> still at "root":
> copy and paste everything from 6.2 thru 6.6
>
> now in chroot ...
> move over to 6.59 and ...
> unpacked udev-16
just did the build at host level:
works fine.
any suggestions?
[X] make check
make --no-print-directory check-recursive
Making check in .
make --no-print-directory libudev/test-libudev udev/test-udev
CC libudev/test-libudev.o
CCLD libudev/test-libudev
CC udev/test-udev.o
CC
Mike Hollis wrote:
> On Mon, Dec 06, 2010 at 08:39:13PM -0600, robert wrote:
>> Bruce Dubbs wrote:
>>> robert wrote:
>>>
Does this mean, then, that I am supposed to receive the message:
FAIL: test/udev-test.pl
>>> Do you have the filesystems mounted in the chroot environment? (Section
>>
16 matches
Mail list logo
