Unresolved Symbols question lm_sensors 2.8.0/i2c 2.8.0/linux

Unresolved Symbols question lm_sensors 2.8.0/i2c 2.8.0/linux

[Yermo M. Lamers]

I am getting an unresolved symbol (dmi_scan_match) trying to install 
lm_sensors 2.8.0 and i2c 2.8.0 under stock RedHat Linux 9.0 install.

I am running on a SuperMicro Dual PIII P3TDLE motherboard.

     http://www.supermicro.com/PRODUCT/MotherBoards/RCC_LE/P3TDLE.htm

I have not been able to verify what sensor chip it uses but from lspci -v:

00:0f.0 ISA bridge: ServerWorks OSB4 South Bridge (rev 51)
	Subsystem: ServerWorks OSB4 South Bridge
	Flags: bus master, medium devsel, latency 0


Output from sensors_detect:

[root@nbi_master lm_sensors-2.8.0]# ./prog/detect/sensors-detect
  This program will help you to determine which I2C/SMBus modules you 
need to
  load to use lm_sensors most effectively.
  You need to have done a `make install', issued a `depmod -a' and made sure
  `/etc/conf.modules' (or `/etc/modules.conf') contains the appropriate
  module path before you can use some functions of this utility. Read
  doc/modules for more information.
  Also, you need to be `root', or at least have access to the 
/dev/i2c[-/]* files for some things. You can use prog/mkdev/mkdev.sh to 
create these /dev files
  if you do not have them already.
  If you have patched your kernel and have some drivers built-in you can
  safely answer NO if asked to load some modules. In this case, things may
  seem a bit confusing, but they will still work.

  BIOS vendor (ACPI): AMI
  System vendor (DMI): Supermicro
  BIOS version (DMI): 0700xx
  We can start with probing for (PCI) I2C or SMBus adapters.
  You do not need any special privileges for this.
  Do you want to probe now? (YES/no):
Probing for PCI bus adapters...
Use driver `i2c-piix4' for device 00:0f.0: ServerWorks OSB4 South Bridge
Probe succesfully concluded.

  We will now try to load each adapter module in turn.
