On 2/10/2019 4:28 AM, C.J. Wagenius wrote:
> gcc -Wl,--verbose -o testa `pkg-config --cflags --libs glib-2.0` test.c
Try: gcc -o testa test.c `pkg-config --cflags --libs glib-2.0`
Its the way the compiler works under Windows (i.e. no unresolved
references, and the order of searching for them).
Hi.
I'm trying to compile the following source file
---
#include
#include
int main(int argc, char **argv)
{
int *a;
a = g_new(int, 1);
g_free(a);
return 0;
}
---
... and get linking errors.
$ gcc -Wl,--verbose -o testa `pkg-config --cflags --libs glib-2.0` test.c
/tmp/ccHtEBvg.o:te
On Feb 9 15:33, Tom Honermann wrote:
> On 2/9/2019 9:51 AM, Corinna Vinschen wrote:
> > On Feb 8 22:25, Tom Honermann wrote:
> >> The following program demonstrates the problem.
> >> [...]
> >> Here is where things go bananas. If the program is run with stdout
> >> initially redirected to a pipe
On Feb 9 18:43, Vince Rice wrote:
> > On Feb 9, 2019, at 6:01 PM, L A Walsh wrote:
> >
> > On 2/9/2019 11:06 AM, Vince Rice wrote:
> >>> On Feb 9, 2019, at 8:46 AM, L A Walsh wrote:
> >
> >> What you think about this is irrelevant.
> >
> >Not really.
> Yes, really.
>
> >
> >> What I think
Am 10.02.2019 um 15:04 schrieb Mundru Suresh:
I have got a warning message while opening bash shell in windows 10. Please
provide a solution to fix this warning. Is this a serious warning??
The warning message is as below,
*"1 [main] bash 124704 find_fast_cwd: WARNING: Couldn't compute
FAST_CWD
5 matches
Mail list logo