Gentoo and Lightscribe?

[xathin]

I have all the AMD64 stuff installed, and I'm trying to use the latest version, but it won't install anything. All I get is a block error from portage.

Code: Select all

# emerge -av lightscribe

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild  NS   ] sys-devel/gcc-3.3.6-r1  USE="fortran gtk nls (-altivec) -bootstrap -boundschecking -build -doc -gcj (-hardened) -ip28 -ip32r10k (-multilib) -multislot (-n32) (-n64) -nocxx -nopie -nossp -objc -test -vanilla" 23,534 kB [0]
[ebuild  N    ] virtual/libstdc++-3.3  0 kB [0]
[ebuild  N F  ] app-cdr/lightscribe-1.8.13.1  USE="-sdk" 520 kB [1]
[blocks B     ] =sys-devel/gcc-3.3* (is blocking app-emulation/emul-linux-x86-compat-1.0-r3)

Total: 3 packages (2 new, 1 in new slot, 1 block), Size of downloads: 24,053 kB
Fetch Restriction: 1 package (1 unsatisfied)
Portage tree and overlays:
 [0] /usr/portage
 [1] /usr/portage/local/layman/wschlich-testing

!!! Error: The above package list contains packages which cannot be installed
!!!        at the same time on the same system.

For more information about Blocked Packages, please refer to the following
section of the Gentoo Linux x86 Handbook (architecture is irrelevant):

http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?full=1#blocked

I have the emul-linux-x86-compat package installed, but the ebuilds don't make any mention of it.

[desultory]

It is specified in emul-linux-x86-compat-1.0-r3.ebuild.

Code: Select all

RDEPEND="!=sys-devel/gcc-3.3*"

[xathin]

It is specified in emul-linux-x86-compat-1.0-r3.ebuild.

Code: Select all

RDEPEND="!=sys-devel/gcc-3.3*"

I understand what the blocking of a package means. But others have said that it works on their amd64 systems. What has to be set to get it to install on amd64?

Do I have to make my own ebuild to make it amd64 compatible?

[desultory]

I understand what the blocking of a package means.

In your earlier post you indicated that you were unable to find, in the ebuilds, the reason for the package block, hence my response.

What has to be set to get it to install on amd64?

The most obvious approaches would be to mask app-emulation/emul-linux-x86-compat-1.0-r3, or to remove any 3.3 series versions of sys-devel/gcc from the system.

Do I have to make my own ebuild to make it amd64 compatible?

That is unlikely.

[xathin]

What has to be set to get it to install on amd64?

The most obvious approaches would be to mask app-emulation/emul-linux-x86-compat-1.0-r3, or to remove any 3.3 series versions of sys-devel/gcc from the system.

The problem with removing/not using sys-devel/gcc-3.3* is it's required by app-cdr/lightscribe, through virtual/libstdc++, which is why I was having the problem.

If I understand the usage of the app-emulation/emul-linux-x86-compat from the description,

Code: Select all

emul-linux-x86 version of lib-compat, with the addition of a 32bit libgcc_s and the libstdc++ versions provided by gcc 3.3 and 3.4 for non-multilib systems.

