Bug 2015

Summary:	LBE 4.1 fails when building syslinux
Product:	LTSP	Reporter:	Patrick McDonnell <pmcdonnell>
Component:	LTSP Core	Assignee:	Jim McQuillan <jam>
Status:	ASSIGNED ---	QA Contact:
Severity:	major
Priority:	medium	CC:	pmcdonnell
Version:	unspecified
Hardware:	x86 (IA32)
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:
Attachments:	Patch for the install.sh file

Description Patrick McDonnell 2004-12-05 05:53:40 UTC

Upon running ./build_all in the top lbe directory, it works until this part:

package=syslinux
Installing...
changing to: /kernel/kernel_2.4.26
total 6313
drwxr-xr-x    3 0        0             192 Dec  5 03:21 2.4.26-ltsp-1
-rw-r--r--    1 0        0          910746 Dec  5 03:21 bzImage-2.4.26-ltsp-1
-rw-r--r--    1 0        0         1035485 Dec  5 03:21 initrd-2.4.26-ltsp-1.gz
-rw-r--r--    1 0        0         2560000 Dec  5 03:21 initrd.ltsp
-rw-r--r--    1 0        0         1952768 Dec  5 03:21 vmlinuz-2.4.26-ltsp-1
tar (child): Cannot open archive /packages/ltsp-kernel-1.3-0-i386.tgz: No such
file or directory
tar (child): Error is not recoverable: exiting now
../install.sh: line 68:  9924 Broken pipe             tar czf
/packages/${TARBALL} --no-recursion --files-from=${FILELIST}
md5sum: /packages/ltsp-kernel-1.3-0-i386.tgz: No such file or directory
../install.sh: line 73: /packages/ltsp-kernel-1.3-0-i386.ltsp: No such file or
directory
Unable to install syslinux
Unable to build kernel-src:

It appears that tar is looking in the wrong place for the tarball?  This is
Debian "Sarge" Linux, using the LBE 4.1 from CVS.

Comment 1 Patrick McDonnell 2004-12-05 07:41:31 UTC

Created attachment 1476 [details] [review]
Patch for the install.sh file

Comment 2 Patrick McDonnell 2004-12-05 07:42:53 UTC

I found that I could get it to build if I told
lbe/kernel-src/syslinux/install.sh to mkdir the /packages directory.  I've
attached the patch I used.

Comment 3 chemtech 2013-03-15 14:11:04 UTC

Patrick McDonnell 
Do you still experience this issue with newer drivers ?
Please check the status of your issue.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.