SEO

When I tried rebuilding a package under Slackware Vn9.0 it failed with
loads of errors. Just as a quick test, I tried compiling "Hello World"
but that failed too reporting syntax errors in
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h

It worked OK on another machine with Vn8.1 so I'm wondering if there's a
known problem with Vn9.0 or if I've just screwed something up on the
install.

Any ideas, anyone?
--
Mike

Mike wrote:

> When I tried rebuilding a package under Slackware Vn9.0 it failed with
> loads of errors. Just as a quick test, I tried compiling "Hello World"
> but that failed too reporting syntax errors in
> /usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h
>
> It worked OK on another machine with Vn8.1 so I'm wondering if there's a
> known problem with Vn9.0 or if I've just screwed something up on the
> install.
>
> Any ideas, anyone?

Hm... Could you show us the program you're trying to compile and the errors
your compilation produces? I compiled a LOT of programs on Slack 9.0, C and
C++, written by other people and written by me. Never had a problem. There
are a few gotchas in gcc 3.2 though. If you wanna get to the bottom of it,
post your code and the error messages.

Best,
Merl

In message <4X1db.5039679$cI2.715818@news.easynews.com>, Merlin
<merlin_the_wizzard@camelot.com> writes
>Mike wrote:
>
>> When I tried rebuilding a package under Slackware Vn9.0 it failed with
>> loads of errors. Just as a quick test, I tried compiling "Hello World"
>> but that failed too reporting syntax errors in
>> /usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h
>>
>> It worked OK on another machine with Vn8.1 so I'm wondering if there's a
>> known problem with Vn9.0 or if I've just screwed something up on the
>> install.
>>
>> Any ideas, anyone?
>
>Hm... Could you show us the program you're trying to compile and the errors
>your compilation produces? I compiled a LOT of programs on Slack 9.0, C and
>C++, written by other people and written by me. Never had a problem. There
>are a few gotchas in gcc 3.2 though. If you wanna get to the bottom of it,
>post your code and the error messages.
>
I tried rebuilding the apmd package, just as an experiment really, but
it failed with various errors. I couldn't see what was wrong so I
quickly tried out the "Hello World" program -

#include<stdio.h>
main()
{
printf("Hello World\n");
}

I just used "gcc hello.c" to compile it but the output was -

In file included from hello.c:1:
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:37:23: features.h: No such file or directory
In file included from /usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:43,
from hello.c:1:
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stddef.h:213: syntax error before "typedef"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:45:25: bits/types.h: No such file or directory
In file included from hello.c:1:
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:55: syntax error before "typedef"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:71: syntax error before "typedef"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:81:19: libio.h: No such file or directory
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:97: syntax error before "typedef"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:147:28: bits/stdio_lim.h: No such file or directory
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:151: syntax error before "extern"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:161: syntax error before "extern"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:161: parse error before "__THROW"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:163: parse error before "__THROW"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:167: parse error before "__BEGIN_NAMESPACE_STD"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:170: syntax error before "extern"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:170: parse error before "__THROW"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:180: parse error before "__THROW"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:207: parse error before "__BEGIN_NAMESPACE_STD"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:209: syntax error before "extern"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:209: parse error before "__THROW"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:211: parse error before "__THROW"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:225: parse error before "__BEGIN_NAMESPACE_STD"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:228: syntax error before "extern"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:229: parse error before "__THROW"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:233: parse error before "__THROW"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:280: parse error before "__BEGIN_NAMESPACE_STD"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:283: syntax error before "extern"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:283: parse error before "__THROW"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:288: parse error before "__THROW"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:302: parse error before "__BEGIN_NAMESPACE_STD"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:304: syntax error before "extern"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:305: parse error before "__THROW"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:307: parse error before "__THROW"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:310: parse error before "__THROW"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:314: parse error before "_G_va_list"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:316: parse error before "_G_va_list"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:320: parse error before "_G_va_list"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:358: parse error before "__BEGIN_NAMESPACE_STD"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:360: syntax error before "extern"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:361: parse error before "__THROW"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:363: parse error before "__THROW"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:366: parse error before "__THROW"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:388: parse error before "__BEGIN_NAMESPACE_STD"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:390: syntax error before "extern"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:390: parse error before "__THROW"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:391: parse error before "__THROW"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:394: parse error before "__THROW"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:413: parse error before "__BEGIN_NAMESPACE_STD"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:415: syntax error before "extern"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:415: parse error before "__THROW"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:416: parse error before "__THROW"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:419: parse error before "__THROW"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:447: parse error before "__BEGIN_NAMESPACE_STD"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:449: syntax error before "extern"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:450: parse error before "__THROW"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:454: parse error before "__THROW"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:484: parse error before "__BEGIN_NAMESPACE_STD"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:486: syntax error before "extern"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:487: parse error before "__THROW"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:490: parse error before "__THROW"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:494: parse error before "__THROW"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:499: parse error before "__THROW"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:502: parse error before "__THROW"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:520: parse error before "__BEGIN_NAMESPACE_STD"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:522: syntax error before "extern"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:522: parse error before "__THROW"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:524: parse error before "__THROW"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:526: parse error before "__THROW"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:553: parse error before "__BEGIN_NAMESPACE_STD"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:556: syntax error before "extern"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:556: parse error before "fpos_t"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:559: parse error before '*' token
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:582: parse error before "__BEGIN_NAMESPACE_STD"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:584: syntax error before "extern"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:584: parse error before "__THROW"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:586: parse error before "__THROW"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:588: parse error before "__THROW"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:599: parse error before "__BEGIN_NAMESPACE_STD"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:601: syntax error before "extern"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:601: parse error before "__THROW"
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:608:30: bits/sys_errlist.h: No such file or directory
/usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:686: parse error before "__END_DECLS"


