Re: [gentoo-amd64] problem with gcc -m32
On Tue, February 22, 2005 7:01 am, John Myers said: On Monday 21 February 2005 15:34, John Myers wrote: I am trying to emerge wine. It seems to want to compile with -m32. This is nifty. However, It fails, with 'C compiler cannot create executables'. But not for the same reason as the common one here: It can't find a suitable libc. I've tried re-emerging glibc, gcc, binutils, and always somewhere end up with this same error. What am I doing wrong? Well, I fixed that problem. I did a few things, so I don't remember which it was, though. Now, however, I am now getting the same error someone on the forums was getting regarding -lXext. I'll look into that next. Hmm... now it's not configuring at all. I'll have to get a fresh copy of the ebuild when I get home, as I've been mucking around in it. Could the multilib eclass help any? -- t3h 3l3ctr0n3rd [EMAIL PROTECTED] Supermarket Deli Clerk and Student Programmer OpenPGP Key Fingerprint: 0A65 EEFA B23A F0AC E6C2 C71C BEA0 E055 BE0E EC25 -- gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] lib = 32, lib64 = 64 is better
Hi, lib = 32, lib64 = 64 is better This is our final goal for 2005.1 IIRC. To catch programs that put their 64bit-libraries into lib, you can stick multilib-strict in your FEATURES, but don't expect your system working for now. I already created a little template to report multilib-strict bugs: http://tinyurl.com/4k3tb Greetings, blubb -- gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] lib = 32, lib64 = 64 is better
Antoine Martin [EMAIL PROTECTED] wrote: On Mon, 2005-02-21 at 19:18 -0600, [EMAIL PROTECTED] wrote: Antoine Martin [EMAIL PROTECTED] wrote: Bearing in mind that I have not been confronted to any of these issues, I can't think of a reason why a piece of software should rely on hard-coded paths. By hard-coded do you mean to exclude software that sets paths at compile time, or do you mean run time? For shared libraries, both, I thought that ld.so.conf friends were supposed to take care of things like that. They do, which makes it unimportant at run-time what the library directories are called. So we should all switch to SuSE 9.2 and use only binary packages. :) Now, the default directories for program specific libs and data (ie: /usr/lib/myprogram/*) obviously need to remain a compile time option. Or am I missing something here? My problem was with plug-ins and so it was a compile time option like what you say. Maybe we could use a database for looking up the locations of things, given a key, and then you could install program components anywhere. -- [EMAIL PROTECTED]http://www.chemoelectric.org I have directed that in the future I sign each letter. -- Rumsfeld pgpthpWUP0UNl.pgp Description: PGP signature
[gentoo-amd64] problem with X configuration
I've been following the suggestions made here as well as the documentation on xorg.conf and nvidia. I continue to have the same issue though. The color depth is off - my desktop background is grainy, and if I open more than one window, like Firefox and a terminal, the colors on the inactive window change to like 8 colors displayed. Here is my xorg.conf file: Section ServerLayout Identifier X.org Configured Screen 0 Screen0 0 0 InputDeviceMouse0 CorePointer InputDeviceKeyboard0 CoreKeyboard EndSection Section Files RgbPath /usr/lib/X11/rgb ModulePath /usr/lib/modules FontPath /usr/share/fonts/misc/ FontPath /usr/share/fonts/TTF/ FontPath /usr/share/fonts/Type1/ FontPath /usr/share/fonts/CID/ FontPath /usr/share/fonts/75dpi/ FontPath /usr/share/fonts/100dpi/ EndSection Section Module Load extmod # Load dri Load dbe Load record Load xtrap Load glx Load type1 Load freetype EndSection Section InputDevice Identifier Keyboard0 Driver kbd EndSection Section InputDevice Identifier Mouse0 Driver mouse Option Protocol auto Option Device /dev/mouse EndSection Section Monitor Identifier Monitor0 VendorName Monitor Vendor ModelNameMonitor Model EndSection Section Device ### Available Driver options are:- ### Values: i: integer, f: float, bool: True/False, ### string: String, freq: f Hz/kHz/MHz ### [arg]: arg optional #Option DigitalVibrance # i #Option NoFlip # [bool] #Option Dac8Bit # [bool] #Option NoLogo # [bool] #Option UBB # [bool] #Option Stereo # i #Option SWcursor# [bool] #Option HWcursor# [bool] #Option VideoKey# i #Option NvAGP # i #Option IgnoreEDID # [bool] #Option NoDDC # [bool] #Option ConnectedMonitor# str #Option ConnectedMonitors # str #Option TVStandard # str #Option TVOutFormat # str #Option RenderAccel # [bool] #Option CursorShadow# [bool] #Option CursorShadowAlpha # i #Option CursorShadowXOffset # i #Option CursorShadowYOffset # i #Option UseEdidFreqs# [bool] #Option FlatPanelProperties # str #Option TwinView# [bool] #Option TwinViewOrientation # str #Option SecondMonitorHorizSync # str #Option SecondMonitorVertRefresh # str #Option MetaModes # str #Option UseInt10Module # [bool] #Option NoTwinViewXineramaInfo # [bool] #Option NoRenderExtension # [bool] #Option Overlay # [bool] #Option CIOverlay # [bool] #Option ForceEmulatedOverlay # [bool] #Option TransparentIndex# i #Option OverlayDefaultVisual # [bool] #Option NvEmulate # i #Option NoBandWidthTest # [bool] #Option CustomEDID-CRT-0# str #Option CustomEDID-CRT-1# str #Option CustomEDID-DFP-0# str #Option CustomEDID-DFP-1# str #Option CustomEDID-TV-0 # str #Option CustomEDID-TV-1 # str #Option TVOverScan # f #Option IgnoreDisplayDevices # str #Option MultisampleCompatibility # [bool] #Option RegistryDwords # str #Option RegistryBinary # str #Option NoPowerConnectorCheck # [bool] #Option AllowDFPStereo # [bool] #Option XvMCUsesTextures# [bool] #Option HorizSync # str #Option VertRefresh # str #Option AllowGLXWithComposite # [bool] Identifier Card0 Driver nvidia VendorName nVidia Corporation BoardName Unknown Board BusID PCI:1:0:0 EndSection Section Screen Identifier Screen0 Device Card0 MonitorMonitor0 SubSection Display Depth 24 Modes 1600x1200 EndSubSection EndSection When I run glxinfo | grep direct, it returns: error: couldn't find RGB GLX visual. Thanks for any help you can provide! -- Mark Creamer -- gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] problem with X configuration
Mark Creamer [EMAIL PROTECTED] wrote: Section Screen Identifier Screen0 Device Card0 MonitorMonitor0 SubSection Display Depth 24 Modes 1600x1200 EndSubSection EndSection Your monitor can handle 1600x1200 resolution? I would try 1280x1024 or 1152x864. Maybe your monitor is barfing. -- [EMAIL PROTECTED]http://www.chemoelectric.org I have directed that in the future I sign each letter. -- Rumsfeld pgpp8YDJnhWxx.pgp Description: PGP signature
[gentoo-amd64] can't mount DVD -- no medium found
ok, i can't mount dvds. i could a few days ago but now, no dice. the only thing I did was burn a dvd-r. i'm getting kind of frustrated. i think this is a udev issue of some sort... [EMAIL PROTECTED] ~ $ dmesg | grep LITE hdc: LITE-ON DVDRW SOHW-1633S, ATAPI CD/DVD-ROM drive [EMAIL PROTECTED] ~ $ ls -l /dev/cdroms/cdrom0 lrwxrwxrwx 1 root root 6 Feb 22 16:36 /dev/cdroms/cdrom0 - ../hdc [EMAIL PROTECTED] ~ $ mount /mnt/cdrom mount: block device /dev/cdroms/cdrom0 is write-protected, mounting read-only mount: I could not determine the filesystem type, and none was specified [EMAIL PROTECTED] ~ $ sudo mount -t iso9660 /dev/cdroms/cdrom0 /mnt/cdrom mount: block device /dev/cdroms/cdrom0 is write-protected, mounting read-only mount: wrong fs type, bad option, bad superblock on /dev/cdroms/cdrom0, or too many mounted file systems what gives? any help at all would be greatly appreciated! i'm a n00b to gentoo so please bear with me. sean -- gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] can't mount DVD -- no medium found
Could we see your fstab, please? Seanny wrote: ok, i can't mount dvds. i could a few days ago but now, no dice. the only thing I did was burn a dvd-r. i'm getting kind of frustrated. i think this is a udev issue of some sort... [EMAIL PROTECTED] ~ $ dmesg | grep LITE hdc: LITE-ON DVDRW SOHW-1633S, ATAPI CD/DVD-ROM drive [EMAIL PROTECTED] ~ $ ls -l /dev/cdroms/cdrom0 lrwxrwxrwx 1 root root 6 Feb 22 16:36 /dev/cdroms/cdrom0 - ../hdc [EMAIL PROTECTED] ~ $ mount /mnt/cdrom mount: block device /dev/cdroms/cdrom0 is write-protected, mounting read-only mount: I could not determine the filesystem type, and none was specified [EMAIL PROTECTED] ~ $ sudo mount -t iso9660 /dev/cdroms/cdrom0 /mnt/cdrom mount: block device /dev/cdroms/cdrom0 is write-protected, mounting read-only mount: wrong fs type, bad option, bad superblock on /dev/cdroms/cdrom0, or too many mounted file systems what gives? any help at all would be greatly appreciated! i'm a n00b to gentoo so please bear with me. sean -- gentoo-amd64@gentoo.org mailing list -- gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] problem with X configuration
I checked the manual, and it says 1280x1024 @ 85Hz is recommended. I set the 1280x1024, but didn't see anyplace to set the refresh rate. Anyway, after a reboot, same result so far On Tuesday 22 February 2005 10:08 pm, [EMAIL PROTECTED] wrote: Mark Creamer [EMAIL PROTECTED] wrote: Section Screen Identifier Screen0 Device Card0 MonitorMonitor0 SubSection Display Depth 24 Modes 1600x1200 EndSubSection EndSection Your monitor can handle 1600x1200 resolution? I would try 1280x1024 or 1152x864. Maybe your monitor is barfing. -- Mark Creamer -- gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] problem with X configuration
Mark Creamer [EMAIL PROTECTED] wrote: When I run glxinfo | grep direct, it returns: error: couldn't find RGB GLX visual. I would try changing Driver nvidia to Driver nv and run opengl-update xorg-x11 and that way at least you will see if it has anything to do with the nvidia driver. I checked the manual, and it says 1280x1024 @ 85Hz is recommended. I set the 1280x1024, but didn't see anyplace to set the refresh rate. Anyway, after a reboot, same result so far Here's an excerpt from my xorg.conf that might help you figure it out: Section Monitor Identifier BenQ FP951 LCD monitor VendorName BenQ ModelName FP951 HorizSync 30-82 VertRefresh 56-76 EndSection -- [EMAIL PROTECTED]http://www.chemoelectric.org I have directed that in the future I sign each letter. -- Rumsfeld pgpXis9shUeDB.pgp Description: PGP signature
Re: [gentoo-amd64] can't mount DVD -- no medium found
Renzo, Thanks man. That is a problem, however, it hasn't fixed anything: lilfoo udf # modprobe udf lilfoo udf # lsmod Module Size Used by udf81544 0 snd_ioctl3218048 0 snd_pcm_oss56360 0 snd_mixer_oss 19584 3 snd_pcm_oss snd_seq_oss34176 0 snd_seq_midi_event 8832 1 snd_seq_oss snd_seq54592 4 snd_seq_oss,snd_seq_midi_event snd_seq_device 9100 2 snd_seq_oss,snd_seq eth139422032 0 uhci_hcd 31520 0 ohci1394 33668 0 ieee1394 117592 2 eth1394,ohci1394 ehci_hcd 30852 0 ohci_hcd 21124 0 nvidia 4055164 12 lilfoo udf # exit exit [EMAIL PROTECTED] ~ $ mount /mnt/cdrom mount: block device /dev/cdroms/cdrom0 is write-protected, mounting read-only mount: I could not determine the filesystem type, and none was specified [EMAIL PROTECTED] ~ $ sudo mount -t udf /dev/cdroms/cdrom0 /mnt/cdrom mount: block device /dev/cdroms/cdrom0 is write-protected, mounting read-only mount: wrong fs type, bad option, bad superblock on /dev/cdroms/cdrom0, or too many mounted file systems On Tue, February 22, 2005 11:58 pm, Renzo Rosales said: Did you enable UDF support in your kernel? http://forums.gentoo.org/viewtopic-t-299303.html -- gentoo-amd64@gentoo.org mailing list
