Many makepkg issues

CyRiX_BlAcK · 2006-03-06 19:45:46

Im trying to makepkg K9COPY and BOSON both are in AUR.

Both give out the same error during the build:

checking for X... configure: error: Can't find X includes. Please check your installation and add the correct paths!
make: *** No targets specified and no makefile found. Stop.
==> ERROR: Build Failed. Aborting...

This is driving me nuts, I just cant seem to get it sorted, its annoying as hell.

Can someone else grab BOSON its only small and try to makepkg it and see if it works.

Its ever since Xorg7 that alot of AUR stuff dont work... :? :? :?

My Xorg is setup like this for Xorg7:

Section "Files"
RgbPath "/usr/share/X11/rgb"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/misc:unscaled"
FontPath "/usr/share/fonts/misc"
FontPath "/usr/share/fonts/75dpi:unscaled"
FontPath "/usr/share/fonts/75dpi"
FontPath "/usr/share/fonts/100dpi:unscaled"
FontPath "/usr/share/fonts/100dpi"
FontPath "/usr/share/fonts/PEX"
# Additional fonts: Locale, Gimp, TTF...
FontPath "/usr/share/fonts/cyrillic"
# FontPath "/usr/share/fonts/latin2/75dpi"
# FontPath "/usr/share/fonts/latin2/100dpi"
# True type and type1 fonts are also handled via xftlib, see /etc/X11/XftConfig!
FontPath "/usr/share/fonts/Type1"
FontPath "/usr/share/fonts/ttf/western"
FontPath "/usr/share/fonts/ttf/decoratives"
FontPath "/usr/share/fonts/truetype"
FontPath "/usr/share/fonts/truetype/openoffice"
FontPath "/usr/share/fonts/truetype/ttf-bitstream-vera"
FontPath "/usr/share/fonts/latex-ttf-fonts"
FontPath "/usr/share/fonts/defoma/CID"
FontPath "/usr/share/fonts/defoma/TrueType"
EndSection

gradgrind · 2006-03-06 20:25:39

Can someone else grab BOSON its only small

Is that what 'small' means nowadays? About 35MB? When I was a lad ...

Anyway, it sounds like you are missing one of the 35000000 packages which make up the new, improved Xorg.

I ran makepkg and didn't get your error, but I did get a compile error. I'm only guessing, but it could be connected with changes in gcc. Check that this program will compile under the present gcc - it looks like it might only work under gcc3.

Sander · 2006-03-07 18:10:32

Maybe boson is still looking for stuff in the old X dirs? Usually a few symlinks resolve the issue, in that case. But don't ask me exactly which

Snowman · 2006-03-07 20:12:34

Sander wrote:

Maybe boson is still looking for stuff in the old X dirs? Usually a few symlinks resolve the issue, in that case. But don't ask me exactly which

No, gradgrind is correct. CyRiX_BlAcK is missing some *proto packages. Here's the ones I have:

[02/19/06 20:23] installed xextproto (7.0.2-1)
[02/19/06 20:23] installed printproto (1.0.3-1)
[02/19/06 20:29] installed xf86vidmodeproto (2.2.2-1)
[02/19/06 20:29] installed glproto (1.4.3-1)
[02/19/06 20:29] installed xproto (7.0.4-2)
[02/19/06 20:29] installed fixesproto (3.0.2-1)
[02/19/06 20:29] installed compositeproto (0.2.2-1)
[02/19/06 20:29] installed damageproto (1.0.3-1)
[02/19/06 20:30] installed xf86dgaproto (2.0.2-1)
[02/19/06 20:30] installed videoproto (2.2.2-1)
[02/19/06 20:30] installed kbproto (1.0.2-1)
[02/19/06 20:30] installed inputproto (1.3.2-1)
[02/19/06 20:30] installed xineramaproto (1.1.2-1)
[02/19/06 20:30] installed randrproto (1.1.2-1)
[02/19/06 20:30] installed renderproto (0.9.1-1)
[02/19/06 20:31] installed recordproto (1.13.2-1)
[02/19/06 20:31] installed xf86miscproto (0.9.2-1)
[02/19/06 20:51] installed fontsproto (2.0.2-1)
[02/19/06 20:51] installed dmxproto (2.2.2-1)
[02/19/06 20:51] installed fontcacheproto (0.1.2-1)
[02/19/06 20:51] installed trapproto (3.4.3-1)
[02/20/06 01:27] installed scrnsaverproto (1.0.2-1)