These might not be individual errors - I know a single error in a file
can give rise to hundreds of reported errors - but there's something
wrong somewhere. What are the gotchas you mentioned?
--
Mike

On Fri, 26 Sep 2003 23:35:47 +0100, Mike <spamdump@fensoft.co.uk> wrote:
> #include<stdio.h>
> main()

main() should return int; I don't know if gcc fills that in for you, if
you don't specify it.

> I just used "gcc hello.c" to compile it but the output was -
>
> In file included from hello.c:1:
> /usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:37:23:
> features.h: No such file or directory

I'd tackle this one first. Do you have the glibc package installed?


--
Simon <simon@no-dns-yet.org.uk> **** GPG: F4A23C69
"We demand rigidly defined areas of doubt and uncertainty."
- Douglas Adams

Mike wrote:
<>

merl@18:16:49~$ cat hello.c
#include<stdio.h>
main()
{
printf("Helo World\n");
}
merl@18:16:54~$ gcc hello.c
merl@18:17:04~$ ./a.out
Helo World
merl@18:17:07~$ cat /etc/slackware-version
Slackware 9.0.0
merl@18:17:40~$ gcc --version
gcc (GCC) 3.2.2
Copyright (C) 2002 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.



Hm... something seems to be seriously wrong with your installation... I
honestly have no idea at the moment...

Best,
Merl

In message <slrnbn9hqc.od1.usenet@dustpuppy.no-dns-yet.org.uk>, Simon
<usenet@no-dns-yet.org.uk> writes
>On Fri, 26 Sep 2003 23:35:47 +0100, Mike <spamdump@fensoft.co.uk> wrote:
>> #include<stdio.h>
>> main()
>
>main() should return int; I don't know if gcc fills that in for you, if
>you don't specify it.
>
I think it's OK, it worked on another machine with Vn8.1 installed.

