From: corey taylor <corey.taylor@gmail.com>
To: Jupp Tscheak <jupp_tscheak@gmx.de>
Cc: gcc-help@gcc.gnu.org
Subject: Re: problems with make...
Date: Wed, 09 Feb 2005 09:11:00 -0000 [thread overview]
Message-ID: <2e393d08050208134329effa4e@mail.gmail.com> (raw)
In-Reply-To: <420931cd.73b89a7f.78a5.30baSMTPIN_ADDED@mx.gmail.com>
Jupp,
For what behavior are you looking?
corey
On Tue, 8 Feb 2005 22:40:45 +0100, Jupp Tscheak <jupp_tscheak@gmx.de> wrote:
> Hi,
>
> we're building our project with automatic generated Makefiles (using qt's
> .pro files, although
> some modules have nothing to do with qt!). The problem is that if a static
> linked library has changed,
> it says "nothing to be done for..." (binary file is older than static lib so
> it should be relinked).
> Does anyone know how to avoid this behavior (any flags for g++)?
>
> Thanks in advance
>
> Jupp Tscheak
>
>
next parent reply other threads:[~2005-02-08 21:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <420931cd.73b89a7f.78a5.30baSMTPIN_ADDED@mx.gmail.com>
2005-02-09 9:11 ` corey taylor [this message]
2005-02-09 14:18 ` AW: " Jupp Tscheak
2005-02-09 14:18 ` Jupp Tscheak
[not found] ` <42093505.69af1669.78a5.37f4SMTPIN_ADDED@mx.gmail.com>
2005-02-09 15:06 ` corey taylor
2005-02-09 15:10 ` Tony Wetmore
2005-02-09 16:01 ` corey taylor
2005-02-09 16:09 ` corey taylor
2005-02-09 1:46 Jupp Tscheak
-- strict thread matches above, loose matches on Subject: below --
2005-02-09 1:46 Jupp Tscheak
[not found] <616BE6A276E3714788D2AC35C40CD18D393F99@whale.softwire.co.uk>
2002-01-28 4:28 ` Problems " Rupert Wood
[not found] <616BE6A276E3714788D2AC35C40CD18D393F88@whale.softwire.co.uk>
2002-01-28 3:41 ` Rupert Wood
2002-01-28 4:16 ` Momchil Velikov
2002-01-28 3:31 kabir.patel
1999-12-23 5:27 problems " Adriano Holanda
1999-12-31 22:24 ` Adriano Holanda
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=2e393d08050208134329effa4e@mail.gmail.com \
--to=corey.taylor@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=jupp_tscheak@gmx.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).