[=B1¤=B0=ED]=C0=E7=C5=C3 "º=CE=BE=F7"=C0Ô=B4=CF=B4Ù.

±ÍÇÏÀÇ ¸ÞÀÏÁÖ¼Ò´Â À¥¼­ÇÎÁß ¾Ë°Ô µÈ°ÍÀ̸ç, E-Mail ÁÖ¼Ò ¿Ü¿¡, ´Ù¸¥ Á¤º¸´Â °®°í ÀÖÁö ¾Ê½À´Ï´Ù. Á¤ÅëºÎ ±Ç°í»çÇ׿¡ ÀÇ°Å Á¦¸ñ¿¡ [±¤°í]¶ó°í Ç¥±âÇÑ ¸ÞÀÏÀÔ´Ï´Ù. ¿øÄ¡ ¾ÊÀ¸¸é ¼ö½Å°ÅºÎ ¸¦ ´­·¯ÁÖ¼¼¿ä ÇÏ·ç 30ºÐ ÅõÀÚÇϽøé Á¤¸» ±¦ÂúÀº ºÎ¾÷ÀÔ´Ï´Ù. ÃÖ°íÀÇ º¸»ó Ç÷£À» ÀÚ¶ûÇÏ´Â »çÀÌÆ

Re: installing stripped kernel modules

> Harlan> The strip options for programs are "too aggressive" for kernel > Harlan> modules. > > Harlan> Some Makefile.am's will install both programs and kernel > Harlan> modules. > > Harlan> What are the choices for altering the strip flags? > > You have a few choices. > > You could set the I

Re: How to handle a non-compilable file.

> There's no point in listing the .xpm files in noinst_DATA if you're > going to list them in EXTRA_DIST. Why did you do this? Probably because based on his original query I told him to put the .xpm file in noinst_DATA and I did not mention EXTRA_DIST at all. At that time, nobody had seen the M

Re: How to handle a non-compilable file.

> "David" == David Kirkby <[EMAIL PROTECTED]> writes: David> 1) Without the 'EXTRA_DIST = atlc.xpm CircInRect.xpm etc', the David> programs seem to compile proplery, taking into account any David> changes in the .xpm files, but the .xpm files will not be David> included if I do a 'make dist'.

»õ·Î¿î ¸®½ºÆ®ÀÔ´Ï´Ù

Title: ÀÌ°÷Àº Á¦¸ñÀÔ´Ï´Ù ÄÄÇ»Å͸¦ ÀÌ¿ëÇϽôµ¥ ²À ÇÊ¿äÇÑ ÄÄÇ»ÅÍ °ü·ÃÇÁ·Î±×·¥À» ¾öû Àú·ÅÇÑ °¡°Ý¿¡ ÆË´Ï´Ù ÃÖ½ÅÇ®¹öÀü°ÔÀÓ. ÄÄÇ»ÅÍ°ü·ÃÇÁ·Î±×·¥. ¼ºÀνõð µîµî ÄÄÇ»ÅÍ¿¡ °ü·ÃµÈ ¸ðµç½Ãµð°¡ ÀÖ½À´Ï´Ù ÃֽŸñ·ÏÀÔ´Ï´Ù ¹°·Ð ½Å¿ëÀº ±âº»ÀÔ´Ï´Ù ¾ÐÃàÈ­ÀϼÓÀÇ ³»¿ëÀ» º¸½ÅÈÄ ÀüÈ­³ª ¸ÞÀÏ·Î ¿¬¶ôÁֽʽÿä ÀÌ ¸ÞÀÏÀ»

Re: How to handle a non-compilable file.

Alexandre Duret-Lutz wrote: > Wow! Is my English that bad? :) > > I was merely asking you whether you tried the example you > posted: Now it was not that, but you said > and then say: > atlc.cpp: coax.xpm there was : is your post, which threw me. -- Dr. David Kirkby PhD, email: [EMAIL PRO

Re: How to handle a non-compilable file.

>>> "David" == David Kirkby <[EMAIL PROTECTED]> writes: [...] David> 2) Alexandre suggested the use of 'atlc.cpp: coax.xpm' David> (okay I quoted a simpler example before), but I'm not David> sure what that meant, and so did not do it. Wow! Is my English that bad? :) I was merely asking y

Re: How to handle a non-compilable file.

Alexandre Duret-Lutz wrote: > David> the compiler will reject it, since it does not know the extension. > > Have you tried? What do you see? > Alexandre Duret-Lutz The example I posted with the missing = was due to the fact I'd made an error in the post. I've copied below the *exact* Makefil

Re: How to handle a non-compilable file.

>>> "David" == David Kirkby <[EMAIL PROTECTED]> writes: David> Hi, David> I've got an application, which has a line like this is the C++ code David> #include "coax.xpm" David> where coax.xpm is an XPM format graphics file. If this David> is changed, the code should be recompiled, since it w

Re: *.in strangeness

>>> "Harlan" == Harlan Stenn <[EMAIL PROTECTED]> writes: [...] Harlan> case "$PERLPROG" in Harlan> '') ;; Harlan> *) AC_CONFIG_FILES(local/fixproc) Harlan> AC_CONFIG_FILES(local/snmpcheck) Harlan> AC_CONFIG_FILES(local/tkmib) Harlan> AC_CONFIG_FILES(local/mib2c) Harlan> AC_CONFIG_FILES(lo