it should include the necessary libraries that libstdc++ requires (please correct if I'm wrong). If this is true, should it not be required to have either the app-emulation/emul-linux-x86-compat or the virtual/libstdc++? And would it not be better to have the emul-linux-x86-compat for amd64?

The ebuild for app-cdr/lightscribe from the overlay does not have any support for amd64. The keywords are "-amd64 ~x86", which would mean that I would need to install it under the x86, not amd64. This would also mean that the dependencies of the package would not include any of the amd64 emulation packages.

If I am totally off base with this, please correct me. If there is a different ebuild for amd64, could someone let me know where I can get it?

[svf]

Thanks! everything's fine here with 4l-gui, LG and fluxbox on amd64.

[Sperlock]

Version 1.8.15.1 is out now. I'm guessing I will have to wait for Wschlich to update the overlay?

[96140]

No need to modify anything for amd64. Especially don't modify the keywords! -amd64 is perfectly valid; you just need to put -amd64 after the appropriate lightscribe ebuilds in /etc/portage/package.keywords, just as you would with any other atom, like ~. This is all explained in the Portage handbooks.

The existing ebuild works just fine on my amd64 machine. If you're having problems, it's not because of the ebuild! I strongly recommend against modifying it.

[woodwizzle]

I ran
layman -S
layman -a wschlich-testing
but emerge search lightscribe still comes up nothing. What am I doing wrong?

[oRo]

I ran
layman -S
layman -a wschlich-testing
but emerge search lightscribe still comes up nothing. What am I doing wrong?

Get a look at /etc/make.conf

Code: Select all

echo "source /usr/portage/local/layman/make.conf" >> /etc/make.conf

By the way, SimpleLabeler still get a segfault
I ran it under gdb and I get this

...
(no debugging symbols found)
Using /etc/lightscribe.rc

Program received signal SIGSEGV, Segmentation fault.
0xb7460d2c in ?? () from /usr/lib/libstdc++-v3/libstdc++.so.5
(gdb)

And if I ask for backtrace, I get this :

(gdb) bt
#0 0xb7460d2c in ?? () from /usr/lib/libstdc++-v3/libstdc++.so.5
#1 0xb7460d3f in ?? () from /usr/lib/libstdc++-v3/libstdc++.so.5
#2 0xb7460d3f in ?? () from /usr/lib/libstdc++-v3/libstdc++.so.5
#3 0xb7460d3f in ?? () from /usr/lib/libstdc++-v3/libstdc++.so.5
#4 0xb7460d3f in ?? () from /usr/lib/libstdc++-v3/libstdc++.so.5
#5 0xb7460d3f in ?? () from /usr/lib/libstdc++-v3/libstdc++.so.5
#6 0xb7460d3f in ?? () from /usr/lib/libstdc++-v3/libstdc++.so.5
#7 0xb7460d3f in ?? () from /usr/lib/libstdc++-v3/libstdc++.so.5
#8 0xb7460d3f in ?? () from /usr/lib/libstdc++-v3/libstdc++.so.5
#9 0xb7460d3f in ?? () from /usr/lib/libstdc++-v3/libstdc++.so.5
#10 0xb7460d3f in ?? () from /usr/lib/libstdc++-v3/libstdc++.so.5
#11 0xb7460d3f in ?? () from /usr/lib/libstdc++-v3/libstdc++.so.5
#12 0xb7460d3f in ?? () from /usr/lib/libstdc++-v3/libstdc++.so.5
#13 0xb7460d3f in ?? () from /usr/lib/libstdc++-v3/libstdc++.so.5
#14 0xb7460d3f in ?? () from /usr/lib/libstdc++-v3/libstdc++.so.5
#15 0xb7460d3f in ?? () from /usr/lib/libstdc++-v3/libstdc++.so.5
#16 0xb7460d3f in ?? () from /usr/lib/libstdc++-v3/libstdc++.so.5
#17 0xb7460d3f in ?? () from /usr/lib/libstdc++-v3/libstdc++.so.5
#18 0xb7460d3f in ?? () from /usr/lib/libstdc++-v3/libstdc++.so.5
#19 0xb7460d3f in ?? () from /usr/lib/libstdc++-v3/libstdc++.so.5
#20 0xb7460d3f in ?? () from /usr/lib/libstdc++-v3/libstdc++.so.5
#21 0xb7460d3f in ?? () from /usr/lib/libstdc++-v3/libstdc++.so.5
#22 0xb7460d3f in ?? () from /usr/lib/libstdc++-v3/libstdc++.so.5
...

undefinitly

I tried to re-emerge virtual/libstdc++ but still get segfault
I tried to use LaCie LightScribe Labeler :

Kenza 4L # ./4L-cli
Using /etc/lightscribe.rc
Missing subcommand
Usage:
4L-cli enumerate

4L-cli update

4L-cli version

4L-cli open <drive_path>

4L-cli close <drive_path>

4L-cli mediainfo <drive_path>

4L-cli printinfo [-q <best|medium|draft>] [-m <title|content|full>] <drive_path>

4L-cli preview [-q <best|medium|draft>] [-g] [-s <fit_auto|fit_height|fit_width|no_fit|DPI>]
[-o <output_file>] [-p <preview_size>] [-m <title|content|full>] <drive_path> <input_image>

4L-cli print [-q <best|medium|draft>] [-g] [-s <fit_auto|fit_height|fit_width|no_fit|DPI>]
[-m <title|content|full>] <drive_path> <input_image>

<DPI>: resolution to use for the input image

It works but....

Kenza 4L # ./4L-cli enumerate
Using /etc/lightscribe.rc
Erreur de segmentation

Without source code of Lightscribe...

[Sperlock]

Can version 1.8.13.1 be found anywhere still? Lightscribe only has the current 1.8.15.1 version available.

[oRo]

Can version 1.8.13.1 be found anywhere still? Lightscribe only has the current 1.8.15.1 version available.

I've looked after it but unable to find

[dek]

Yeah, if anyone finds a mirror with lightscribe-1.8.13.1-linux-2.6-intel.rpm, please post a link.

[woodwizzle]

I ran
layman -S
layman -a wschlich-testing
but emerge search lightscribe still comes up nothing. What am I doing wrong?

Get a look at /etc/make.conf

Code: Select all

echo "source /usr/portage/local/layman/make.conf" >> /etc/make.conf

Then I get this error when searching for lightscribe:
!!![Errno 2] No such file or directory: '/usr/portage/local/layman/make.conf' in /etc/make.conf
!!! Incorrect multiline literals can cause this. Do not use them.

[oRo]

Then I get this error when searching for lightscribe:
!!![Errno 2] No such file or directory: '/usr/portage/local/layman/make.conf' in /etc/make.conf
!!! Incorrect multiline literals can cause this. Do not use them.

Strange....

I guess you doesn't have an portage directory "/usr/portage/local/layman" or layman is misconfigurated
Maybe "/usr/local/portage/layman" is your overlay directory ??

Get a look at http://gentoo-wiki.com/TIP_Overlays

[whimmel]

Yeah, if anyone finds a mirror with lightscribe-1.8.13.1-linux-2.6-intel.rpm, please post a link.

I went into the overlay and copied the current ebuild to one named lightscribe-1.8.15.1.ebuild, then I was able to install with emerge -av --digest lightscribe-1.8.15.1 normally..

Unfortunately, I'm still getting the segfault when trying to enumerate the drive.

[Sperlock]

Yeah, if anyone finds a mirror with lightscribe-1.8.13.1-linux-2.6-intel.rpm, please post a link.

I went into the overlay and copied the current ebuild to one named lightscribe-1.8.15.1.ebuild, then I was able to install with emerge -av --digest lightscribe-1.8.15.1 normally..

Unfortunately, I'm still getting the segfault when trying to enumerate the drive.

I tried this but couldn't get it to even install, much less run.

[guerro]

new version of lightscribe:
lightscribe-1.10.13.1-linux-2.6-intel.rpm

Please update ebuild

[oRo]

lightscribe-1.10.13.1-linux-2.6-intel.rpm

After install, and re emerge virtual/libstdc++ && sys-libs/libstdc++-v3, SimpleLabeler work fine

[Morimando]

I modified the ebuild to work with lightscribe-1.10.13.1, but 4L-cli enumerate doesn't recognize my drive
Does anyone know what might be the problem? the drive is a Samsung SH-203B

[lixantrope]

I have successfully installed and used the LaCie lightscribe labeler. I didn't install it from portage, since it is not there, I downloaded the two rpm packages (http://www.lacie.com/download/drivers/l ... -intel.rpm and http://www.lacie.com/download/drivers/4 ... 6.i586.rpm from http://www.lacie.com/products/product.htm?pid=10803).

The installation was almost straightforward, except for a small glitch (it assumes that /usr/lib is your lib dir, which is not true in case of 32-bit apps on a amd64 system). The steps:
0. you need the various emul-linux* packages (I guess the xlibs, baselibs and compat), for the sake of completeness here is the list of my installed emul-linux* packages that could matter:

• app-emulation/emul-linux-x86-baselibs (10.2)
  app-emulation/emul-linux-x86-compat (1.0-r3)
  app-emulation/emul-linux-x86-gtklibs (10.0-r1)
  app-emulation/emul-linux-x86-xlibs (10.0)

1. Install both rpms (either via rpm -i, or convert them via rmp2tgz, then unpack in root directory)
2. LaCie assumes /usr/lib to be the lib directory, but then then running 4L-gui and 4L-cli won't find the libraries.
-copy the lib files to /usr/lib32 (as root):

Code: Select all

cp /usr/lib/liblightscribe.so.1 /usr/lib32/
ln -s /usr/lib32/liblightscribe.so.1 /usr/lib32/liblightscribe.so
cp -r /usr/lib/lightscribe /usr/lib32/

Just moving them is not enough, because updating LaCie will fail later (though hardlinking them should work, alternatively you could use the LD_LIBRARY_PATH env variable).
3. update LaCie (it downloads info about newer CD/DVD writers)

Code: Select all

4L-cli update

4. run enumerating, now your drive should be found if it hasn't been found before the update. Output should look something like this (the line 'Usable: 1' is important, if it is 0, your drive won't be recognized)

