All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Adams <pa3gcu@zeelandnet.nl>
To: Thomas Beer <tbeer@analogon.com>, linux-newbie@vger.kernel.org
Subject: Re: make error
Date: Tue, 16 Apr 2002 19:06:12 +0000	[thread overview]
Message-ID: <02041619061203.04062@unix.pa3gcu> (raw)
In-Reply-To: <00a701c1e575$ea0958e0$0901a8c0@system>

On Tuesday 16 April 2002 18:38, Thomas Beer wrote:
> Hi,
>
> I'm trying to install a radio clock software, which
> issues make errors. Can anyone guess what may be
> wrong. Tryed to modify the pcfclock.c with no positive
> result. Any suggestions are highly appreciated.
>
> Thanks Tom

The thing is with source is that quite often it will only compile with a 
spesific kernel-verion-header files/and or spesific libs.

I suggest you check the doc's which i am presuming came with the source and 
see if there is any mention of what the authour used to compile it.

It could also be that he/she used a different compiler than you have.

>
> make
> cd . \
>   && CONFIG_FILES= CONFIG_HEADERS=config.h \
>      /bin/sh ./config.status
> config.status: creating config.h
> config.status: config.h is unchanged
> make  all-recursive
> make[1]: Wechsel in das Verzeichnis Verzeichnis
> »/big/download/pcfclock-0.29«
> Making all in linux
> make[2]: Wechsel in das Verzeichnis Verzeichnis
> »/big/download/pcfclock-0.29/linux«
> gcc -O2 -Wall -fomit-frame-pointer -I/lib/modules/2.4.4/build/include
> -D__KERNEL__ -DMODULE -DMODVERSIONS -include
> /lib/modules/2.4.4/build/include/linux/modversions.h -D__SMP__   -c -o
> pcfclock.o pcfclock.c
> pcfclock.c:547: parse error before string constant

This could be a simple syntax error in the source, or it could be the result 
of a header file mismatch.

> pcfclock.c:547: warning: type defaults to `int' in declaration of
> `MODULE_LICENSE'
> pcfclock.c:547: warning: data definition has no type or storage class

Looking at that i would take a wild guess and say that the software is very 
old indeed and needs lib5 support, thesedays we have Glib's and they are 
mostly not backwards compatable.

Of course it could be something else intyrly...

> make[2]: *** [pcfclock.o] Fehler 1
> make[2]: Verlassen des Verzeichnisses Verzeichnis
> »/big/download/pcfclock-0.29/linux«
> make[1]: *** [all-recursive] Fehler 1
> make[1]: Verlassen des Verzeichnisses Verzeichnis
> »/big/download/pcfclock-0.29«
> make: *** [all] Fehler 2
> [tom@milestone pcfclock-0.29]$
>
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.linux-learn.org/faqs

-- 
Regards Richard
pa3gcu@zeelandnet.nl
http://people.zeelandnet.nl/pa3gcu/

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

  reply	other threads:[~2002-04-16 19:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-16 18:38 make error Thomas Beer
2002-04-16 19:06 ` Richard Adams [this message]
2002-04-17  0:59 ` lawson_whitney
2002-04-17  6:40   ` Tom Beer
  -- strict thread matches above, loose matches on Subject: below --
2011-10-08 12:04 Masaru Nomiya
2011-10-10 11:02 ` Todor Tomov
2011-10-10 12:26   ` Masaru Nomiya
2012-11-01 12:18 Gregg Douglas
     [not found] ` <CAP0ktjLiv=2U2oja_2vk1r9Gof_xL+n5Vs0diigsPOMxWHyvdw@mail.gmail.com>
2012-11-01 13:13   ` Gregg Douglas
2012-11-01 14:40     ` Kumar amit mehta

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=02041619061203.04062@unix.pa3gcu \
    --to=pa3gcu@zeelandnet.nl \
    --cc=linux-newbie@vger.kernel.org \
    --cc=tbeer@analogon.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.