[gentoo-amd64] Re: problems with emerging programs
Richard Fish [EMAIL PROTECTED] posted [EMAIL PROTECTED], excerpted below, on Mon, 25 Sep 2006 17:25:50 -0700: On 9/25/06, Patric Douhane [EMAIL PROTECTED] wrote: That didn't help. But I have some more info on my problem though, found this line when trying to emerge mozilla-firefox: ./loadmsgcat.c: 1295: internal compiler error: Segmentation fault Hope someone can interprete it... Every time I've seen this message on my systems, it has been the result of flakey hardware, particularly memory. Nothing stresses the memory system quite like compiling. If the system works otherwise, I suspect flaky memory timings. Try backing those off (in the BIOS), and see if the problems disappear. And of course, if you are overclocking anything, stop! 100% agreed! I used to have some borderline generic memory, rated pc3200 (400 MHz), that wasn't quite stable at that. The trouble was my machine didn't at that time have a BIOS with memory timing limit capacities, so it was clocked what it was rated and that was that. After suffering with it for awhile, I discovered they had a new BIOS update out which allowed memory timing limits. Setting it to limit @ 183 MHz (DDRed to 366), I guess PC3000, it was stable as a rock, no problems whatsoever, until I upgraded to 8 gig awhile later. Anyway, while it would occasionally freeze the machine, doing whatever, the worst was bunzip2ing and compiling. Those would segfault frequently enough that I had to babysit all my emerges, and learn how to restart in the middle of them instead of starting over. So yes, definitely, if gcc is segfaulting, that's a very strong hint of a hardware problem. Note that memory is one possibility, but another strong candidate is bad power, either due to a bad (or underpowered) computer power supply, or in one case that came up on the lists, an underpowered UPS, or possibly simply bad incoming power. So in addition to checking memory, verify your entire power system, from the wall, thru your UPS (if you don't have one, try one, but make sure it's high enough powered), thru your computer power supply itself. Low power's the equivalent of clocking beyond stable, in that the effect is occasional zeros where there should be ones. And yes, it's gcc and bzip2 (well bunzip2) that seem most sensitive to it. On the bright side, when there was a problem, gcc would segfault or there'd be other errors. I never had an issue with bad builds due to the memory. It either built right, or it failed to complete the build at all. -- Duncan - List replies preferred. No HTML msgs. Every nonfree program has a lord, a master -- and if you use the program, he is your master. Richard Stallman -- gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] Re: problems with emerging programs
Ok that could be it, though I've never noticed that there could be something wrong with the memory before, but I ran Windows XP and perhaps you don't notice such problems then? Can I test my memory with Memtest86?? - Original Message - From: Duncan [EMAIL PROTECTED] To: gentoo-amd64@lists.gentoo.org Sent: Tuesday, September 26, 2006 8:06 AM Subject: [gentoo-amd64] Re: problems with emerging programs Richard Fish [EMAIL PROTECTED] posted [EMAIL PROTECTED], excerpted below, on Mon, 25 Sep 2006 17:25:50 -0700: On 9/25/06, Patric Douhane [EMAIL PROTECTED] wrote: That didn't help. But I have some more info on my problem though, found this line when trying to emerge mozilla-firefox: ./loadmsgcat.c: 1295: internal compiler error: Segmentation fault Hope someone can interprete it... Every time I've seen this message on my systems, it has been the result of flakey hardware, particularly memory. Nothing stresses the memory system quite like compiling. If the system works otherwise, I suspect flaky memory timings. Try backing those off (in the BIOS), and see if the problems disappear. And of course, if you are overclocking anything, stop! 100% agreed! I used to have some borderline generic memory, rated pc3200 (400 MHz), that wasn't quite stable at that. The trouble was my machine didn't at that time have a BIOS with memory timing limit capacities, so it was clocked what it was rated and that was that. After suffering with it for awhile, I discovered they had a new BIOS update out which allowed memory timing limits. Setting it to limit @ 183 MHz (DDRed to 366), I guess PC3000, it was stable as a rock, no problems whatsoever, until I upgraded to 8 gig awhile later. Anyway, while it would occasionally freeze the machine, doing whatever, the worst was bunzip2ing and compiling. Those would segfault frequently enough that I had to babysit all my emerges, and learn how to restart in the middle of them instead of starting over. So yes, definitely, if gcc is segfaulting, that's a very strong hint of a hardware problem. Note that memory is one possibility, but another strong candidate is bad power, either due to a bad (or underpowered) computer power supply, or in one case that came up on the lists, an underpowered UPS, or possibly simply bad incoming power. So in addition to checking memory, verify your entire power system, from the wall, thru your UPS (if you don't have one, try one, but make sure it's high enough powered), thru your computer power supply itself. Low power's the equivalent of clocking beyond stable, in that the effect is occasional zeros where there should be ones. And yes, it's gcc and bzip2 (well bunzip2) that seem most sensitive to it. On the bright side, when there was a problem, gcc would segfault or there'd be other errors. I never had an issue with bad builds due to the memory. It either built right, or it failed to complete the build at all. -- Duncan - List replies preferred. No HTML msgs. Every nonfree program has a lord, a master -- and if you use the program, he is your master. Richard Stallman -- gentoo-amd64@gentoo.org mailing list -- gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] Re: GCC 4 CFLAGS
On Monday 25 September 2006 19:16, Duncan wrote: If you trust me not to pull some weird trick (I wouldn't, but hey, for all you know I'm just some guy on a list, do you know me well enough to trust? I'm not sure I'd trust a guy on the list in your spot, maybe depends on how desperate I was), I have binpkgs of the following gcc versions I could mail you: Thanks anyway, Duncan, but I'm back to a stable 3.4.4 system now. I had to re-solve a problem with gnutls and I had to re-compile the kernel, but for the moment everything's looking solid. I probably ought to leave the GCC upgrade now until I come back from my honeymoon. That does explain why your eselect-compiler could say 4.1.1 yet you were having problems as if it was 3.4.x. If 3.4.x was the only one on your system... But 4.1.1 did exist as well - it must have to compile the kernel with modules that had 4.1.1-magic. I don't know why the emerge process couldn't find it, but I'm sure it was there, or had been at some stage. (After restoring my backup with its 3.4.4 kernel modules, the 4.1.1 kernel in my /boot partition couldn't load those modules at boot time, so I had to boot an older system and recompile the kernel with 3.4.4 GCC. Soon done, but it confirms the presence of gcc-4.1.1.) -- Rgds Peter -- gentoo-amd64@gentoo.org mailing list
[gentoo-amd64] Re: GCC 4 CFLAGS
Peter Humphrey [EMAIL PROTECTED] posted [EMAIL PROTECTED], excerpted below, on Tue, 26 Sep 2006 07:48:54 +: Thanks anyway, Duncan, but I'm back to a stable 3.4.4 system now. I had to re-solve a problem with gnutls and I had to re-compile the kernel, but for the moment everything's looking solid. I probably ought to leave the GCC upgrade now until I come back from my honeymoon. Yeah. Some things gotta be first! =8^) -- Duncan - List replies preferred. No HTML msgs. Every nonfree program has a lord, a master -- and if you use the program, he is your master. Richard Stallman -- gentoo-amd64@gentoo.org mailing list
[gentoo-amd64] Re: problems with emerging programs
Patric Douhane [EMAIL PROTECTED] posted [EMAIL PROTECTED], excerpted below, on Tue, 26 Sep 2006 08:41:00 +0200: Ok that could be it, though I've never noticed that there could be something wrong with the memory before, but I ran Windows XP and perhaps you don't notice such problems then? Can I test my memory with Memtest86?? You can, but it won't necessarily find a problem. If it does tho, you know you have one, but on mine, it didn't, because the problem wasn't really with the memory, but with the speed of access. Memtest86 came up 100% fine, but it was running on an otherwise idle system (duh, since you boot to it and can't be running anything else at the time), and simply wasn't stressing the timings enough to trigger the problem, which as I said wasn't the memory cells themselves going bad, but simply the timing. That was part of the frustration. At first I didn't know which component it was, and the memory never did actually turn out bad. It's just that it wasn't stable at the rated speed when under stress. I never /did/ actually know it was the memory until I got the BIOS that let me slow it down, and that cured it -- and then when I got new memory and it ran just fine at the higher speed, so it wasn't that the mobo memory traces simply couldn't handle it either. -- Duncan - List replies preferred. No HTML msgs. Every nonfree program has a lord, a master -- and if you use the program, he is your master. Richard Stallman -- gentoo-amd64@gentoo.org mailing list
[gentoo-amd64] emerge sandbox is using the wrong host id
Well, I decided to forge ahead while I still have the steam. I'm upgrading GCC from 3.4.4 to 4.1.1-r1. I followed the instructions thus: # emerge -uav gcc # gcc-config i686-pc-linux-gnu-4.1.1 # source /etc/profile # fix_libtool_files.sh 3.4.4 # emerge --oneshot -av libtool I then decided, before emerging -e system and risking confusion of GCC versions as before, to remove 3.4.4 and emerge libtool again to check that the compiler works ok. That went without a problem, so I do have a working 4.1.1 compiler. Now, during emerge -e system, emerge of sandbox (the ninth package of 114) falls over with the dreaded C compiler cannot create executables. I followed its own advice and ran: FEATURES=-sandbox emerge sandbox which failed at the same point. Here are some extracts from /var/tmp/portage/sandbox-1.2.18.1/work/build-x86-x86_64-pc-linux-gnu/config.log: Invocation command line was $ ../sandbox-1.2.18.1//configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr /share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib32 --enable-multili b --build=i686-pc-linux-gnu Note the --host=i686-pc-linux-gnu. I think that's wrong: it should say --host=x86_64-pc-linux-gnu, no? Continuing the log extract: configure:1533: checking for a BSD-compatible install configure:1588: result: /bin/install -c configure:1599: checking whether build environment is sane configure:1642: result: yes configure:1707: checking for gawk configure:1723: found /bin/gawk configure:1733: result: gawk configure:1743: checking whether make sets $(MAKE) configure:1763: result: yes configure:1942: checking for i686-pc-linux-gnu-gcc configure:1958: found /usr/bin/i686-pc-linux-gnu-gcc configure:1968: result: i686-pc-linux-gnu-gcc configure:2250: checking for C compiler version configure:2253: i686-pc-linux-gnu-gcc --version /dev/null 5 gcc-config error: i686-pc-linux-gnu-gcc wrapper: Could not determine which compiler to use. Invalid CTARGET or CTARGET has no selected profile. Indeed, issuing commands manually I get this: $ i686-pc-linux-gnu-gcc --version gcc-config error: i686-pc-linux-gnu-gcc wrapper: Could not determine which compiler to use. Invalid CTARGET or CTARGET has no selected profile. $ which i686-pc-linux-gnu-gcc /usr/bin/i686-pc-linux-gnu-gcc $ eselect compiler list Available compilers for CTARGET i686-pc-linux-gnu [1] x86_64-pc-linux-gnu-4.1.1/x86-vanilla Available compilers for CTARGET x86_64-pc-linux-gnu [2] x86_64-pc-linux-gnu-4.1.1/amd64-vanilla Activated profiles: [null] $ x86_64-pc-linux-gnu-gcc --version x86_64-pc-linux-gnu-gcc (GCC) 4.1.1 (Gentoo 4.1.1-r1) [...copyright notice...] [End of log extracts] Other packages are compiling as I write, having got to package 38 of 105, so the environment is broadly correct. Anyone any ideas? -- Rgds Peter -- gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] Re: problems with emerging programs
On 9/25/06, Patric Douhane [EMAIL PROTECTED] wrote: Ok that could be it, though I've never noticed that there could be something wrong with the memory before, but I ran Windows XP and perhaps you don't notice such problems then? Can I test my memory with Memtest86?? Not really. memtest86 can really only tell you if you have bad cells, which is actually extremely rare. This is because it works in a very linear fashion, and only between the CPU and memory. Compiling involves random access to different memory cells, rows, and even pages, as well as DMA transfers to/from the disk[s]. You can find a better script for testing memory here: http://people.redhat.com/dledford/memtest.html You might have to make some edits to get it to run on a Gentoo box. -Richard -- gentoo-amd64@gentoo.org mailing list
[gentoo-amd64] cups problem
Hi, I am trying to get my printer working and have installed cups. When I start cupsd I get the following message:- /etc/init.d/cupsd start * Starting cupsd ... cupsd: Child exited on signal 15! I have umerged and remerged but still get the same error here is some of emerge info:- Portage 2.1.1 (default-linux/amd64/2006.1/desktop, gcc-4.1.1, glibc-2.4-r3, 2.6.17-gentoo-r5 x86_64) = System uname: 2.6.17-gentoo-r5 x86_64 AMD Athlon(tm) 64 Processor 3500+ Gentoo Base System version 1.12.5 Last Sync: Mon, 25 Sep 2006 07:31:01 + app-admin/eselect-compiler: [Not Present] dev-java/java-config: 1.2.11-r1 dev-lang/python: 2.4.3-r1 dev-python/pycrypto: 2.0.1-r5 dev-util/ccache: [Not Present] dev-util/confcache: [Not Present] sys-apps/sandbox:1.2.17 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2 sys-devel/binutils: 2.16.1-r3 sys-devel/gcc-config: 1.3.13-r3 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS=amd64 The install logs did not show any errors. Any ideas what to do next? Paul -- This message has been sent using kmail with gentoo linux -- gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] cups problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Paul Stear wrote: Hi, I am trying to get my printer working and have installed cups. When I start cupsd I get the following message:- /etc/init.d/cupsd start * Starting cupsd ... cupsd: Child exited on signal 15! I'm not saying I can help but what does your cups error log say and lets see your /etc/cups/cupsd.conf file - -- Kirby Walborn -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFGRt+5HAWgdRxRvURAixJAJ4ou1hfKBENRgexRxzJnkdZpLEfPACfT+/K QhG6TZGiDXSt+0ypi78dy/I= =6KBp -END PGP SIGNATURE- -- gentoo-amd64@gentoo.org mailing list
[gentoo-amd64] Re: emerge sandbox is using the wrong host id
Peter Humphrey [EMAIL PROTECTED] posted [EMAIL PROTECTED], excerpted below, on Tue, 26 Sep 2006 11:18:18 +: Well, I decided to forge ahead while I still have the steam. I'm upgrading GCC from 3.4.4 to 4.1.1-r1. I followed the instructions thus: # emerge -uav gcc # gcc-config i686-pc-linux-gnu-4.1.1 # source /etc/profile # fix_libtool_files.sh 3.4.4 # emerge --oneshot -av libtool I then decided, before emerging -e system and risking confusion of GCC versions as before, to remove 3.4.4 and emerge libtool again to check that the compiler works ok. That went without a problem, so I do have a working 4.1.1 compiler. Now, during emerge -e system, emerge of sandbox (the ninth package of 114) falls over with the dreaded C compiler cannot create executables. I followed its own advice and ran: FEATURES=-sandbox emerge sandbox which failed at the same point. Here are some extracts from /var/tmp/portage/sandbox-1.2.18.1/work/build-x86-x86_64-pc-linux-gnu/config.log: Invocation command line was $ ../sandbox-1.2.18.1//configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr /share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib32 --enable-multili b --build=i686-pc-linux-gnu Note the --host=i686-pc-linux-gnu. I think that's wrong: it should say --host=x86_64-pc-linux-gnu, no? Continuing the log extract: No, that's correct in this case. I see your problem now. While most packages you install are 64-bit only and work, sandbox has both 32-bit and 64-bit components -- libraries that enforce sandbox restrictions in both 32-bit and 64-bit mode. What's happening is that your 64-bit gcc is working, but somewhere along the way, you lost a working 32-bit compiler. With it horked, you can't compile any 32-bit stuff, including the 32-bit part of sandbox. However, since most of the system is 64-bit and that's working, you can compile most packages just fine. Other packages that likely won't compile will be glibc and gcc, since they both have 32-bit aspects as well, and that's what's horked. configure:1942: checking for i686-pc-linux-gnu-gcc configure:1958: found /usr/bin/i686-pc-linux-gnu-gcc configure:1968: result: i686-pc-linux-gnu-gcc configure:2250: checking for C compiler version configure:2253: i686-pc-linux-gnu-gcc --version /dev/null 5 gcc-config error: i686-pc-linux-gnu-gcc wrapper: Could not determine which compiler to use. Invalid CTARGET or CTARGET has no selected profile. Indeed, issuing commands manually I get this: $ i686-pc-linux-gnu-gcc --version gcc-config error: i686-pc-linux-gnu-gcc wrapper: Could not determine which compiler to use. Invalid CTARGET or CTARGET has no selected profile. This simply confirms the above -- you have a dead 32-bit gcc. $ which i686-pc-linux-gnu-gcc /usr/bin/i686-pc-linux-gnu-gcc $ eselect compiler list Available compilers for CTARGET i686-pc-linux-gnu [1] x86_64-pc-linux-gnu-4.1.1/x86-vanilla Available compilers for CTARGET x86_64-pc-linux-gnu [2] x86_64-pc-linux-gnu-4.1.1/amd64-vanilla Activated profiles: [null] $ x86_64-pc-linux-gnu-gcc --version x86_64-pc-linux-gnu-gcc (GCC) 4.1.1 (Gentoo 4.1.1-r1) [...copyright notice...] [End of log extracts] Note the [null]. That should be where it lists the configured active 32-bit compiler. It's not set, so you are having problems. FWIW, this is almost certainly one of the reasons eselect-compiler is currently masked... Also note that since it's masked, the instructions for upgrading gcc needn't bother with any eselect compiler specific issues. Here's what happened. The old gcc-config (which the instructions have in mind) set both, but eselect compiler sets them separately and since you used the gcc-config compatibility wrapper with instructions for the old both-at-once gcc-config, guess what, you set only one. So... Try eselect compiler list, then eselect compiler set number, where number is an appropriate number selected from the available 32-bit compiler options. Hopefully, that gets you back on the right track, and you can successfully complete the sandbox emerge. If it doesn't, things get more difficult, but we identified the problem now, which is certainly half the way to fixing it right there. If necessary, you can rebuild gcc using the multilib version in the stage tarball to get working multilib back, and go from there. Same with glibc if necessary. Other packages are compiling as I write, having got to package 38 of 105, so the environment is broadly correct. As I said, the majority of the packages will be 64-bit, so lack of a valid 32-bit compiler setting won't affect them at all. Only the toolchain packages, for the most part, will be affected, so sandbox, glibc, gcc, and maybe binutils. (I don't have a good grasp of exactly how much of binutils is multilib split, but various remarks I've read indicate that at least some of it is.)
[gentoo-amd64] PDF Editor
Hello All, Can anyone recommend an application to edit a pdf file, and of course works on 64 bit Gentoo? Thanks, Sean -- gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] PDF Editor
On Tuesday 26 September 2006 10:20, sean [EMAIL PROTECTED] wrote about '[gentoo-amd64] PDF Editor': Can anyone recommend an application to edit a pdf file, and of course works on 64 bit Gentoo? PDF isn't meant to be edited. Most (if not all) of the TeX tools in portage as well as OpenOffice and KOffice can export to PDF, and anything that can print to cups should be able to generate a PDF via the cups-pdf fake printer. That said, I do not know of any application that lets you open an existing PDF and--say--correct typos, though I won't go far enough to say one doesn't exist. -- If there's one thing we've established over the years, it's that the vast majority of our users don't have the slightest clue what's best for them in terms of package stability. -- Gentoo Developer Ciaran McCreesh pgpd4wOp3NnlJ.pgp Description: PGP signature
Re: [gentoo-amd64] PDF Editor
--- sean [EMAIL PROTECTED] wrote: Hello All, Can anyone recommend an application to edit a pdf file, and of course works on 64 bit Gentoo? Well, KWord (part of the KOffice suite) has the ability to import PDF files, but it doesn't work very well. You can give it a try and maybe you'll be lucky and it works for your files. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] PDF Editor
On Tuesday 26 September 2006 22:32, Andrei Slavoiu wrote: --- sean [EMAIL PROTECTED] wrote: Hello All, Can anyone recommend an application to edit a pdf file, and of course works on 64 bit Gentoo? If other optins mentioned doesnt suit you, give a try to some OCR software. if needed, with imagemagick convert to jpg or something. m -- Linux 2.6.17-gentoo-r8 AMD Athlon(tm) 64 Processor 3200+ 22:41:15 up 18:11, 6 users, load average: 1.61, 1.94, 1.57 -- gentoo-amd64@gentoo.org mailing list
[gentoo-amd64] can't write certain characters in X
Hi I have a mysterious problem, I can't write @ | when I'm in x-terminal or in Gnome. someone know where to edit? (my keyboard layout is swedish)
Re: [gentoo-amd64] can't write certain characters in X
Are you using pc104 or pc105 as XkbModel (xorg.conf)? 2006/9/26, Patric Douhane [EMAIL PROTECTED]: Hi I have a mysterious problem, I can't write @ | when I'm in x-terminal or in Gnome. someone know where to edit?(my keyboard layout is swedish) -- gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] can't write certain characters in X
I am using pc104 - Original Message - From: Christoph Mende [EMAIL PROTECTED] To: gentoo-amd64@lists.gentoo.org Sent: Tuesday, September 26, 2006 10:08 PM Subject: Re: [gentoo-amd64] can't write certain characters in X Are you using pc104 or pc105 as XkbModel (xorg.conf)? 2006/9/26, Patric Douhane [EMAIL PROTECTED]: Hi I have a mysterious problem, I can't write @ | when I'm in x-terminal or in Gnome. someone know where to edit?(my keyboard layout is swedish) -- gentoo-amd64@gentoo.org mailing list -- gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] can't write certain characters in X
Set it to pc105 and you're problems are most likely fixed 2006/9/26, Patric Douhane [EMAIL PROTECTED]: I am using pc104 - Original Message - From: Christoph Mende [EMAIL PROTECTED] To: gentoo-amd64@lists.gentoo.org Sent: Tuesday, September 26, 2006 10:08 PM Subject: Re: [gentoo-amd64] can't write certain characters in X Are you using pc104 or pc105 as XkbModel (xorg.conf)? 2006/9/26, Patric Douhane [EMAIL PROTECTED]: Hi I have a mysterious problem, I can't write @ | when I'm in x-terminal or in Gnome. someone know where to edit?(my keyboard layout is swedish) -- gentoo-amd64@gentoo.org mailing list -- gentoo-amd64@gentoo.org mailing list -- gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] PDF Editor
Am Dienstag 26 September 2006 20:54 schrieb Daniel Gryniewicz: On Tue, 2006-09-26 at 13:50 -0500, Boyd Stephen Smith Jr. wrote: On Tuesday 26 September 2006 10:20, sean [EMAIL PROTECTED] wrote about '[gentoo-amd64] PDF Editor': Can anyone recommend an application to edit a pdf file, and of course works on 64 bit Gentoo? PDF isn't meant to be edited. Most (if not all) of the TeX tools in portage as well as OpenOffice and KOffice can export to PDF, and anything that can print to cups should be able to generate a PDF via the cups-pdf fake printer. That said, I do not know of any application that lets you open an existing PDF and--say--correct typos, though I won't go far enough to say one doesn't exist. evince/poppler/kpdf is working on it, but write support is not finished in poppler yet. I'm not aware of any other pdf editing software (except acrobat, or course). Daniel (evince maintainer) For simple things like cat some pdf Files I use app-text/mbtpdfasm Summary: This program can be used to assemble/merge PDF files, extract information from PDF files, and update the metadata in PDF files. Best regards Joerg -- gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] can't write certain characters in X
So I did, it didn't work, do I have to run some update or what? - Original Message - From: Christoph Mende [EMAIL PROTECTED] To: gentoo-amd64@lists.gentoo.org Sent: Tuesday, September 26, 2006 10:29 PM Subject: Re: [gentoo-amd64] can't write certain characters in X Set it to pc105 and you're problems are most likely fixed 2006/9/26, Patric Douhane [EMAIL PROTECTED]: I am using pc104 - Original Message - From: Christoph Mende [EMAIL PROTECTED] To: gentoo-amd64@lists.gentoo.org Sent: Tuesday, September 26, 2006 10:08 PM Subject: Re: [gentoo-amd64] can't write certain characters in X Are you using pc104 or pc105 as XkbModel (xorg.conf)? 2006/9/26, Patric Douhane [EMAIL PROTECTED]: Hi I have a mysterious problem, I can't write @ | when I'm in x-terminal or in Gnome. someone know where to edit?(my keyboard layout is swedish) -- gentoo-amd64@gentoo.org mailing list -- gentoo-amd64@gentoo.org mailing list -- gentoo-amd64@gentoo.org mailing list -- gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] can't write certain characters in X
Well, you have to restart X. 2006/9/26, Patric Douhane [EMAIL PROTECTED]: So I did, it didn't work, do I have to run some update or what? - Original Message - From: Christoph Mende [EMAIL PROTECTED] To: gentoo-amd64@lists.gentoo.org Sent: Tuesday, September 26, 2006 10:29 PM Subject: Re: [gentoo-amd64] can't write certain characters in X Set it to pc105 and you're problems are most likely fixed 2006/9/26, Patric Douhane [EMAIL PROTECTED]: I am using pc104 - Original Message - From: Christoph Mende [EMAIL PROTECTED] To: gentoo-amd64@lists.gentoo.org Sent: Tuesday, September 26, 2006 10:08 PM Subject: Re: [gentoo-amd64] can't write certain characters in X Are you using pc104 or pc105 as XkbModel (xorg.conf)? 2006/9/26, Patric Douhane [EMAIL PROTECTED]: Hi I have a mysterious problem, I can't write @ | when I'm in x-terminal or in Gnome. someone know where to edit?(my keyboard layout is swedish) -- gentoo-amd64@gentoo.org mailing list -- gentoo-amd64@gentoo.org mailing list -- gentoo-amd64@gentoo.org mailing list -- gentoo-amd64@gentoo.org mailing list -- gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] can't write certain characters in X
Of course, did that, doesn't help thoughdoes it have to do with unicode? - Original Message - From: Christoph Mende [EMAIL PROTECTED] To: gentoo-amd64@lists.gentoo.org Sent: Tuesday, September 26, 2006 10:50 PM Subject: Re: [gentoo-amd64] can't write certain characters in X Well, you have to restart X. 2006/9/26, Patric Douhane [EMAIL PROTECTED]: So I did, it didn't work, do I have to run some update or what? - Original Message - From: Christoph Mende [EMAIL PROTECTED] To: gentoo-amd64@lists.gentoo.org Sent: Tuesday, September 26, 2006 10:29 PM Subject: Re: [gentoo-amd64] can't write certain characters in X Set it to pc105 and you're problems are most likely fixed 2006/9/26, Patric Douhane [EMAIL PROTECTED]: I am using pc104 - Original Message - From: Christoph Mende [EMAIL PROTECTED] To: gentoo-amd64@lists.gentoo.org Sent: Tuesday, September 26, 2006 10:08 PM Subject: Re: [gentoo-amd64] can't write certain characters in X Are you using pc104 or pc105 as XkbModel (xorg.conf)? 2006/9/26, Patric Douhane [EMAIL PROTECTED]: Hi I have a mysterious problem, I can't write @ | when I'm in x-terminal or in Gnome. someone know where to edit?(my keyboard layout is swedish) -- gentoo-amd64@gentoo.org mailing list -- gentoo-amd64@gentoo.org mailing list -- gentoo-amd64@gentoo.org mailing list -- gentoo-amd64@gentoo.org mailing list -- gentoo-amd64@gentoo.org mailing list -- gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] can't write certain characters in X
Don't know what exactly you mean, but the unicode use flag doesn't cause any problems. Here's my keyboard section in xorg.conf, maybe it helps: Section InputDevice Identifier Generic Keyboard Driver kbd Option CoreKeyboard Option XkbModel pc105 Option XkbLayout de Option XkbVariant nodeadkeys Option XkbOptions nodeadkeys EndSection You have to change the XkbLayout, of course :) 2006/9/26, Patric Douhane [EMAIL PROTECTED]: Of course, did that, doesn't help thoughdoes it have to do with unicode? - Original Message - From: Christoph Mende [EMAIL PROTECTED] To: gentoo-amd64@lists.gentoo.org Sent: Tuesday, September 26, 2006 10:50 PM Subject: Re: [gentoo-amd64] can't write certain characters in X Well, you have to restart X. 2006/9/26, Patric Douhane [EMAIL PROTECTED]: So I did, it didn't work, do I have to run some update or what? - Original Message - From: Christoph Mende [EMAIL PROTECTED] To: gentoo-amd64@lists.gentoo.org Sent: Tuesday, September 26, 2006 10:29 PM Subject: Re: [gentoo-amd64] can't write certain characters in X Set it to pc105 and you're problems are most likely fixed 2006/9/26, Patric Douhane [EMAIL PROTECTED]: I am using pc104 - Original Message - From: Christoph Mende [EMAIL PROTECTED] To: gentoo-amd64@lists.gentoo.org Sent: Tuesday, September 26, 2006 10:08 PM Subject: Re: [gentoo-amd64] can't write certain characters in X Are you using pc104 or pc105 as XkbModel (xorg.conf)? 2006/9/26, Patric Douhane [EMAIL PROTECTED]: Hi I have a mysterious problem, I can't write @ | when I'm in x-terminal or in Gnome. someone know where to edit?(my keyboard layout is swedish) -- gentoo-amd64@gentoo.org mailing list -- gentoo-amd64@gentoo.org mailing list -- gentoo-amd64@gentoo.org mailing list -- gentoo-amd64@gentoo.org mailing list -- gentoo-amd64@gentoo.org mailing list -- gentoo-amd64@gentoo.org mailing list -- gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] emerge sandbox is using the wrong host id
On Tuesday 26 September 2006 12:17, Simon Stelling wrote: Stop using eselect-compiler, it's broken :P Unmerge it and make sure you have =gcc-config-1.3* installed. Yes, I think I knew it was broken; I only used it to list what's available. Selection of compiler I did with gcc-config. -- Rgds Peter -- gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] Re: emerge sandbox is using the wrong host id
On Tuesday 26 September 2006 12:20, Duncan wrote: Other packages that likely won't compile will be glibc and gcc, since they both have 32-bit aspects as well, and that's what's horked. Nope, they both compile just fine. Of those, only sandbox is causing me grief. ... the majority of the packages will be 64-bit, so lack of a valid 32-bit compiler setting won't affect them at all. Only the toolchain packages, for the most part, will be affected, so sandbox, glibc, gcc, and maybe binutils. Actually, only sandbox and module-init-tools are failing. if you are lucky, simply setting the 32-bit compiler will put you back in good form. I can't see why selecting a 32-bit compiler should make portage work again. Surely I need a 64-bit compiler for almost the whole system? I haven't changed any multilib flags, so I should still have both, no? For the moment I'm continuing with emerge -e world, just skipping the few packages that fail (just the two of them so far) - they still exist, after all, in their earlier state. ... I wonder how much of your earlier problems might have the same thing? Oh, well, hindsight's always 20/20, as they say. One more thing to add to our list of things to check... -- Duncan - List replies preferred. No HTML msgs. Every nonfree program has a lord, a master -- and if you use the program, he is your master. Richard Stallman -- Rgds Peter -- gentoo-amd64@gentoo.org mailing list
[gentoo-amd64] Re: problems with emerging programs [SOLVED]
Patric Douhane [EMAIL PROTECTED] posted [EMAIL PROTECTED], excerpted below, on Tue, 26 Sep 2006 17:51:07 +0200: Thanks guys, this solved it! I changed the memory timing in bios, but I also disabled apic, so I really don't know which of them did it, but I will re-enable them one at a time to check (later on...) Good. One more bug stomped to death! =8^) -- Duncan - List replies preferred. No HTML msgs. Every nonfree program has a lord, a master -- and if you use the program, he is your master. Richard Stallman -- gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] PDF Editor
Sean wrote: Hello All, Can anyone recommend an application to edit a pdf file, and of course works on 64 bit Gentoo? app-text/pdftk can be used to attach files to a pdf doc, add a watermark, fill forms, cat pdf files together and burst them apart. It does not allow you to edit the textual content. It needs gcj, so you will have to add that to your USE flags and re-emerge gcc. Dave F -- gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] PDF Editor
http://www.foxitsoftware.com/pdf/desklinux/ Foxit has a no-fee reader for Linux, but no writer. Only on Windows. --- Vladimir On Tuesday 26 September 2006 10:20, sean [EMAIL PROTECTED] wrote Can anyone recommend an application to edit a pdf file, and of course works on 64 bit Gentoo? -- Vladimir G. Ivanovic [EMAIL PROTECTED]
[gentoo-amd64] First Impressions
Hello, everyone! It's my first mail to this list. I hope the community here is as friendly as the one at the general gentoo-user list ;-) Please, forgive me if open some threads about already discussed issues until I catch up with rhythm of the list. So let me start a with 2 newbie questions caused by my first impressions from the x86_64 world: 1) I use CFLAGS=-march=athlon64 -mfpmath=sse -msse -msse2 -msse3 -m3dnow -mmmx -O3 -fomit-frame-pointer -pipe -fpic. Portage complains with *red letters* about the fpic flag. Every time I emerge something it says that fpic breaks things, but I haven't met a single breakage so far. Is that a bug? Actually there was an ebuild which could not be compiled if mysql was compiled w/o fpic. I'm not 100% sure but AFAIR it was dev-perl/DBD-mysql. 2) I see too many flags that are disabled by the profile - the kind with the parenthesis around them, like (-3dnow). Why? As I mentioned above I enable some of these through my CFLAGS - e.g. (-mmx), (-mmxext), (-sse) and (-sse2) and everything works perfect. -- gentoo-amd64@gentoo.org mailing list
