From: Takashi Iwai <tiwai@suse.de>
To: Andrei Boros <andrei@srr.ro>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: alsa-driver, make 3.79, cvscompile
Date: Thu, 20 Mar 2003 11:58:36 +0100 [thread overview]
Message-ID: <s5h3clis3s3.wl@alsa2.suse.de> (raw)
In-Reply-To: <3E799CB6.EB6ED828@srr.ro>
At Thu, 20 Mar 2003 12:49:26 +0200,
Andrei Boros wrote:
>
> Takashi Iwai wrote:
> >
> > > I got make 3.79 installed, hopefully the sequencer module problems will
> > > be solved, but I get a tiny error that didn't appear before when runing
> > > cvscompile :
> > >
> > > I updated the cvs tree, did a make clean, deleted Makefile, then ran
> > ^^^^^^^^^^^^^^^^
> > ?? you'll need it for cvscompile, too. Makefile itself won't
> > generated by configure (but Makefile.conf will be).
>
> I corrected that.
> It still wants to make all-deps before anything else, when I run
> cvscompile. Dunno it this is intended.
this is intentional behavior.
"make all-deps" will create the dependent files for configure script
such as toplevel.config.in.
Takashi
-------------------------------------------------------
This SF.net email is sponsored by: Tablet PC.
Does your code think in ink? You could win a Tablet PC.
Get a free Tablet PC hat just for playing. What are you waiting for?
http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en
next prev parent reply other threads:[~2003-03-20 10:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-19 10:45 sequencer module problems Andrei Boros
2003-03-19 11:29 ` Takashi Iwai
[not found] ` <3E7863A8.B5BACE35@srr.ro>
2003-03-19 13:41 ` Takashi Iwai
2003-03-20 8:17 ` Typo in configure.in : dummy sequencer Andrei Boros
2003-03-20 8:28 ` Jaroslav Kysela
2003-03-20 8:20 ` alsa-driver, make 3.79, cvscompile Andrei Boros
2003-03-20 10:33 ` Takashi Iwai
[not found] ` <3E799CB6.EB6ED828@srr.ro>
2003-03-20 10:58 ` Takashi Iwai [this message]
2003-03-20 8:28 ` dummy sequencer module problems Andrei Boros
2003-03-20 10:32 ` Takashi Iwai
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=s5h3clis3s3.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=andrei@srr.ro \
/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.