I recommend installing them all.
Anyway, this doesn't fixed boson. It's a gcc4 issue. There's already a comment to that effect in AUR. Check if a newer version of boson was released.

When you say "Its ever since Xorg7 that alot of AUR stuff dont work", if your talking about the X include not found problem, installing the *proto packages will solve it. There might be PKGBUILD in AUR not working with xorg7. In that case, probably the maintainer didn't updated its PKGBUILD yet. Post a comment in AUR to notify him.

PeteMo · 2006-03-07 22:34:30

Snowman wrote:

No, gradgrind is correct. CyRiX_BlAcK is missing some *proto packages. Here's the ones I have:

[02/19/06 20:23] installed xextproto (7.0.2-1)
[02/19/06 20:23] installed printproto (1.0.3-1)
[02/19/06 20:29] installed xf86vidmodeproto (2.2.2-1)
[02/19/06 20:29] installed glproto (1.4.3-1)
[02/19/06 20:29] installed xproto (7.0.4-2)
[02/19/06 20:29] installed fixesproto (3.0.2-1)
[02/19/06 20:29] installed compositeproto (0.2.2-1)
[02/19/06 20:29] installed damageproto (1.0.3-1)
[02/19/06 20:30] installed xf86dgaproto (2.0.2-1)
[02/19/06 20:30] installed videoproto (2.2.2-1)
[02/19/06 20:30] installed kbproto (1.0.2-1)
[02/19/06 20:30] installed inputproto (1.3.2-1)
[02/19/06 20:30] installed xineramaproto (1.1.2-1)
[02/19/06 20:30] installed randrproto (1.1.2-1)
[02/19/06 20:30] installed renderproto (0.9.1-1)
[02/19/06 20:31] installed recordproto (1.13.2-1)
[02/19/06 20:31] installed xf86miscproto (0.9.2-1)
[02/19/06 20:51] installed fontsproto (2.0.2-1)
[02/19/06 20:51] installed dmxproto (2.2.2-1)
[02/19/06 20:51] installed fontcacheproto (0.1.2-1)
[02/19/06 20:51] installed trapproto (3.4.3-1)
[02/20/06 01:27] installed scrnsaverproto (1.0.2-1)

Somewhat OT, but how did you get that output?

Thanks

Cam · 2006-03-07 22:56:31

cat /var/log/pacman.log | grep proto

That's what it looks like anyway

tomk · 2006-03-07 23:10:44

You could also get the complete list of *proto packages direct from pacman -

pacman -Ss proto

and go through it by hand, or better still

pacman -Ss proto | grep /.*proto | grep -v protocol

to get rid of package descriptions and anything that isn't *proto.
Or you could find and install them all in one command

pacman -S `pacman -Ss proto | grep /.*proto | grep -v protocol | cut -d "/" -f 2 | cut -d " " -f 1 | tr "n" " "`

Add --noconfirm to that and you won't even have to confirm with 'Y'.

PeteMo · 2006-03-08 00:59:31

Cam wrote:

cat /var/log/pacman.log | grep proto

Cool, I didn't know pacman kept a log of all activity -- that's pretty useful!

tomk wrote:

pacman -Ss proto | grep /.*proto | grep -v protocol
to get rid of package descriptions and anything that isn't *proto.

That is also very handy. I can tell what the / in /.*proto does (it gets rid of the second line - the package description - in the pacman output), but I'm unclear on exactly why (or how) it does that. I'd like to file away that /.* expression for future use, but I'd like to understand it a little better.

_Gandalf_ · 2006-03-08 01:35:02

it isn't about /.* it's about .*, let's take a look at pacman -Ss proto output (just 2 of them actually)

current/randrproto 1.1.2-1
community/ruby-gtktrayicon 0.1.0-1