Load `i2c-piix4' (say NO if built into your kernel)? (YES/no):
/lib/modules/2.4.20-8smp/kernel/drivers/i2c/busses/i2c-piix4.o: 
unresolved symbol dmi_scan_mach
/lib/modules/2.4.20-8smp/kernel/drivers/i2c/busses/i2c-piix4.o: insmod 
/lib/modules/2.4.20-8smp/kernel/drivers/i2c/busses/i2c-piix4.o failed
/lib/modules/2.4.20-8smp/kernel/drivers/i2c/busses/i2c-piix4.o: insmod 
i2c-piix4 failed
Loading failed... skipping.
  Do you now want to be prompted for non-detectable adapters? (yes/NO):

I have the corresponding source for the kernel I am running:

[root@nbi_master i2c-2.8.0]# cat /proc/version
Linux version 2.4.20-8smp (bhcompile@porky.devel.redhat.com) (gcc 
version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)) #1 SMP Thu Mar 13 
17:45:54 EST 2003

[root@nbi_master i2c-2.8.0]# ls /lib/modules/2.4.20-8smp/build/
arch             Documentation  kernel       README
configs          drivers        lib          REPORTING-BUGS
COPYING          fs             MAINTAINERS  Rules.make
COPYING.modules  include        Makefile     scripts
CREDITS          init           mm           tmp_include_depends
crypto           ipc            net


What am I doing wrong?

If I can be of any assistance in tracking this down please contact me 
here at yml@yml.com

thank you for your time,

-- Yermo


-- 
---------------------------------------------------------------------
DTLink Software                                 http://www.dtlink.com
---------------------------------------------------------------------

Unresolved Symbols question lm_sensors 2.8.0/i2c 2.8.0/linux

[Jean Delvare]

> I am getting an unresolved symbol (dmi_scan_match) trying to install 
> lm_sensors 2.8.0 and i2c 2.8.0 under stock RedHat Linux 9.0 install.

This symbol is exported by the dmi_scan module, which ships with
lm_sensors. Don't you have it? You really should, if you were able to
compile i2c-piix4.

-- 
Jean Delvare
http://www.ensicaen.ismra.fr/~delvare/

Unresolved Symbols question lm_sensors 2.8.0/i2c 2.8.0/linux

[Yermo M. Lamers]

>>I am getting an unresolved symbol (dmi_scan_match) trying to install 
>>lm_sensors 2.8.0 and i2c 2.8.0 under stock RedHat Linux 9.0 install.
> 
> This symbol is exported by the dmi_scan module, which ships with
> lm_sensors. Don't you have it? You really should, if you were able to
> compile i2c-piix4.

Yea, I crawled through the code. I believe it's either user error on my 
part or a bug.

i2c-piix4 compiled just fine:

root@nbi_master lm_sensors-2.8.0]# find . -name "*piix4*"
./doc/busses/i2c-piix4
./kernel/busses/i2c-piix4.c
./kernel/busses/i2c-piix4.d
./kernel/busses/i2c-piix4.o

[root@nbi_master lm_sensors-2.8.0]# find . -exec fgrep -l dmi_scan_mach 
{} \;
./kernel/busses/dmi_scan.c
./kernel/busses/i2c-piix4.c
./kernel/busses/i2c-piix4.o

Maybe it's something simple stupid I did (wouldn't be the first time).

Build i2c-2.8.0
make, make install, depmod -aij

build lm_sensors

make, make install, depmod -a

do the ldconfig thing.

do the sensors-detect thing.

get the unresolved symbol I reported.

How is dmi-scan linked in?

---------------------------------------------------------------------
DTLink Software                                 http://www.dtlink.com
---------------------------------------------------------------------

Unresolved Symbols question lm_sensors 2.8.0/i2c 2.8.0/linux

[Jean Delvare]

> i2c-piix4 compiled just fine:
> 
> root@nbi_master lm_sensors-2.8.0]# find . -name "*piix4*"
> ./doc/busses/i2c-piix4
> ./kernel/busses/i2c-piix4.c
> ./kernel/busses/i2c-piix4.d
> ./kernel/busses/i2c-piix4.o
> 
> [root@nbi_master lm_sensors-2.8.0]# find . -exec fgrep -l
> dmi_scan_mach {} \;
> ./kernel/busses/dmi_scan.c
> ./kernel/busses/i2c-piix4.c
> ./kernel/busses/i2c-piix4.o

What about 'find . -name "*dmi_scan*"'?

> Maybe it's something simple stupid I did (wouldn't be the first time).
> 
> Build i2c-2.8.0
> make, make install, depmod -aij
> 
> build lm_sensors
> 
> make, make install, depmod -a
> 
> do the ldconfig thing.
> 
> do the sensors-detect thing.

Looks good. Doesn't depmod -a complain about the missing symbol?

> get the unresolved symbol I reported.

OK, not so good ;)

> How is dmi-scan linked in?

dmi_scan is a kernel module, exactly as i2c-piix4 is, and i2c-piix4
depends on it. It looks like you were able to build the second without
the first, which should not happend. Could you try explicitely asking
for it? 'make kernel/busses/dmi_scan.o' should do it. BTW, could you
give a try to i2c/lm_sensors CVS, in case it changes something? (I think
I remember we made some adjustements to the build process right after -
or was it right before - the 2.8.0 release.)

Thanks.

-- 
Jean Delvare
http://www.ensicaen.ismra.fr/~delvare/

Unresolved Symbols question lm_sensors 2.8.0/i2c 2.8.0/linux

[Yermo M. Lamers]

>>dmi_scan_mach {} \;
>>./kernel/busses/dmi_scan.c
>>./kernel/busses/i2c-piix4.c
>>./kernel/busses/i2c-piix4.o
> 
> What about 'find . -name "*dmi_scan*"'?

Hmmmmm. It looks like that didn't get compiled .. maybe I missed some 
errors during the make?

[root@nbi_master lm_sensors-2.8.0]# find . -name "*dmi_scan*"
./kernel/busses/dmi_scan.c
./kernel/busses/dmi_scan.h

>>do the sensors-detect thing.
> 
> Looks good. Doesn't depmod -a complain about the missing symbol?

I must've missed that. It does in fact complain about the unresolved symbol.


>>How is dmi-scan linked in?
> 
> dmi_scan is a kernel module, exactly as i2c-piix4 is, and i2c-piix4
> depends on it. It looks like you were able to build the second without
> the first, which should not happend. Could you try explicitely asking
> for it? 'make kernel/busses/dmi_scan.o'

Here's what I get:

[root@nbi_master lm_sensors-2.8.0]# make kernel/busses/dmi_scan.o
grep: /lib/modules/2.4.20-8smp/build/.config: No such file or directory
grep: /lib/modules/2.4.20-8smp/build/.config: No such file or directory
grep: /lib/modules/2.4.20-8smp/build/.config: No such file or directory
grep: /lib/modules/2.4.20-8smp/build/.config: No such file or directory
grep: /lib/modules/2.4.20-8smp/build/.config: No such file or directory
grep: /lib/modules/2.4.20-8smp/build/.config: No such file or directory
grep: /lib/modules/2.4.20-8smp/build/.config: No such file or directory
grep: /lib/modules/2.4.20-8smp/build/.config: No such file or directory
grep: /lib/modules/2.4.20-8smp/build/.config: No such file or directory
grep: /lib/modules/2.4.20-8smp/build/.config: No such file or directory
grep: /lib/modules/2.4.20-8smp/build/.config: No such file or directory
grep: /lib/modules/2.4.20-8smp/build/.config: No such file or directory
grep: /lib/modules/2.4.20-8smp/build/.config: No such file or directory
grep: /lib/modules/2.4.20-8smp/build/.config: No such file or directory
grep: /lib/modules/2.4.20-8smp/build/.config: No such file or directory
grep: /lib/modules/2.4.20-8smp/build/.config: No such file or directory
grep: /lib/modules/2.4.20-8smp/build/.config: No such file or directory
grep: /lib/modules/2.4.20-8smp/build/.config: No such file or directory
grep: /lib/modules/2.4.20-8smp/build/.config: No such file or directory
grep: /lib/modules/2.4.20-8smp/build/.config: No such file or directory
grep: /lib/modules/2.4.20-8smp/build/.config: No such file or directory
grep: /lib/modules/2.4.20-8smp/build/.config: No such file or directory
grep: /lib/modules/2.4.20-8smp/build/.config: No such file or directory
grep: /lib/modules/2.4.20-8smp/build/.config: No such file or directory
grep: /lib/modules/2.4.20-8smp/build/.config: No such file or directory
grep: /lib/modules/2.4.20-8smp/build/.config: No such file or directory
grep: /lib/modules/2.4.20-8smp/build/.config: No such file or directory
grep: /lib/modules/2.4.20-8smp/build/.config: No such file or directory
grep: /lib/modules/2.4.20-8smp/build/.config: No such file or directory
grep: /lib/modules/2.4.20-8smp/build/.config: No such file or directory
grep: /lib/modules/2.4.20-8smp/build/.config: No such file or directory
grep: /lib/modules/2.4.20-8smp/build/.config: No such file or directory
grep: /lib/modules/2.4.20-8smp/build/.config: No such file or directory
grep: /lib/modules/2.4.20-8smp/build/.config: No such file or directory
grep: /lib/modules/2.4.20-8smp/build/.config: No such file or directory
grep: /lib/modules/2.4.20-8smp/build/.config: No such file or directory
grep: /lib/modules/2.4.20-8smp/build/.config: No such file or directory
grep: /lib/modules/2.4.20-8smp/build/.config: No such file or directory
grep: /lib/modules/2.4.20-8smp/build/.config: No such file or directory
grep: /lib/modules/2.4.20-8smp/build/.config: No such file or directory
grep: /lib/modules/2.4.20-8smp/build/.config: No such file or directory
grep: /lib/modules/2.4.20-8smp/build/.config: No such file or directory
grep: /lib/modules/2.4.20-8smp/build/.config: No such file or directory
grep: /lib/modules/2.4.20-8smp/build/.config: No such file or directory
grep: /lib/modules/2.4.20-8smp/build/.config: No such file or directory
grep: /lib/modules/2.4.20-8smp/build/.config: No such file or directory
grep: /lib/modules/2.4.20-8smp/build/.config: No such file or directory
grep: /lib/modules/2.4.20-8smp/build/.config: No such file or directory
grep: /lib/modules/2.4.20-8smp/build/.config: No such file or directory
grep: /lib/modules/2.4.20-8smp/build/.config: No such file or directory
grep: /lib/modules/2.4.20-8smp/build/.config: No such file or directory
grep: /lib/modules/2.4.20-8smp/build/.config: No such file or directory
gcc  -D__SMP__ -DMODVERSIONS -include 
/lib/modules/2.4.20-8smp/build/include/linux/modversions.h -D__KERNEL__ 
-DMODULE -DEXPORT_SYMTAB -fomit-frame-pointer -I. -Ikernel/include 
-I/usr/local/include -I/lib/modules/2.4.20-8smp/build/include  -nostdinc 
-I /usr/lib/gcc-lib/i386-redhat-linux/3.2.2/include  -Wall -O2   -c 
kernel/busses/dmi_scan.c -o kernel/busses/dmi_scan.o

Seems to have compiled

> give a try to i2c/lm_sensors CVS, in case it changes something? (I think
> I remember we made some adjustements to the build process right after -
> or was it right before - the 2.8.0 release.)

I can certainly do that.

If you like I can also give you an ssh login with root access on this 
box. It's not yet being used for anything ...

---------------------------------------------------------------------
DTLink Software                                 http://www.dtlink.com
---------------------------------------------------------------------

Unresolved Symbols question lm_sensors 2.8.0/i2c 2.8.0/linux

[Mark M. Hoffman]

* Yermo M. Lamers <yml@yml.com> [2003-10-03 15:46:52 -0400]:

<snip>

> Here's what I get:
> 
> [root@nbi_master lm_sensors-2.8.0]# make kernel/busses/dmi_scan.o
> grep: /lib/modules/2.4.20-8smp/build/.config: No such file or directory

<snip>

This is the (RedHat specific) problem.  You need to copy the matching
config from /usr/src/linux-2.4/configs/<blah> to /usr/src/linux-2.4/.config
The missing file above is actually a link to...  ^^^^^^^^^^^^^^^^^^^^^^^^^^

Then start over.  Be sure to "make clean" in i2c and lm_sensors2 first.

Everyone else: why don't we simply fail compilation without this file?

Regards,

-- 
Mark M. Hoffman
mhoffman@lightlink.com

Unresolved Symbols question lm_sensors 2.8.0/i2c 2.8.0/linux

[Yermo M. Lamers]

That fixed it. I am now successfully running lm_sensors 2.8.0 under 
stock redhat 9.

Thank you /very/ much. You guys rock.

-- Yermo

Mark M. Hoffman wrote:
> * Yermo M. Lamers <yml@yml.com> [2003-10-03 15:46:52 -0400]:
> 
> <snip>
> 
>>Here's what I get:
>>
>>[root@nbi_master lm_sensors-2.8.0]# make kernel/busses/dmi_scan.o
>>grep: /lib/modules/2.4.20-8smp/build/.config: No such file or directory
> 
> 
> <snip>
> 
> This is the (RedHat specific) problem.  You need to copy the matching
> config from /usr/src/linux-2.4/configs/<blah> to /usr/src/linux-2.4/.config
> The missing file above is actually a link to...  ^^^^^^^^^^^^^^^^^^^^^^^^^^
> 
> Then start over.  Be sure to "make clean" in i2c and lm_sensors2 first.
> 
> Everyone else: why don't we simply fail compilation without this file?
> 
> Regards,
> 

-- 
---------------------------------------------------------------------
DTLink Software                                 http://www.dtlink.com
---------------------------------------------------------------------

Unresolved Symbols question lm_sensors 2.8.0/i2c 2.8.0/linux

[Yermo M. Lamers]

Thank you for all your help. I received a message from 
mhoffman@lightlink.com who suggested that the /usr/src/linux-2.4/.config 
file was missing and that I needed to copy 
/usr/src/linux-2.4/configs/<DEFANGED_appropriate config file> to the .config above.

I did that, redid the install and now everything compiles correctly and 
I was able to run the sensors executable.

Thank you very much for all you help. This rocks.

-- Yermo

Jean Delvare wrote:
>>i2c-piix4 compiled just fine:
>>
>>root@nbi_master lm_sensors-2.8.0]# find . -name "*piix4*"
>>./doc/busses/i2c-piix4
>>./kernel/busses/i2c-piix4.c
>>./kernel/busses/i2c-piix4.d
>>./kernel/busses/i2c-piix4.o
>>
>>[root@nbi_master lm_sensors-2.8.0]# find . -exec fgrep -l
>>dmi_scan_mach {} \;
>>./kernel/busses/dmi_scan.c
>>./kernel/busses/i2c-piix4.c
>>./kernel/busses/i2c-piix4.o
> 
> 
> What about 'find . -name "*dmi_scan*"'?
> 
> 
>>Maybe it's something simple stupid I did (wouldn't be the first time).
>>
>>Build i2c-2.8.0
>>make, make install, depmod -aij
>>
>>build lm_sensors
>>
>>make, make install, depmod -a
>>
>>do the ldconfig thing.
>>
>>do the sensors-detect thing.
> 
> 
> Looks good. Doesn't depmod -a complain about the missing symbol?
> 
> 
>>get the unresolved symbol I reported.
> 
> 
> OK, not so good ;)
> 
> 
>>How is dmi-scan linked in?
> 
> 
> dmi_scan is a kernel module, exactly as i2c-piix4 is, and i2c-piix4
> depends on it. It looks like you were able to build the second without
> the first, which should not happend. Could you try explicitely asking
> for it? 'make kernel/busses/dmi_scan.o' should do it. BTW, could you
> give a try to i2c/lm_sensors CVS, in case it changes something? (I think
> I remember we made some adjustements to the build process right after -
> or was it right before - the 2.8.0 release.)
> 
> Thanks.
> 

-- 
---------------------------------------------------------------------
DTLink Software                                 http://www.dtlink.com
---------------------------------------------------------------------

Unresolved Symbols question lm_sensors 2.8.0/i2c 2.8.0/linux

[Yermo M. Lamers]

[root@nbi_master root]# lsmod
Module                  Size  Used by    Not tainted
eeprom                  4688   0  (unused)
lm87                    7776   0  (unused)
i2c-proc                8084   0  [eeprom lm87]
i2c-piix4               4424   0  (unused)
dmi_scan                2148   0  [i2c-piix4]
i2c-core               20196   0  [eeprom lm87 i2c-proc i2c-piix4]
autofs                 13684   0  (autoclean) (unused)
e100                   62340   1
ipt_REJECT              3928   6  (autoclean)
iptable_filter          2412   1  (autoclean)
ip_tables              15864   2  [ipt_REJECT iptable_filter]
keybdev                 2976   0  (unused)
mousedev                5656   0  (unused)
hid                    22308   0  (unused)
input                   6208   0  [keybdev mousedev hid]
usb-ohci               22216   0  (unused)
usbcore                82592   1  [hid usb-ohci]
ext3                   73376   1
jbd                    56336   1  [ext3]
raid1                  16044   2
aic79xx               142084   4
sd_mod                 13452   8
scsi_mod              110488   2  [aic79xx sd_mod]

Another question.

this is a Dual PIII SuperMicro board. The P3TDLE.

lm_sensors (and i2c) 2.8.0. under Redhat 9.

[root@nbi_master root]# cat /proc/version
Linux version 2.4.20-8smp (bhcompile@porky.devel.redhat.com) (gcc 
version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)) #1 SMP Thu Mar 13 
17:45:54 EST 2003

Here is the output I'm getting from sensors:

[root@nbi_master root]# sensors
lm87-i2c-0-2e
Adapter: SMBus PIIX4 adapter at 0580
Algorithm: Non-I2C SMBus adapter
2.5V:      +0.00 V  (min =  +2.36 V, max =  +2.63 V)   ALARM
Vccp1:     +1.43 V  (min =  +1.36 V, max =  +1.51 V)
3.3V:      +3.31 V  (min =  +3.12 V, max =  +3.47 V)
5V:        +5.13 V  (min =  +4.73 V, max =  +5.26 V)
12V:      +12.25 V  (min = +11.37 V, max = +12.62 V)
Vccp2:     +0.00 V  (min =  +1.36 V, max =  +1.51 V)   ALARM
fan1:     3308 RPM  (min = 3000 RPM, div = 2)
fan2:     3308 RPM  (min = 3000 RPM, div = 2)
temp1:       +34?C  (min =  +10?C, max =  +60?C)
CPU_Temp:    +36?C  (min =  +10?C, max =  +60?C)
vid:       +1.45 V

lm87-i2c-0-2e
Adapter: SMBus PIIX4 adapter at 0580
Algorithm: Non-I2C SMBus adapter
2.5V:      +0.00 V  (min =  +2.36 V, max =  +2.63 V)   ALARM
Vccp1:     +1.43 V  (min =  +1.36 V, max =  +1.51 V)
3.3V:      +3.31 V  (min =  +3.12 V, max =  +3.47 V)
5V:        +5.13 V  (min =  +4.73 V, max =  +5.26 V)
12V:      +12.25 V  (min = +11.37 V, max = +12.62 V)
Vccp2:     +0.00 V  (min =  +1.36 V, max =  +1.51 V)   ALARM
fan1:     3308 RPM  (min = 3000 RPM, div = 2)
fan2:     3308 RPM  (min = 3000 RPM, div = 2)
temp1:       +34?C  (min =  +10?C, max =  +60?C)
CPU_Temp:    +36?C  (min =  +10?C, max =  +60?C)
vid:       +1.45 V

eeprom-i2c-0-50
Adapter: SMBus PIIX4 adapter at 0580
Algorithm: Non-I2C SMBus adapter
Memory type:            SDRAM DIMM SPD
Memory size (MB):       512

eeprom-i2c-0-51
Adapter: SMBus PIIX4 adapter at 0580
Algorithm: Non-I2C SMBus adapter
Memory type:            SDRAM DIMM SPD
Memory size (MB):       512

I'm assuming the duplicate entries at the top are what's mentioned in 
the FAQ, right?

My issue is that the second CPU Temparature is not showing up. From what 
I can tell temp1 is the case ambient temperature. Did I miss something 
in the configuration?

I'm assuming the voltage alarms are for things that are not hooked up, no?

The sensor itself seems to be working as evidenced by BIOS setup.

thanks,

-- Yermo


Other info:

[root@nbi_master root]# lsmod
Module                  Size  Used by    Not tainted
eeprom                  4688   0  (unused)
lm87                    7776   0  (unused)
i2c-proc                8084   0  [eeprom lm87]
i2c-piix4               4424   0  (unused)
dmi_scan                2148   0  [i2c-piix4]
i2c-core               20196   0  [eeprom lm87 i2c-proc i2c-piix4]
autofs                 13684   0  (autoclean) (unused)
e100                   62340   1
ipt_REJECT              3928   6  (autoclean)
iptable_filter          2412   1  (autoclean)
ip_tables              15864   2  [ipt_REJECT iptable_filter]
keybdev                 2976   0  (unused)
mousedev                5656   0  (unused)
hid                    22308   0  (unused)
input                   6208   0  [keybdev mousedev hid]
usb-ohci               22216   0  (unused)
usbcore                82592   1  [hid usb-ohci]
ext3                   73376   1
jbd                    56336   1  [ext3]
raid1                  16044   2
aic79xx               142084   4
sd_mod                 13452   8
scsi_mod              110488   2  [aic79xx sd_mod]

Mark M. Hoffman wrote:
> * Yermo M. Lamers <yml@yml.com> [2003-10-03 15:46:52 -0400]:
> 
> <snip>
> 
>>Here's what I get:
>>
>>[root@nbi_master lm_sensors-2.8.0]# make kernel/busses/dmi_scan.o
>>grep: /lib/modules/2.4.20-8smp/build/.config: No such file or directory
> 
> 
> <snip>
> 
> This is the (RedHat specific) problem.  You need to copy the matching
> config from /usr/src/linux-2.4/configs/<blah> to /usr/src/linux-2.4/.config
> The missing file above is actually a link to...  ^^^^^^^^^^^^^^^^^^^^^^^^^^
> 
> Then start over.  Be sure to "make clean" in i2c and lm_sensors2 first.
> 
> Everyone else: why don't we simply fail compilation without this file?
> 
> Regards,
> 

-- 
---------------------------------------------------------------------
DTLink Software                                 http://www.dtlink.com
---------------------------------------------------------------------

Unresolved Symbols question lm_sensors 2.8.0/i2c 2.8.0/linux

[Jean Delvare]

> Everyone else: why don't we simply fail compilation without this file?
> ($LINUX/.config)

Agreed, that would avoid some problems. But how would you do that,
technically speaking? I admit I don't know how I would do it.

-- 
Jean Delvare
http://www.ensicaen.ismra.fr/~delvare/

Unresolved Symbols question lm_sensors 2.8.0/i2c

[Mark Studebaker]

I've added a dependency and a bomb-out message if it doesn't exist.
see how you like it.

Jean Delvare wrote:
> 
> > Everyone else: why don't we simply fail compilation without this file?
> > ($LINUX/.config)
> 
> Agreed, that would avoid some problems. But how would you do that,
> technically speaking? I admit I don't know how I would do it.
> 
> --
> Jean Delvare
> http://www.ensicaen.ismra.fr/~delvare/