Code: Select all

$ 4L-cli enumerate
Using /etc/lightscribe.rc
Drive path: /dev/hda
Usable: 1
Full name: HL-DT-ST DVDRAM GSA-T20L NC08 147
Model: DVDRAM GSA-T20L 
Manufacturer: HL-DT-ST
Capabilities: monochrome 
Drive inner radius: 21000
Drive outer radius: 58700

5. if your drive is recognized, make the 4L-cli and 4L-gui suid

Code: Select all

chmod +s /usr/4L/4L-cli
chmod +s /usr/4L/4L-gui

Alternatively, instead of giving suid permissions to the binaries, you may use sudo (edit /etc/sudoers to allow specific users etc.)
6. just to test it, put in a lightscribe DVD/CD medium and run

Code: Select all

4L-cli mediainfo /dev/your_dvd_or_cd_drive

The output should have a line saying: "Lightscribe media: 1"
7. run 4L-gui and burn the image and have a look at the PDF manual (http://www.lacie.com/download/manual/Li ... nux_en.pdf), it is short and concise

Enjoy

[cpicton]

Here is a way to fix the segmentation fault some people have been experiencing.

From what I have seen, the people using amd64 with the 32 bit compatibility libs are not experiencing problems, but the 32 bit users which have compiled their own glibc/stdc++ are getting the segfault.

What I have done is to take some libraries from ubuntu dapper, and put them in their own dir. I then use the dapper dynamic loader to run lightscribe, but using the different libraries.

You can download lightscribe-libs.tar.bz2 from http://www.tangent.co.za/~chrisp/lights ... bs.tar.bz2

Uncompress them to somewhere (like /home/chrisp/lightscribe)

Create a script as follows:


/home/chrisp/bin/lightscribe

Code: Select all

#!/bin/bash
DIR=/home/chrisp/lightscribe
LD_LIBRARY_PATH=$DIR/lib:$DIR/usr/lib $DIR/lib/ld-linux.so.2 /usr/4L/4L-cli "$@"

This only works for the cli version, but that is all I am using anyway. If you need the gui, you may need to copy more libs from dapper into the directory.

[dony]

Hi all,

I installed the rpm's (rpm2tar; tar) from lacie and it works great with my Asus DRW-1814BL.

lightscribe-1.8.15.1-linux-2.6-intel.rpm
4L-1.0-r6.i586.rpm

The only thing I had to do for my amd64 is to

cp /usr/lib/liblightscribe.so.1 /usr/lib32/liblightscribe.so.1

("emul-linux-x86-xxx" were installed)

Regards

Dony

[yoyo]

Maybe an "ln -s /usr/lib/liblightscribe.so.1 /usr/lib32/liblightscribe.so.1" should do the trick.

BTW, thanks for posting your solution.

Enjoy !

[dony]

You're right - a link is the better Solution ...

FYI: It takes about 15 Min. to "lightscribe" a DVD in best resolution.

Regards

Dony