Re: [gentoo-user] Can't build OpenSSH, requires Perl 5
On Fri, 10 Jun 2005 20:51:20 -0700, Ted Ozolins wrote: I ran into the same glitch on a new system. The only way I was able to get around that was to blank out my USE= in /etc/make.conf. I realized afterwards that I could have accomplished the same by: USE=*- emerge -v perl They aren't the same thing. Commenting out the USE declaration in make.conf makes portage use the default USE flags from your profile. USE=-* overrides your profile and turns everything off. -- Neil Bothwick Top Oxymorons Number 45: Resident alien pgpX5qELv19VZ.pgp Description: PGP signature
Re: [gentoo-user] Can't build OpenSSH, requires Perl 5
Zac Medico wrote: afterwards that I could have accomplished the same by: USE=*- emerge -v perl More drastic than my solution but it could be necessary. I've seen USE=-* more commonly but maybe they're equivalent. I believe emerge --nodeps does basically the same thing. no USE=-* skips all optional dependencies (depending on a use flag) --nodeps skips ALL dependecies yoyo -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Can't build OpenSSH, requires Perl 5
YoYo Siska wrote: Zac Medico wrote: More drastic than my solution but it could be necessary. I've seen USE=-* more commonly but maybe they're equivalent. I believe emerge --nodeps does basically the same thing. no USE=-* skips all optional dependencies (depending on a use flag) --nodeps skips ALL dependecies yoyo Yeah, now I'm curious how --nodeps handles USE flags. I suppose it should leave them as is. Generally, the only time I use --nodeps is when when I encounter strange dependency issues with binary packages. Zac -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Can't build OpenSSH, requires Perl 5
Zac Medico wrote: YoYo Siska wrote: Zac Medico wrote: More drastic than my solution but it could be necessary. I've seen USE=-* more commonly but maybe they're equivalent. I believe emerge --nodeps does basically the same thing. no USE=-* skips all optional dependencies (depending on a use flag) --nodeps skips ALL dependecies yoyo Yeah, now I'm curious how --nodeps handles USE flags. I suppose it should leave them as is. Generally, the only time I use --nodeps is when when I encounter strange dependency issues with binary packages. why should it handle USE flags in any way? it just tels portage not to emerge the dependencie, whatever they are ( when added by use flags..) that means USE=alsa emerge --nodeps mplayer would (try to) compile mplayer _with_ alsa support but in the case alsa-lib (which is an optional dep on the alsa use flag) is no installed, it will not emerge it (which can cause mplayer not to compile, or not to work...) -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Can't build OpenSSH, requires Perl 5
YoYo Siska wrote: Zac Medico wrote: YoYo Siska wrote: Zac Medico wrote: More drastic than my solution but it could be necessary. I've seen USE=-* more commonly but maybe they're equivalent. I believe emerge --nodeps does basically the same thing. no USE=-* skips all optional dependencies (depending on a use flag) --nodeps skips ALL dependecies yoyo Yeah, now I'm curious how --nodeps handles USE flags. I suppose it should leave them as is. Generally, the only time I use --nodeps is when when I encounter strange dependency issues with binary packages. why should it handle USE flags in any way? it just tels portage not to emerge the dependencie, whatever they are ( when added by use flags..) that means USE=alsa emerge --nodeps mplayer would (try to) compile mplayer _with_ alsa support but in the case alsa-lib (which is an optional dep on the alsa use flag) is no installed, it will not emerge it (which can cause mplayer not to compile, or not to work...) Yep, that's why --nodeps is a very special option. It depends on the way the USE flags interact with the build. I see at least 3 possible outcomes here: 1) The build fails because the it can't live without the alsa libs. 2) The build succeeds because the it can live without the alsa libs and automatically disables the alsa features. 3) The build succeeds because the alsa libs happen to already be installed. Cool ;-) Zac -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Can't build OpenSSH, requires Perl 5
Zac Medico wrote: YoYo Siska wrote: why should it handle USE flags in any way? it just tels portage not to emerge the dependencie, whatever they are ( when added by use flags..) that means USE=alsa emerge --nodeps mplayer would (try to) compile mplayer _with_ alsa support but in the case alsa-lib (which is an optional dep on the alsa use flag) is no installed, it will not emerge it (which can cause mplayer not to compile, or not to work...) Yep, that's why --nodeps is a very special option. It depends on the way the USE flags interact with the build. I see at least 3 possible outcomes here: 1) The build fails because the it can't live without the alsa libs. 2) The build succeeds because the it can live without the alsa libs and automatically disables the alsa features. 3) The build succeeds because the alsa libs happen to already be installed. I have a real example that illustrates (2) above: USE=-nomotif emerge --nodeps xpdf If motif isn't installed (or the headers aren't linked properly by motif-config), the build completes successfully with motif disabled. The ebuild tells the configure script to enable motif because of the USE=-nomotif flag but then later the configure script doesn't detect the motif headers and continues the build anyways without motif. Zac -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Can't build OpenSSH, requires Perl 5
Zac Medico wrote: Zac Medico wrote: YoYo Siska wrote: why should it handle USE flags in any way? it just tels portage not to emerge the dependencie, whatever they are ( when added by use flags..) that means USE=alsa emerge --nodeps mplayer would (try to) compile mplayer _with_ alsa support but in the case alsa-lib (which is an optional dep on the alsa use flag) is no installed, it will not emerge it (which can cause mplayer not to compile, or not to work...) Yep, that's why --nodeps is a very special option. It depends on the way the USE flags interact with the build. I see at least 3 possible outcomes here: 1) The build fails because the it can't live without the alsa libs. 2) The build succeeds because the it can live without the alsa libs and automatically disables the alsa features. 3) The build succeeds because the alsa libs happen to already be installed. I have a real example that illustrates (2) above: USE=-nomotif emerge --nodeps xpdf If motif isn't installed (or the headers aren't linked properly by motif-config), the build completes successfully with motif disabled. The ebuild tells the configure script to enable motif because of the USE=-nomotif flag but then later the configure script doesn't detect the motif headers and continues the build anyways without motif. Zac yep, and there is: 2.5) build succeeds, but the app can have something broken if the dep was a runtime dep (if for example the app just executes something else and doesn't check for the binary at compile time ;) yoyo -- gentoo-user@gentoo.org mailing list
[gentoo-user] Can't build OpenSSH, requires Perl 5
I'm compiling my system (emerge -env system), but when it gets down to building OpenSSH, it fails, saying You need Perl 5. Pretending and checking the tree shows that Perl 5 will be emerged later on during the install. Attempting to emerge -v perl attempts to emerge svgalib as well (since I haven't built the system), which fails saying that the kernel has not been configured yet. Any ideas? -- Colin -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Can't build OpenSSH, requires Perl 5
Colin wrote: I'm compiling my system (emerge -env system), but when it gets down to building OpenSSH, it fails, saying You need Perl 5. Pretending and checking the tree shows that Perl 5 will be emerged later on during the install. Attempting to emerge -v perl attempts to emerge svgalib as well (since I haven't built the system), which fails saying that the kernel has not been configured yet. Any ideas? -- Colin I ran into the same glitch on a new system. The only way I was able to get around that was to blank out my USE= in /etc/make.conf. I realized afterwards that I could have accomplished the same by: USE=*- emerge -v perl Cheers. -- Ted Ozolins(VE7TVO) Westbank, B. C -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Can't build OpenSSH, requires Perl 5
--- Ted Ozolins [EMAIL PROTECTED] wrote: Colin wrote: I'm compiling my system (emerge -env system), but when it gets down to building OpenSSH, it fails, saying You need Perl 5. Pretending and checking the tree shows that Perl 5 will be emerged later on during the install. Attempting to emerge -v perl attempts to emerge svgalib as well (since I haven't built the system), which fails saying that the kernel has not been configured yet. Any ideas? -- Colin I ran into the same glitch on a new system. The only way I was able to get around that was to blank out my USE= in /etc/make.conf. I realized afterwards that I could have accomplished the same by: USE=*- emerge -v perl More drastic than my solution but it could be necessary. I've seen USE=-* more commonly but maybe they're equivalent. I believe emerge --nodeps does basically the same thing. Zac __ Discover Yahoo! Get on-the-go sports scores, stock quotes, news and more. Check it out! http://discover.yahoo.com/mobile.html -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Can't build OpenSSH, requires Perl 5
--- Colin [EMAIL PROTECTED] wrote: Now that I've been thinking about it for a while, if OpenSSH needs Perl, shouldn't Perl be built before OpenSSH? This seems like an ebuild bug to me. openssh depends on autoconf which depends on perl. Apparently you have autoconf but not perl. Is perl really not there? There is a related bug here: http://bugs.gentoo.org/show_bug.cgi?id=70984 Zac __ Discover Yahoo! Get on-the-go sports scores, stock quotes, news and more. Check it out! http://discover.yahoo.com/mobile.html -- gentoo-user@gentoo.org mailing list
