Re: [gentoo-amd64] Re: wxSVGXML?
Duncan wrote: "Mark Haney" <[EMAIL PROTECTED]> posted [EMAIL PROTECTED], excerpted below, on Wed, 04 Jun 2008 10:39:24 -0400: Thanks to everyone for helping this ebuild n00b get working. I've get everything setup, but now I've hit a snag. The ebuild I am working on requires svgxml.h and I cannot find that file. With other distros it's in the wxsvg-devel package (or similar), but I can't find one for that in Gentoo. With wxsvg, there's a wxSVG and wxXML folder in /usr/include/, but neither have this file. I don't even know where to begin looking for it in Gentoo. Ideas? I don't have the file and don't have any of the wxWidgets installed, but at a guess... wrong version. This seems to be confirmed with a search: Google this for the fedora 1.0 beta 10 package: wxsvg-devel-1.0-0.8.b10 svgxml.h Now replace the b10 with b9, b8, etc. No hits. Delete the svgxml.h bit and you get hits again, so it's seeing the package, just not that file in the package. Therefore, it would seem that file was added in beta 10. Unfortunately, Gentoo's tree is outdated, with only the beta 7 ebuild. A quick check of bugzy results in: media-libs/wxsvg-1.0_beta10 version bump request http://bugs.gentoo.org/show_bug.cgi?id=215665 Duncan, I saw that when I googled for that file, but from the wxsvg home page, there's no mention at all of a Beta10 (or B9 for that matter). That site may be outdated, since I can see the Fedora 9 devel rpm, I suppose I can rip it apart and use it if I need to, just for the header files. I'll look at the ebuilds first. Thanks! -- Libenter homines id quod volunt credunt -- Caius Julius Caesar Mark Haney Sr. Systems Administrator ERC Broadband (828) 350-2415 Call (866) ERC-7110 for after hours support -- gentoo-amd64@lists.gentoo.org mailing list
Re: [gentoo-amd64] wxSVGXML?
On Wed, 2008-06-04 at 12:50 -0400, Mark Haney wrote: > Sebastian Redl wrote: > > Mark Haney wrote: > > >> > >> > > Looking at the source code and the ebuild for wxSVG, I see no reason why > > the file wouldn't be installed. Are you sure you don't have the wxSVGXML > > directory in /usr/include? xmlsvg.h should be in there. > > > > Sebastian > > That directory doesn't exist in my system: > > > octavian dvdstyler # ls /usr/include/wx* -d > > /usr/include/wx-2.6 /usr/include/wx-2.8 /usr/include/wxSVG > > /usr/include/wxXML > > Which I don't get. Is there a USE flag that would account for this? > FWIW nothing installed in 2 of 2 systems here, but a masked wxsvg ebuild is in /usr/portage/media-libs on both > > -- > Libenter homines id quod volunt credunt -- Caius Julius Caesar > > > Mark Haney > Sr. Systems Administrator > ERC Broadband > (828) 350-2415 > > Call (866) ERC-7110 for after hours support -- gentoo-amd64@lists.gentoo.org mailing list
[gentoo-amd64] Re: wxSVGXML?
"Mark Haney" <[EMAIL PROTECTED]> posted [EMAIL PROTECTED], excerpted below, on Wed, 04 Jun 2008 10:39:24 -0400: > Thanks to everyone for helping this ebuild n00b get working. I've get > everything setup, but now I've hit a snag. The ebuild I am working on > requires svgxml.h and I cannot find that file. With other distros it's > in the wxsvg-devel package (or similar), but I can't find one for that > in Gentoo. With wxsvg, there's a wxSVG and wxXML folder in > /usr/include/, but neither have this file. > > I don't even know where to begin looking for it in Gentoo. Ideas? I don't have the file and don't have any of the wxWidgets installed, but at a guess... wrong version. This seems to be confirmed with a search: Google this for the fedora 1.0 beta 10 package: wxsvg-devel-1.0-0.8.b10 svgxml.h Now replace the b10 with b9, b8, etc. No hits. Delete the svgxml.h bit and you get hits again, so it's seeing the package, just not that file in the package. Therefore, it would seem that file was added in beta 10. Unfortunately, Gentoo's tree is outdated, with only the beta 7 ebuild. A quick check of bugzy results in: media-libs/wxsvg-1.0_beta10 version bump request http://bugs.gentoo.org/show_bug.cgi?id=215665 Seems they're working on it, but it needs some patches to work with Gentoo, and while it's building, it isn't actually functional (segfaults). So... you can try hacking that ebuild and see if you can get it to work, or building and installing manually, to see if that works. I'd certainly suggest CCing yourself to the bug. It's also possible that whatever you are trying to build against that header file, you can either find an older version that builds against beta 7, or maybe, you can merge the building but segfaulting beta 10, and not have it matter if all you need are the header files. -- 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@lists.gentoo.org mailing list
Re: [gentoo-amd64] wxSVGXML?
Sebastian Redl wrote: Mark Haney wrote: Looking at the source code and the ebuild for wxSVG, I see no reason why the file wouldn't be installed. Are you sure you don't have the wxSVGXML directory in /usr/include? xmlsvg.h should be in there. Sebastian That directory doesn't exist in my system: octavian dvdstyler # ls /usr/include/wx* -d /usr/include/wx-2.6 /usr/include/wx-2.8 /usr/include/wxSVG /usr/include/wxXML Which I don't get. Is there a USE flag that would account for this? -- Libenter homines id quod volunt credunt -- Caius Julius Caesar Mark Haney Sr. Systems Administrator ERC Broadband (828) 350-2415 Call (866) ERC-7110 for after hours support -- gentoo-amd64@lists.gentoo.org mailing list
Re: [gentoo-amd64] wxSVGXML?
Mark Haney wrote: > Thanks to everyone for helping this ebuild n00b get working. I've get > everything setup, but now I've hit a snag. The ebuild I am working on > requires svgxml.h and I cannot find that file. With other distros > it's in the wxsvg-devel package (or similar), but I can't find one for > that in Gentoo. With wxsvg, there's a wxSVG and wxXML folder in > /usr/include/, but neither have this file. > > I don't even know where to begin looking for it in Gentoo. Ideas? > > Looking at the source code and the ebuild for wxSVG, I see no reason why the file wouldn't be installed. Are you sure you don't have the wxSVGXML directory in /usr/include? xmlsvg.h should be in there. Sebastian -- gentoo-amd64@lists.gentoo.org mailing list
Re: [gentoo-amd64] wxSVGXML?
Mark Haney schrieb: Thanks to everyone for helping this ebuild n00b get working. I've get everything setup, but now I've hit a snag. The ebuild I am working on requires svgxml.h and I cannot find that file. With other distros it's in the wxsvg-devel package (or similar), but I can't find one for that in Gentoo. With wxsvg, there's a wxSVG and wxXML folder in /usr/include/, but neither have this file. I don't even know where to begin looking for it in Gentoo. Ideas? Good site to query is the "www.portagefilelist.de" Sadly in this case you will have no luck! signature.asc Description: OpenPGP digital signature
[gentoo-amd64] wxSVGXML?
Thanks to everyone for helping this ebuild n00b get working. I've get everything setup, but now I've hit a snag. The ebuild I am working on requires svgxml.h and I cannot find that file. With other distros it's in the wxsvg-devel package (or similar), but I can't find one for that in Gentoo. With wxsvg, there's a wxSVG and wxXML folder in /usr/include/, but neither have this file. I don't even know where to begin looking for it in Gentoo. Ideas? -- Libenter homines id quod volunt credunt -- Caius Julius Caesar Mark Haney Sr. Systems Administrator ERC Broadband (828) 350-2415 Call (866) ERC-7110 for after hours support -- gentoo-amd64@lists.gentoo.org mailing list
Re: [gentoo-amd64] Ebuild HOWTO
deface wrote: Hey Mark, Cool, your in Asheville. I used to live there; grew up there actually. - as far as your ebuild's; take a look at the following sites. Hey that's very cool. I actually live in Old Fort now, but grew up in Swannanoa. Work in Buncombe County since McDowell Co doesn't know what a computer is yet. :) I will certainly take a look at these and see if they fit the bill. I haven't seen the gentoo-wiki URL in my searches so I may start there. http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=2&chap=1 http://devmanual.gentoo.org/quickstart/index.html http://gentoo-wiki.com/HOWTO_Create_an_Updated_Ebuild once done with the actual ebuild, http://www.gentoo.org/doc/en/ebuild-submit.xml I use layman, and create my own ebuilds for testing purposes in it. hope this helps, deface -- Libenter homines id quod volunt credunt -- Caius Julius Caesar Mark Haney Sr. Systems Administrator ERC Broadband (828) 350-2415 Call (866) ERC-7110 for after hours support -- gentoo-amd64@lists.gentoo.org mailing list -- Libenter homines id quod volunt credunt -- Caius Julius Caesar Mark Haney Sr. Systems Administrator ERC Broadband (828) 350-2415 Call (866) ERC-7110 for after hours support -- gentoo-amd64@lists.gentoo.org mailing list
Re: [gentoo-amd64] Ebuild HOWTO
On 6/4/08, Mark Haney <[EMAIL PROTECTED]> wrote: > Okay, I've gone over the docs and the HOWTOs on gentoo.org and I'm still a > wee bit (okay maybe a lot) fuzzy on developing/updating ebuilds. > > I have a particular app I use quite often (DVDStyler), but the ebuild in > portage is pretty old (1.5.2_p2) compared to the latest version available > (1.6.2), the difference being about a year between them. > > I know I can just compile the source for the latest, but I'd like to update > the ebuild to learn how to do it. The docs however, aren't helpful from the > standpoint that there's no clear cut procedure for setting up a devel > environment for building/testing an ebuild locally without becoming a gentoo > developer, per se. > > Me, I rather like having step-by-step instructions on my first go round so > I can 'do it right' the first time, then I'll know how to fix it if I bork > something. > > Is there something like that floating around? > > Mark Haney Mark, is a local layman repo something for you? I found this link http://gentoo-wiki.com/TIP_Sync_your_private_overlay Hope this is of some help :) -- gentoo-amd64@lists.gentoo.org mailing list
Re: [gentoo-amd64] Ebuild HOWTO
Hey Mark, Cool, your in Asheville. I used to live there; grew up there actually. - as far as your ebuild's; take a look at the following sites. http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=2&chap=1 http://devmanual.gentoo.org/quickstart/index.html http://gentoo-wiki.com/HOWTO_Create_an_Updated_Ebuild once done with the actual ebuild, http://www.gentoo.org/doc/en/ebuild-submit.xml I use layman, and create my own ebuilds for testing purposes in it. hope this helps, deface On Jun 4, 2008, at 8:53 AM, Mark Haney wrote: Okay, I've gone over the docs and the HOWTOs on gentoo.org and I'm still a wee bit (okay maybe a lot) fuzzy on developing/updating ebuilds. I have a particular app I use quite often (DVDStyler), but the ebuild in portage is pretty old (1.5.2_p2) compared to the latest version available (1.6.2), the difference being about a year between them. I know I can just compile the source for the latest, but I'd like to update the ebuild to learn how to do it. The docs however, aren't helpful from the standpoint that there's no clear cut procedure for setting up a devel environment for building/testing an ebuild locally without becoming a gentoo developer, per se. Me, I rather like having step-by-step instructions on my first go round so I can 'do it right' the first time, then I'll know how to fix it if I bork something. Is there something like that floating around? -- Libenter homines id quod volunt credunt -- Caius Julius Caesar Mark Haney Sr. Systems Administrator ERC Broadband (828) 350-2415 Call (866) ERC-7110 for after hours support -- gentoo-amd64@lists.gentoo.org mailing list -- gentoo-amd64@lists.gentoo.org mailing list
Re: [gentoo-amd64] Ebuild HOWTO
2008/6/4 Mark Haney <[EMAIL PROTECTED]>: > Okay, I've gone over the docs and the HOWTOs on gentoo.org and I'm still a > wee bit (okay maybe a lot) fuzzy on developing/updating ebuilds. > > I have a particular app I use quite often (DVDStyler), but the ebuild in > portage is pretty old (1.5.2_p2) compared to the latest version available > (1.6.2), the difference being about a year between them. > > I know I can just compile the source for the latest, but I'd like to update > the ebuild to learn how to do it. The docs however, aren't helpful from the > standpoint that there's no clear cut procedure for setting up a devel > environment for building/testing an ebuild locally without becoming a gentoo > developer, per se. > > Me, I rather like having step-by-step instructions on my first go round so > I can 'do it right' the first time, then I'll know how to fix it if I bork > something. > > Is there something like that floating around? > the easiest way is to rename the old ebuild to 1.6.2, to remove from it the epatch options and see if it builds. harder stuff consist of testing the manual build of the package (download, configure, make, but not make install, then test various configure options and retest make and then put them in the ebuild). -- dott. ing. beso
[gentoo-amd64] Ebuild HOWTO
Okay, I've gone over the docs and the HOWTOs on gentoo.org and I'm still a wee bit (okay maybe a lot) fuzzy on developing/updating ebuilds. I have a particular app I use quite often (DVDStyler), but the ebuild in portage is pretty old (1.5.2_p2) compared to the latest version available (1.6.2), the difference being about a year between them. I know I can just compile the source for the latest, but I'd like to update the ebuild to learn how to do it. The docs however, aren't helpful from the standpoint that there's no clear cut procedure for setting up a devel environment for building/testing an ebuild locally without becoming a gentoo developer, per se. Me, I rather like having step-by-step instructions on my first go round so I can 'do it right' the first time, then I'll know how to fix it if I bork something. Is there something like that floating around? -- Libenter homines id quod volunt credunt -- Caius Julius Caesar Mark Haney Sr. Systems Administrator ERC Broadband (828) 350-2415 Call (866) ERC-7110 for after hours support -- gentoo-amd64@lists.gentoo.org mailing list
[gentoo-amd64] Re: multicore strange issue
Beso <[EMAIL PROTECTED]> posted [EMAIL PROTECTED], excerpted below, on Wed, 04 Jun 2008 07:34:09 +: > the make modules_install && make install would put the right stuff in > the right place, but when restarting the kernel image read was the old > one (the one without smp support) and so the different executable file > format errror, using the new smp modules and the old single-core kernel > image. i'm really feeling really stupid for not having noticed this > earlier, but maybe since the issue got out at about 23.00 after a full > day of work maybe it's plausible. thanks to all of you who have answered > to my question. Don't worry about it. I'm sure most of us eventually hit that or a similar modules/kernel mismatch error. I know I've seen it when I boot my rootbak partition (on which I keep a backup system image, from a time it was known to be generally working) and the kernel in /boot is newer than the modules on rootbak, one of the reasons I recognized it. > ps. duncan, when you've got some spare time could you please post the > scripts for the kernel automation build if it's not bothersome. thanks > again. I have it on my list for this weekend if not earlier. If I haven't posted anything by Sunday, poke me. =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@lists.gentoo.org mailing list
Re: [gentoo-amd64] Re: multicore strange issue
2008/6/3 Konrad Okurowski <[EMAIL PROTECTED]>: > Hi, > IMO when performing "make" after make clean and make menuconfig (assuming > you want to change something in kernel) builds kernel image and modules as > well. After that I run rm -rf /lib/modules/ and make && make > modules_install. Then there shouldn't be any problem. (also [emerge -av > $(qdepends -CNQ virtual/linux-sources)] would be nice). > > Kfiaciarka > > 2008/6/3 Duncan <[EMAIL PROTECTED]>: > > Beso <[EMAIL PROTECTED]> posted >> [EMAIL PROTECTED], excerpted >> below, on Tue, 03 Jun 2008 09:01:04 +: >> >> > the problem is that with the old normal config the kernel detects one >> > processor and one core and it works, loading the modules, but when >> > enabling simetric multiprocessing the kernel detects just one processor >> > and one core and then it fails to load modules because of a different >> > executable format in the modules. >> >> This indicates that the modules and the kernel aren't matched. IOW, you >> apparently compiled the new kernel but failed to compile the matching >> modules, so it's trying to use the old ones, which don't match the new >> kernel, so it won't load them. >> >> Even if it's the exact same kernel you compiled, if you change options, >> particularly something as big as SMP, you'll need to recompile the kernel >> modules as well. >> >> Also note that if you use an initrd/initramfs, you'll need to redo it, >> loading the new modules as appropriate into it as well as placing them in >> the normal /lib/modules// dir. I don't run an initramfs/ >> initrd, so have never learned the technical intricacies thereof, but >> wherever it's trying to load them from, you don't have the right ones >> there for it to load. >> >> One way or the other, with or without the initrd/initramfs, the kernel is >> trying to load modules that don't match the kernel, and failing. Correct >> that, and you will have fixed at least that problem, altho it's possible >> you'll then have others to fix as well. >> >> -- >> 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@lists.gentoo.org mailing list >> >> > > > -- > pozdrawiam > Konrad Okurowski <[EMAIL PROTECTED]> > Key Fingerprint = D993 3823 F20D 3B8D 2719 3012 2FE8 > i've found out the problem: i'm using a /boot not on the /partition and on the new pc i've set the partition table in a different way, so boot didn't mount at startup. the make modules_install && make install would put the right stuff in the right place, but when restarting the kernel image read was the old one (the one without smp support) and so the different executable file format errror, using the new smp modules and the old single-core kernel image. i'm really feeling really stupid for not having noticed this earlier, but maybe since the issue got out at about 23.00 after a full day of work maybe it's plausible. thanks to all of you who have answered to my question. ps. duncan, when you've got some spare time could you please post the scripts for the kernel automation build if it's not bothersome. thanks again. -- dott. ing. beso