>> I just used "gcc hello.c" to compile it but the output was -
>>
>> In file included from hello.c:1:
>> /usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:37:23:
>> features.h: No such file or directory
>
>I'd tackle this one first. Do you have the glibc package installed?
>
What a silly question, of course I ..... Oh S**T!! I hereby nominate
myself for "Prat of The Year" award - I should win it easily (might
manage Prat of the Century too.

I'll install the 'l' series and try again. Thanks for the tip.

--
Mike

In message <SV3db.5041896$mA4.714207@news.easynews.com>, Merlin
<merlin_the_wizzard@camelot.com> writes
>Mike wrote:
><>
>
>merl@18:16:49~$ cat hello.c
>#include<stdio.h>
>main()
>{
>printf("Helo World\n");
>}
>merl@18:16:54~$ gcc hello.c
>merl@18:17:04~$ ./a.out
>Helo World
>merl@18:17:07~$ cat /etc/slackware-version
>Slackware 9.0.0
>merl@18:17:40~$ gcc --version
>gcc (GCC) 3.2.2
>Copyright (C) 2002 Free Software Foundation, Inc.
>This is free software; see the source for copying conditions. There is NO
>warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
>
>
>
>Hm... something seems to be seriously wrong with your installation... I
>honestly have no idea at the moment...
>
Er, yes. Seems I hadn't installed the 'l' series I'm doing it now
so, hopefully, all will be well soon. Thanks for the help.

--
Mike

On Sat, 27 Sep 2003 10:25:47 +0100, Mike <spamdump@fensoft.co.uk> wrote:
> In message <slrnbn9hqc.od1.usenet@dustpuppy.no-dns-yet.org.uk>, Simon
><usenet@no-dns-yet.org.uk> writes
>>On Fri, 26 Sep 2003 23:35:47 +0100, Mike <spamdump@fensoft.co.uk> wrote:
>>> In file included from hello.c:1:
>>> /usr/lib/gcc-lib/i386-slackware-linux/3.2.2/include/stdio.h:37:23:
>>> features.h: No such file or directory
>>
>>I'd tackle this one first. Do you have the glibc package installed?
>>
> What a silly question, of course I ..... Oh S**T!! I hereby nominate
> myself for "Prat of The Year" award - I should win it easily (might
> manage Prat of the Century too.

I've done similar things. Once thing you might want to look at is one
of the entries in our FAQ - "Which package contains <insert filename
here>?": <URL:http://wombat.san-francisco.ca.us/cgi-bin/fom?file=14>.

> I'll install the 'l' series and try again. Thanks for the tip.

No problem.


--
Simon <simon@no-dns-yet.org.uk> **** GPG: F4A23C69
"We demand rigidly defined areas of doubt and uncertainty."
- Douglas Adams

In message <slrnbnbk3t.v29.usenet@dustpuppy.no-dns-yet.org.uk>, Simon
<usenet@no-dns-yet.org.uk> writes
>On Sat, 27 Sep 2003 10:25:47 +0100, Mike <spamdump@fensoft.co.uk> wrote:
>> I'll install the 'l' series and try again. Thanks for the tip.
>
>No problem.
>
With the 'l' series installed I can compile stuff now. I've noticed
something strange though. Just as an experiment, I rebuilt some of the
packages without changing anything but the output .tgz files I produced
had different sizes from the originals. For example the
cpio-2.5-i386-1.tgz on the installation disks is 75494 but when I
rebuilt it I got 70686. Comparing the sizes of the individual programs,
I found these differences-

file original rebuild

bin/cpio 52764 52568
bin/mt-GNU 10772 10752
info/cpio.info.gz 6084 6083

The compile seems OK. I'm not that familiar with this but I copied the
source into /tmp and used SlackBuild >mike 2>mike2 (yeah, I know, very
original filenames <g>) to rebuild the package. Afterwards, mike2 had
one line saying "tar-1.13: cpio-2.5-i386-1.tar is the archive; not
dumped". I presume this is OK but I'm a bit new to Slackware and,
especially, rebuilding packages - up to now I've just been using Linux
as an OS.

--
Mike

On Thu, 2 Oct 2003 18:54:33 +0100, Mike <spamdump@fensoft.co.uk> wrote:
> For example the
> cpio-2.5-i386-1.tgz on the installation disks is 75494 but when I
> rebuilt it I got 70686.

I've not tried rebuilding without changing anything (either the version
or ./configure arguments), so I don't know what's causing that.

> Afterwards, mike2 had
> one line saying "tar-1.13: cpio-2.5-i386-1.tar is the archive; not
> dumped". I presume this is OK

That's fine. tar is just refusing to put the tar archive inside
itself.


--
Simon <simon@no-dns-yet.org.uk> **** GPG: F4A23C69
"We demand rigidly defined areas of doubt and uncertainty."
- Douglas Adams