so how did tomk do in order to seperate randrproto and ruby-gtktrayicon?? actually when you call grep you can pass either words or regular expression, so the / is what's after current or community nothing special, .* matches any character afterward till proto
so
/randrproto matches /.*proto but not /ruby-gtktrayicon coz there isn't a proto in the name

try for example this
i want all the lines that has join and a channel name that has arch from an irc log, like

echo -e "/join #archlinuxn/msg archer hi" | grep arch

but this will give me also messages sent to users with name has arch, as well as normal messages which has arch
so if i change the above line to

echo -e "/join #archlinuxn/msg archer hi" | grep /join.*arch

i can get what i want, try them

hope that helps !

PeteMo · 2006-03-08 02:35:50

_Gandalf_ wrote:

it isn't about /.* it's about .*, let's take a look at pacman -Ss proto output (just 2 of them actually)
current/randrproto 1.1.2-1
community/ruby-gtktrayicon 0.1.0-1
so how did tomk do in order to seperate randrproto and ruby-gtktrayicon?? actually when you call grep you can pass either words or regular expression, so the / is what's after current or community nothing special, .* matches any character afterward till proto
so
/randrproto matches /.*proto but not /ruby-gtktrayicon coz there isn't a proto in the name

Ok, I see. Thanks. I was confused by the slash because I didn't think it was needed. I see though that it is limiting the .* (any character zero or more times) expression to only characters after a "/". That keep the "proto" in the ruby-gtktrayicon description from matching - since it isn't preceeded by a "/" anywhere. Awesome. Thanks.

_Gandalf_ · 2006-03-08 02:51:22

Glad i made it clear

you're welcome

Snowman · 2006-03-08 03:45:53

Cam wrote:

cat /var/log/pacman.log | grep proto
That's what it looks like anyway

Actually, I did:
grep proto /var/log/pacman.log
and removed the ones that where not related to xorg's *proto packages.

CyRiX_BlAcK · 2006-03-09 19:26:18

I have all them proto thingys, but still. Anyone know a say to get boson to atually work?

im not missing any of the proto thingys, so its a gcc4 thing?

This is what I got installed, All of em!

current/fontsproto 2.0.2-1
current/glproto 1.4.5-1
current/inputproto 1.3.2-1
current/kbproto 1.0.2-1
current/printproto 1.0.3-1
current/randrproto 1.1.2-1
current/recordproto 1.13.2-1
current/renderproto 0.9.1-1
current/resourceproto 1.0.2-1
current/scrnsaverproto 1.0.2-1
current/trapproto 3.4.3-1
current/videoproto 2.2.2-1
current/xcmiscproto 1.1.2-1
current/xextproto 7.0.2-1
current/xf86bigfontproto 1.1.2-1
current/xf86dgaproto 2.0.2-1
current/xf86driproto 2.0.3-1
current/xf86miscproto 0.9.2-1
current/xf86rushproto 1.1.2-1
current/xf86vidmodeproto 2.2.2-1
current/xineramaproto 1.1.2-1
current/xproto 7.0.4-2
current/xproxymngproto 1.0.2-1

Tell you what you get the PKG build and build it and tell me how you did it lol, I still get this:

checking for snprintf... yes
checking for X... configure: error: Can't find X includes. Please check your installation and add the correct paths!
make: *** No targets specified and no makefile found. Stop.
==> ERROR: Build Failed. Aborting...

Arch Linux

#1 2006-03-06 19:45:46

Many makepkg issues

#2 2006-03-06 20:25:39

Re: Many makepkg issues

#3 2006-03-07 18:10:32

Re: Many makepkg issues

#4 2006-03-07 20:12:34

Re: Many makepkg issues

#5 2006-03-07 22:34:30

Re: Many makepkg issues

#6 2006-03-07 22:56:31

Re: Many makepkg issues

#7 2006-03-07 23:10:44

Re: Many makepkg issues

#8 2006-03-08 00:59:31

Re: Many makepkg issues

#9 2006-03-08 01:35:02

Re: Many makepkg issues

#10 2006-03-08 02:35:50

Re: Many makepkg issues

#11 2006-03-08 02:51:22

Re: Many makepkg issues

#12 2006-03-08 03:45:53

Re: Many makepkg issues

#13 2006-03-09 19:26:18

Re: Many makepkg issues

Board footer